Event ID: 5774
Source NETLOGON
Type Error
Description Registration of the DNS record '_gc._tcp.Default-First-Site._sites.. 600 IN SRV 0
100 3268 .' failed with the following error: .
Comments Darren Kennedy: See the link below to Registry Tweaks for a description of the problem.
Adrian Grigorof: Error: "DNS server unable to interpret format." - This error message may be generated in several circumstances. See Q259277 for a general approach on troubleshooting this. In some cases this may be caused by the security setting on the parent.local server being set to only use secure updates. Changing this to allow "dynamic updates" (instead of only secure) might eliminate the problem.
Another newsgroup discussion thread suggested that the event was caused by the fact that the Active Directory Domain Controller running the DNS server did NOT point to itself as a DNS server (instead it used the ISP DNS servers). Changing the DNS server settings to point to itseld fixed the problem.
Joakim Bengtsson: I found that delaying startup of Netlogon service until DNS was started solved this problem. Just add DNS to the DependOnService entry in HKLM-System-CurrentControlSet-Services-Netlogon. This is described among other things in Q193888.
Sven Jedeck: This event can occur when the IP address of the server is changed.
Daniel Hamilton: This Error occurs when DNS Server has its database in Active Directory Integrated mode, and is also a Domain Controller and network adapters have been changed in the system. Fix: Delete affected zones and recreate the zones. This will allow the NETLOGON service to successfully re-register the records that were being reported in the 5774 event.
PeterI: Error: "DNS RR set that ought not exist, does exist." - This can be caused by someone manually creating an alias for that namespace (in this case test.com). If none of the published fixes addresses your problem, try this instead. Open the DNS console from the MMC and expand the primary dns server. Select Forward Lookup Zones and select the target zone (test.com). There you should see an A (alias) or CNAME record. Delete it, then stop and start the netlogon service.
Johannes (Jazzy) Nielsen: Error: "DNS operation refused." - The problem was the time it took logging on to the W2K server, the clients were not able to find the server and waited up to 30 min. before logging on. This was solved by configuring the internal DC as DNS servers instead of the ISP DNS.
E Soden: I had my DNS server setup as a root server, which it is not. Go to the Computer Management Console DNS snap-in and drill down to the Forward Lookup Zones. If there is a DOT zone listed "." then your server is setup as a root server. Deleting the Root zone got rid of the error message.
Links Q259277 , Q284963 , www.microsoft.com/TechNet/win2000/win2ksrv/reskit/tcpch06.asp, Q193888 , Registry Tweaks, Q265706
