Intermittent NSLOOKUP failures (long)

[dsturgeon]

I have 3 DNS servers, 2 new W2K3 and one NT4. If I use either one of the 2 new W2K3 servers to do an NSLOOKUP query for a given internal machine name, I receive back a ***request to %servername% timed out*** response. I can set the timeout value to 20 seconds and it still doesn't matter, I get the same result. If I perform the query using
the machine IP address I receive the response immediately resolved to the machine name, so the reverse lookups are functioning. If I switch to the NT4 server all of the query results are returned as they should be. If I set the type=any, then I do receive a response with the correct machine name. The forward zone queries to the W2K3 servers do function on some machines, just not all of them. The logs are clean on the servers.

More info- I launched the network monitor and ran a capture while testing various name lookups. If I launch NSLOOKUP and run a query for my machine, there are no responses sent from the DNS server to my machine. I can
send name requests for external hosts (google, msn, etc) and they are returned. If I set the query type=any, I then receive responses from the name server for my local machine. This is an intermittent issue, it functions correctly on some machines and does not function correctly on others (like mine).

Any thoughts?

 

[ChicagoTechNet]

this may help. quoted from

http://www.chicagotech.net/

Can't find server name for ....: No response from server - DNS Request Timed Out

Symptom: When running nslookup, you may receive this message: Can't find server name for ....: No response from server

Cause: the DNS server's reverse lookup zones do not contain a PTR record for the DNS server's IP address.


Robert Lin, MS-MVP, MCSE & CNE
Windows, Network, Internet, VPN, Routing and How to at

http://www.ms-mvps.com

 

[dsturgeon]

The forward and reverse zones all have entries for the 3 servers and the workstation that I am trying to look up.

Fish

"Your worst day is only 24 hours long"