Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

We're having some issues with our name resolution, but the first thing we're trying to figure out is whether our DNS server is resolving the names or if it's the DNS configured on our Router which connects us to our ISP.

What tests can I perform to figure this out?

Regards, Jacques

share|improve this question
Are the names you're trying to resolve local? Is the DNS server configured to use the router as a forwarder? Are the clients configured to use the server for DNS, or the router, or both? – joeqwerty Sep 15 '11 at 13:18
Each machine seems to be configured to use the Win Server 2008 as the primary DNS, the DNS server on the Win Server in turn has forwarders configured which is set to our ISPs DNS servers – Jacques Sep 15 '11 at 14:33
Then you're not using your router for DNS. – joeqwerty Sep 15 '11 at 14:43
up vote 2 down vote accepted

From a client, open a command prompt and run nslookup. It should tell you what DNS server it is connecting to. When you resolve a name it will tell you what server answers.

To see which server resolves a specific request, try using dig +trace to see the path it takes to find the answer

share|improve this answer
Yip, that points to our internal DNS server. Our internal DNS uses forwarders, a few of them, is there a way to tell which DNS server our server uses when it can't resolve the name itself? I know it should go in the order specified in the forwarders section, just wondering if there's a way to tell exactly which servers are responding well – Jacques Sep 15 '11 at 14:35
Run a network capture on the DNS server and then open up a web page (HP, Microsoft, Yahoo, etc) and watch the capture for DNS queries FROM your DNS server and see which forwarder is performing the DNS lookup for your server. – joeqwerty Sep 15 '11 at 14:44
If you have a Linux machine handy, use dig with the +trace option to see the resolution path. – uSlackr Sep 15 '11 at 20:06
There are copies of dig available on the web that have been built as binaries for Windows. – mfinni Jul 19 '13 at 16:59

Are you pointing your clients to a non active-directory DNS server? Even as a secondary DNS server, this is a bad idea. Stop it. Setup an additional DC with DNS and point your clients to that box as your secondary DNS. Once your done doing that, you'll know for sure that your clients are resolving names using one of your servers.

share|improve this answer
As far as I know the internal clients point to the Win Server 2008 which is an SBS edition and as far as I know is an Active Directory server as well – Jacques Sep 15 '11 at 14:36
@Jacques - Then why are you asking if your router is resolving DNS? – Jason Berg Sep 15 '11 at 14:45

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.