I'm having a DNS resolving issue that
is affecting the performance of my locally hosted web site when browse it on my local
machine. If I attach my network's DNS suffix to my local machine name when I go to the
URL in my browser, the site has terrible load times (100+ times slower) than without the
DNS suffix.
I thought I could fix this by using
my hosts file to avoid the need for a lookup. I added an entry to my hosts file like
this
127.0.0.1
myMachine.MyDnsSuffix
But
this didn't change the load times, even after a reboot. Although it is not important to
resolve this specific problem, I would really like to know
why this
happens.
Also, when I run nslookup on the domain
myMachine.MyDnsSuffix
, I notice it uses my network's DNS server
to find the IP. Could this be related to my problem or am I just mis-understanding how
nslookup works?
I believe
nslookup is used to test a DNS server itself, as opposed to utilizing your HOSTS file.
rel="noreferrer">http://support.microsoft.com/kb/200525 seems to indicate
as much.
Try just a simple ping. Does
ping myMachine.MyDnsSuffix
resolve to the loopback address you
have specified in your HOSTS file?
Comments
Post a Comment