DNS Not resolving properly 1

[kwei]

Hello,

One of my servers DNS does not seem to be functioning properly. I first noticed it when some users started complaining about slow loading of websites they visited (msn.com, cnn.com, etc). The server is a Single DC for 20+ workstations. I have DHCP and DNS enabled. The servers DNS is configured as the DNS server for itself, and provides DNS for the entire domain. DHCP makes sure of this and is working properly.

I did a test running nslookup from the command prompt, the output was as follows:
C:\Documents and Settings\Administrator>nslookup msn.com
Server: lakeserv.lakeo.ssm.local
Address: 172.17.17.4

DNS request timed out.
timeout was 2 seconds.
*** Request to lakeserv.lakeo.ssm.local timed-out

I'm not sure why this started happening. A couple weeks ago everyting was working fine. No changes to the server were made by myself. I am the only one who would make them. Last night I removed my forward and revers lookups from DNS and then re added them to see if that would help, it has not seemed to. There are a couple errors Under DNS. error 4004 source DNS. This error has occurred before in the past and on other servers and to my knowledge did not cause this problem. One other thing I tried doing was running dcdiag. Everything passed except for syslog. Syslog always seems to fail though. Thanks for any help!

Justin

 

[micronmega]

My guess is you are using forwarders to get your external resolution done, i'd start there. From the DC can you ping the forwarder DNS servers you have setup? If so try it with a small load, add a -l(that's a lowercase L) 1500 to the end of the ping, you might be getting latency trying to talk to the External DNS servers.

 

[kwei]

Micronmega, thanks for the advice. It looks like that *might* have done the trick, nslookup is working now. Web pages are still loading a little slow, but I'll give it a day and see if it improves in a bit, maybe do a /flushdns. Good tip, should have thought of that one. Looks like the servers I had forwarding to in there were no longer valid (thx to my ISP changing them w/o telling me). Thx again!!

Justin