Troubleshoot DNS Browsing Issues


We have a web site that is hosted internally that users who are also situated internally sometimes have trouble resolving.  Sometimes when they try to resolve the URL, they receive the "Page Cannot Be displayed" in the web browser.

The workaround we have found is to flush the DNS cache on the client computer using the following command from a command line prompt (I've put it into a batch file):

ipconfig /flushdns

We have 2 Windows Server 2008 R2 domain controllers that is also serving as a DNS servers.

So far we've only been able to test with Windows clients, but I am thinking of trying a Linux client as well in order to see if it's not isolated to Windows.

Having said that, I'm wondering if anyone has an idea as to what is causing this or how to fix this without having our users always resorting to running a ipconfig /flushdns

Thanks for any help,
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.


At a command prompt of the client run NSLOOKUP and at the prompt, enter the name of the webserver. e.g.
Is the correct IP address returned, or multiple addresses?
Check you get the same results from both DNS servers by using the "SERVER" command in nslookup to query the other DNS server.  e.g. server

How is the DNS client configured on the workstation - which DNS servers is it using, check it is NOT configured with external DNS servers.

Also on the client, in IE options disable "Show friendly HTTP error messages" which may give some more detail.

When next experiencing the issue, at the client, again run the nslookup to see if it is still the same.

Can you ping the server by IP address when getting the error in IE?

That should give a little more to go on...
Perform an NSLookup for the host at each of your DNS servers

nslookup dnsserver1
nslookup dnsserver2

Is the destination web server operating on a single nic or multiple nics?
Gary ColtharpSr. Systems EngineerCommented:
I have seen this happen when clients were configured with both domain and public DNS servers. Ideally, they should only DNS to a domain controller.



Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
paradigm_ISAuthor Commented:
I'm going to try Gary's suggestion and remove the public DNS entry from the DHCP lease that clients get.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.