Well, then I wouldn't concern myself. It isn't a MAJOR error -- dcdiag, netdiag, and dnslint are happy. Do your upgrade and let's clean up the other stuff later.
Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -----Original Message----- From: Michael Leone [mailto:[email protected]] Sent: Wednesday, March 03, 2010 9:26 PM To: NT System Admin Issues Subject: Re: Yet another DNS question On Wed, Mar 3, 2010 at 4:57 PM, Michael B. Smith <[email protected]> wrote: > Ya got me. Did you read here? > > http://eventid.net/display.asp?eventid=4010&eventno=791&source=DNS&pha > se=1 I did. And I haven't tried that "scorched earth" suggestion, about deleting the netlogon.dns.db files. Or deleting and re-creating the forward lookup zone, which is the zone for the parent domain. That just sounds very scary, especially if that doesn't cure the problem. I'd hate to find that I made the problem worse, by trying to fix it ... ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
