NS Lookup

[WaferITMan]

I am having trouble with nslookup. I currently have 3 DNS servers 2 internal and 1 forwarding to an external DNS. When doing an nslookup against an IP address or domain (

http://www.yahoo.com,

216.109.118.66). It fails the first we try's. I receive the following error.

DNS request timed out.
timeout was 2 seconds.
*** Request to XX.XX.XXX.com timed-out

After the 2nd or 3rd try it resolves the address.

Any ideas to what is causing this delay?

thanks.

Mike

 

[GlenJohnson]

1) How long has this been going on? Has it ever worked?
2) Have you checked you're log files for error messages?
3) When it fails, what does ipconfig /all show?
4) How is you're dns setup? Who are the dns servers pointing to, and who are the clients pointing to.
5) What machines are the nslookup failing, servers or clients?
Good luck, and the awnsers to the above questions will help us sort it out.

Click here to learn How to help with tsunami relief...

http://www.google.com/tsunami_relief.html

Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin feel free to join the Tek-Tips in Chicago, Illinois Forum.
Don't forget to shop @ theTek-Tips Store

 

[WaferITMan]

Thank you for your help. The answers to your questions are listed below.

1) How long has this been going on? Has it ever worked?

It was never working. I recently setup forwarding and it forwards but only after three tries.

2) Have you checked you're log files for error messages?

Yes, no errors.

3) When it fails, what does ipconfig /all show?

The ipconfig looks normal. The DNS suffix is correct and the DNS sever is correct.
4) How is you're dns setup? Who are the dns servers pointing to, and who are the clients pointing to.

3 DNS servers. They are used for internal resolution. One has a forwarder to an external DNS(Server C). The other 2 servers are forwarded to (Server C). Clients are to pointing to server A, server B.

5) What machines are the nslookup failing, servers or clients?

All are experiencing the same issue. I tried pointing to different DNS servers and all have the same problem.

I hope this information can resolve this issue.

Thanks.

 

[ChrisAC]

Is this just an issue with resolving external DNS or internal as well? Do you have this issue on Server C?

Are these Windows DNS servers or BIND servers?

And finally, why use a forwarder on Server C?

Chris.

**********************
Chris A.C, CCNA, CCSA
**********************

 

[WaferITMan]

Thanks for the quick response. This issue only occurs when resolving external addresses. Issue happens on all DNS Severs

We are currently running win2k3 DNS.

I am forwarding to server C because it is the only server that has internet access.

I hope this helps.

Thanks.

 

[grimmy26]

can you telnet to the external DNS server using port 53?

 

[WaferITMan]

Yes, I can telnet to port 53. It does resolve DNS but only after three trys.

Very odd.

Thanks.

 

[ChrisAC]

When I mentioned forwarding, I meant why does server C forward DNS requests to another DNS server on the internet? It may be having issues with the server that it's forwarding all its requests to? Have you tried it without a forwarder? It may work better doing its own resolution.

Chris.

**********************
Chris A.C, CCNA, CCSA
**********************

 

[WaferITMan]

YOU ARE THE MAN! The removal of the forwarders did the trick.

Thanks for the help.

 

[ChrisAC]

No problem!



Chris.

**********************
Chris A.C, CCNA, CCSA
**********************