Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a strange issue:

We have two DNS servers, both are Windows 2003 SP2. The only difference between the two is they have seperate gateways to the internet. One goes out through a cable modem, the other goes out through a 10MB metro-ethernet service.

Both servers appear to work fine, having no issues, all clients are able to resolve internal and external DNS querries, with one exception. When doing an nslookup on the first server, I receive a timeout messgae for one and only one particular domain. The other server doesn't not receive a timeout for that same domain, it works fine.

When looking at the domain in question, I see no issues, I'm able to ping it from other computers outside my network, etc. How can I troubleshoot the reason for this particular domain lookup failing on only this DNS server?

Things I've done so far: 1. Reset the cache on both server. 2. Restart both servers 3. Turn debugging on, but nothing is showing up in the logs.

share|improve this question
up vote 1 down vote accepted

Here's what I would do: install a packet capture program on the DNS server in question (Microsoft Network Monitor works well), start a capture using a filter for DNS traffic, run nslookup for the domain in question, wait until nslookup times out, stop the capture and analyze the DNs traffic to see where the issue is occurring.

share|improve this answer
Good idea. I was hoping there was a debug/error log I could turn on more easily and get some info, but if there isn't then I might go this route. – Aaron Oct 29 '10 at 19:27

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.