Windows 7 stops resolving DNS

Intermittently, numerous PCs with Windows 7 stop resolving DNS for a site (no specific site today). When this happens the browser displays a server not found error. Using command prompt, cannot ping the name (could not find host). Use NSLOOKUP and an IP address is returned. Able to ping the IP address or type IP in browser and get to site. Able to ping or browse to other sites by name. Using Wireshark no DNS entries show up. If DNS cache is flushed or the DNSClient service is disabled it starts functioning. 3000 node network. Have been looking for solution several days.
Who is Participating?
rfairchildsConnect With a Mentor Author Commented:
Thanks for the help. We finally caught a request going to our DNS server that didn't respond so we have opened a case with our DNS vendor. Thanks for all the assistance.
some things to try -

if you're not using ipv6 remove it from the network setup

If you are - and for Ipv4 - make sure you have Obtain DNS server automatically checked in advanced settings - unless you are manually configuring opendns

the nslookup might be a red herring - it might be resolving in the local cache before you flush it

I'd suggest reinstalling driver for network card but you mentioned its multiple PC, are they all identical, same driver etc?
David Johnson, CD, MVPOwnerCommented:
what are your dns server entries?
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

rfairchildsAuthor Commented:
IPV6 disabled
DNS automatic
Will check local cache next time it happens.
Multiple machines, assorted hardware.
We have two internal DNS servers that are handed out via DHCP.
The really curious thing about this is that no requests are made via the NIC when this happens (according to Wireshark).
Wondering if it is mistakenly using some other interface that it shouldn't.
If its always the same machines that are affected you could try changing some of them over to an alternate DNS (manually)  -opendns for example- and see if it still occurs; then you can at least prove that the problem is local.

I'd also check the network routing tables if you are looking for other interfaces (route.exe).

It might also be worth recording the route, nslookup and ipconfig info on one of the machines when its working for a before/after comparison
rfairchildsAuthor Commented:
The problem was found in house.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.