That is the same thing I thought, but I decided to clear the cache before restarting the DNS server service just for kicks, and it remedied the problem. Why would a DNS request timeout for cnn.com when it was working on other DNS servers? I could uderstand if it was just returning the wrong address but not timing out. And clearing the cache fixed it how? Do DNS records somehow get corrupt (in which case clearing the cache fixes the problem by querying something farther up the chain again)? Any insight is appreciated, I just hate not knowing the cause of a problem.
________________________________ From: [EMAIL PROTECTED] on behalf of Grillenmeier, Guido Sent: Wed 11/17/2004 6:28 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] AD integrated DNS one way of clearing the cache is to restart the DNS service - not sure if that's really your problem though. Shouldn't really have to remove records from the cache unless the target ip-address has changed. /Guido -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Douglas M. Long Sent: Wednesday, November 17, 2004 4:10 PM To: [EMAIL PROTECTED] Subject: [ActiveDir] AD integrated DNS What settings are recommended for 2003 AD integrated DNS? Automatic scavenging? If so, how frequently? Is there a way to automatically clear the cache on the server every night, or do you just have to add a task to task scheduler to do it? Would there be anything wrong with clearing the cache every night? The reason I ask is because nslookups were timing out for cnn.com today, and clearing the cache on the DNS server fixed it. List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
<<winmail.dat>>
