As a domain controller
Netlogon service cannot register or unregister multiple resource records, Netlogon 5781 error messages will be recorded in the system event log. This event description does not contain the name of these resource records. In addition, the event description may also be "NO DNS Servers Are Available" that will misunderstand the contents of "NO DNS Servers Are Are Available", pay attention: Frequently reason for these errors is that the domain controller is a primary DNS server in its TCP / IP property. . When the domain controller is activated using this configuration, the NetLogon service may start before the DNS service is started. Since the Netlogon service must register a record in DNS, the DNS service is not available, so an error may occur. In this case, you can safely ignore these errors because the Netlogon service will try to register these records again after approximately 5 minutes, and will be able to register successfully. However, in this case, there are two ways to avoid these errors: Make sure the domain controller does not reference its own reference as the primary DNS server in its TCP / IP attribute. Configure Netlogon services to make it depend on DNS service. This will cause the Netlogon service to start after the DNS service is started. To do this, run the regedt32 and go to: hkey_local_machine / system / currentControlSet / Services / NetLogon In the right pane, double-click the DependonService value, then add DNS to the next available blank line. Click OK to exit the Registry Editor.
