[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

First NSLookup always times out

Posted on 2009-12-23
5
Medium Priority
?
1,886 Views
Last Modified: 2015-01-12
I have a training environment which consists of 1 physical 2008 R2 Server running AD, DNS, DHCP and Hyper V. On Hyper V I have 2 other DCs (2008 R2) which are also running DNS.

When I use nslookup to look up an internet address the first attempt always times out. When I run nslookup again, it resolves correctly. The behaviour is the same from all servers and clients:

C:\Users\ben>nslookup google.com
Server:  btraining.home.com
Address:  192.168.1.105

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to btraining.home.com timed-out

C:\Users\ben>nslookup google.com
Server:  btraining.home.com
Address:  192.168.1.105

Non-authoritative answer:
Name:    google.com
Addresses:  209.85.227.147
          209.85.227.106
          209.85.227.105
          209.85.227.99
          209.85.227.104
          209.85.227.103

btraining, 192.168.1.105, is set by DCHP as the primary DNS and it's own IP address is set for DNS in tcp/ip properties. The problem is the same when using one of the other servers. At the moment I have to refresh web pages to get them to display, as the first lookup always times out.

Can anyone suggest the cause of this problem?

Thanks for your help
   
0
Comment
Question by:BenBispham1
  • 2
  • 2
5 Comments
 
LVL 26

Accepted Solution

by:
Pber earned 2000 total points
ID: 26112248
I'm thinking it may be trying to resolve via root hints and you client times out before the DNS server gets the address.  The 2nd time you query, the DNS server resolved the address (after your client timeout) and it is now in the DNS cache on the DNS server so it works.
Have you setup each DNS server forwarders to your ISPs DNS server?
0
 

Author Comment

by:BenBispham1
ID: 26112422
Thank you for that. It doesn't help that I missed that step when I set it up because it just worked... The not resolving then resolving threw me off the scent. Thanks for explaining. I've put the Open DNS servers in there and everything is fixed.
0
 

Author Closing Comment

by:BenBispham1
ID: 31669400
Thanks
0
 
LVL 26

Expert Comment

by:Pber
ID: 26112437
Happy your fixed, glad to help.
0
 

Expert Comment

by:Freda Driscoll-Sbar
ID: 40544301
We addressed the same issue in our environment by removing internal cross-domain name servers from Forwarders and left them as conditional-forwarders only.
0

Featured Post

A Cyber Security RX to Protect Your Organization

Join us on December 13th for a webinar to learn how medical providers can defend against malware with a cyber security "Rx" that supports a healthy technology adoption plan for every healthcare organization.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
A procedure for exporting installed hotfix details of remote computers using powershell
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
Suggested Courses

830 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question