A common cause for these errors is that a domain controller references itself as a primary DNS server in its TCP/IP properties. When the domain controller starts in this configuration, the Netlogon service may start before the DNS service starts. Because the Netlogon service must register records in DNS and the DNS service is not yet available, errors may occur. In this situation, you can safely ignore the errors because the Netlogon service will again try to register the records in approximately five minutes, at which time it will be successful. However, there are two ways to avoid the errors in this scenario:

  • Make sure that domain controllers do not reference themselves as a primary DNS server in their TCP/IP properties.
  • Configure the Netlogon service to depend on the DNS service. This will cause the Netlogon service to start after the DNS service starts. To do this, run REGEDT32, and go to:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon

    In the right pane, double-click the value DependOnService and add DNS to the next available blank line. Click OK and exit Registry Editor.

Ref: http://support.microsoft.com/kb/259277

Leave a Reply

Your email address will not be published.


*