Netlogon Event ID: 5774 We renamed a Windows 2003 domain and after completing successfully, we found that the DNS records are still being registered for the Old Domain Name.
Environment: Windows Server 2003 R2
Renaming domain is a complex task, ensuring all the functionality in Domain to remain working. However, in this particular environment, we follow everything by the book. Unfortunately, something was still not done properly, and finally we started to dig deeper to find what went wrong. Primarily we noticed the following event in the logs to start our troubleshooting with:
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5774
Time: 4:02:57 AM
The dynamic registration of the DNS record ‘_kpasswd._udp..com. 600 IN SRV 0 100 464 NewDC..com.’ failed on the following DNS server:
DNS server IP address: x.x.x.x
Returned Response Code: 9
Returned Status Code: 9009
For computers and users to locate this domain controller, this record must be registered in DNS.
Determine what might have caused this failure, resolve the problem, and initiate registration of the DNS records by the domain controller. To determine what might have caused this failure, run DCDiag.exe. You can find this program on the Windows Server 2003 installation CD in Support\Tools\support.cab. To learn more about DCDiag.exe, see Help and Support Center. To initiate registration of the DNS records by this domain controller, run ‘nltest.exe /dsregdns’ from the command prompt on the domain controller or restart Net Logon service. Nltest.exe is available in the Microsoft Windows Server Resource Kit CD.
Or, you can manually add this record to DNS, but it is not recommended.
Error Value: DNS server not authoritative for zone.
Resolution: The easiest fix we found to this problem was to run “random /clean” again. Yes, we did run it first time as well, but may have over looked the results on the first place. However, as we were advised, ran this command again against all the Domain Controllers in the following format.
Once we ran the above command against all the domain controllers, we were able to successfully register the proper DNS records for the New Domain.
Latest posts by Rishi Chaudhary (see all)
- ShadowCopy Backup after renaming VSSADMIN.EXE - October 5, 2016
- No Network Connection after Windows 10 Upgrade – Fixed - August 25, 2015
- Windows 10 System Tray Notification Issue - August 7, 2015