Citation :
Bjarni Thor: I had this test machine that was a DC running DNS. I was getting this error, every two hours. I got rid of this error as follows:
1. In the TCP/IP properties of the machine I selected "Advanced" and then "DNS"
2. In the "DNS server addresses, in order of use:" I put the IP of my DNS server at the top, then the forwarders.
Before the 5781 I was getting the 5782 error - for that I made the recommended changes in the registry:
Key: HKEY_LOCAL_MACHINE\Systems\CurrentControlSet\Services\Netlogon\Parameters
Create a new DWORD value and name it: DnsUpdateOnAllAdapters. Set the value to 1.
Adrian Grigorof: This error may occur in several circumstances. See Q259277 for a general approach on troubleshooting this error message. The event can also be caused by start of NETLOGON service before DNS if hosted on same Domain Controller - see Q193888 - adding DNS as a dependency for Netlogon service - (link below) One particular condition is when a DNS server running BIND is used a forwarder in a Windows 2000-based DNS. Due to its behavior on caching DNS records, a response to a DNS query made by a Windows 2000 server to dynamically register a client computer name may appear as not being authoritative (even if it is). In this case the Windows 2000 server informs the client that the request failed. As per Microsoft, this problem was fixed with SP1.
Henry Sayer: Microsoft's KB article Q311354 only tells you half the story, there is another file called netlogon.dnb that holds those records. That file should be removed as well as doing what Q311354 tells you to do. Stale resource records now disappear for good.
|