in the event viewer i have all the

[stevends]

in the event viewer i have all the time the following message
event ID : 5775

description : Deregistration of the DNS record 'gc._msdcs.koek. 600 IN A 140.0.0.150'
failed with the following error:
DNS name does not exist

how can i solve this problem

 

[GrnEyedLdy]

Is your DNS server configured to accept dynamic updates?


Patty

 

[stevends]

yes the dns server accepts dynamic updates

 

[compgirlfhredi]

The Netlogon 5775 error message is logged in the System event log when the Netlogon service on a domain controller cannot deregister an individual resource record. 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.

 

[compgirlfhredi]

REMEMBER:
The Netlogon service can be delayed to ensure that the DNS Server service is up and running for Dynamic DNS registration and query for existing Active Directory domain controllers that are in the DNS server database. Use the DependOnService in the Netlogon and add DNS to the list of LanmanWorkstation and LanmanServer. This delays Netlogon from starting until the DNS Server service on that same computer is started and ready.

NOTE: Only delay the Netlogon service for DNS on a Windows 2000 Server when the DNS service is on the same Windows 2000-based server.