WIN 2000 DNS Unresponsive

[tylan]

Has anyone ever seen DNS on WIN 2000 SP4 go unresponsive? One of our DCs will randomly go unresoponsive - - no dns queries will be responded to - - whether you test with a local name or an internet name. A restart of the DNS service solves the problem.

Ideas?

 

[chipk]

Are there any events in your logs that correspond with the stop? This could probably be anything from a non-ascii character somewhere to a leaky process.

 

[tylan]

No, event logs are clean. It's a mysterious stop. The dns service is still running, but it's not responding to queries.

 

[chipk]

Is it pointing to itself as a primary or secondary DNS server? I've seen hotfixes for these types of problems, but only for very specific behavior.

 

[tylan]

Pointing to itself(10.0.0.10) as primary and the other DC as secondary(10.0.0.20). Also, it is an AD intergrated zone. The troublesome machine is W2K Std SP4 and the other DC is 2003 Std SP1.

Also, this server hasn't given me problem at all in the past.

 

[chipk]

You might try looking at some of the troubleshooting tools found here:

http://technet2.microsoft.com/Windo...6ba0-4f08-b1d9-525bf949fa761033.mspx?mfr=true

Specifically, dcdiag and netdiag. See if they turn anything up.

If there are no errors on the server, I'm thinking it's just a leaky process. Is anything unusual about the dns process when the trouble occurs? (dns.exe)

And can you perform name resolution on the server itself when the problem occurs, or is it just clients who have the problem?

 

[tylan]

Honestly, I haven't seen it happen that often. It's happened when some of the other staff members have been on call. Basically, we were concerned about getting DNS working rather than troubleshooting. The last time this issue occurred the net admin just restarted the DNS service. I guess we need to take some more time next time it happens.

I've run dcdiag and netdiag during normal circumstances and everything passes. Now I have to wait for DNS to break!

 

[chipk]

I'd get some real-time monitoring going using perfmon.msc or do some occasional queries with home-grown scripts. That way when it breaks you can look for weirdness in your performance logs.

 

[technome]

I go along with KipK, look for a leaky process other than DNS. Dns generally is one of the first things to go with leaks.


........................................
Chernobyl disaster..a must see pictorial

http://www.kiddofspeed.com/default.htm