On my Windows 2008 R2 Active Directory server (which also is the DNS server), my AD domain name is MyDomainName.com.
Our college website, hosted on a separate server, has the same domain name, namely, MyDomainName.com.
In my DNS settings, I have MyDomainName.com pointing to 10.0.0.30, which is the AD & DNS server, and MyDomainName.com also has an A Record for 10.0.0.32, which is the webserver.
When accessing the website MyDomainName.com, the initial pause between adding the domain name to your browser and site actually appearing, can take many annoying seconds. When I added another A Record pointing to our website and gave it Web.MydomainName.com, then the site appears very quickly.
I don't really know what is going on, but I am guessing the long delay has something to do with the AD Domain name having the same domain name as the website is the root of the problem? The problem only happens on the campus where the AD server is, while off campus the domain name only points to the website IP address.
Is there something I am supposed to do on our DNS server to prevent this long delay from occurring? So that when a browser makes a request to the AD/DNS server, it returns the IP address of the webserver immediately. Or am I barking up the wrong tree with this?
NOTE: I have added this also to the IIS Web Server Topic, though our website does not use IIS.