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 W2K3 Server that is the Domain Controller and also the DNS server. I wanted to make another DNS zone on my network called "something.local" and then make 'A' records to point requests like 'admin.something.local' and 'www.something.local' to machines on my network.

I keep getting DNS timeouts but then after 2 tries it succeeds. Why would this happen? How can I troubleshoot?

From my desktop I run:

nslookup admin.something.local

and get:


DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.

Name:    admin.something.local

If I go back the other way:


I get:


Name: admin.something.local
  • My DNS server address is
  • The new DNS zone is not hooked up to active directory.
  • I do not have much experience with DNS.
  • Yesterday it was working fine.
  • I have tried doing an 'ipconfig /flushdns' on both my desktop and the DNS server
share|improve this question
up vote 1 down vote accepted

Good chance your DNS or client has a slight bit of physical resource contraints. This is more common when using virtualization with the DNS server and/or DNS client. Likely, the response to the query is returned just after the default 2 second wait time before timing out in nslookup.

Try this at a command prompt:


If that works the first time, that's likely the issue. The reason it worked the second time is the query is now cached in the DNS server's memory, thereby allowing it to respond without reading from disk the zone file.

share|improve this answer

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.