Question : First NSLookup always times out

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
   

Answer : First NSLookup always times out

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?