Dynamic registration or deletion of one or more DNS records associated with DNS domain ‘%1’ failed. These records are used by other computers to locate this server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition). Possible causes of failure include: – TCP/IP properties of the network connections of this computer contain wrong IP address(es) of the preferred and alternate DNS servers – Specified preferred and alternate DNS servers are not running – DNS server(s) primary for the records to be registered is not running – Preferred or alternate DNS servers are configured with wrong root hints – Parent DNS zone contains incorrect delegation to the child zone authoritative for the DNS records that failed registration USER ACTION Fix possible misconfiguration(s) specified above and initiate registration or deletion of the DNS records by running ‘nltest.exe /dsregdns’ from the command prompt or by restarting Net Logon service. Nltest.exe is available in the Microsoft Windows Server Resource Kit CD.

Details
Product:	Windows Operating System
Event ID:	5781
Source:	NetLogon
Version:	5.2
Symbolic Name:	NELOG_NetlogonDynamicDnsServerFailure
Message:	Dynamic registration or deletion of one or more DNS records associated with DNS domain ‘%1’ failed. These records are used by other computers to locate this server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition). Possible causes of failure include: – TCP/IP properties of the network connections of this computer contain wrong IP address(es) of the preferred and alternate DNS servers – Specified preferred and alternate DNS servers are not running – DNS server(s) primary for the records to be registered is not running – Preferred or alternate DNS servers are configured with wrong root hints – Parent DNS zone contains incorrect delegation to the child zone authoritative for the DNS records that failed registration USER ACTION Fix possible misconfiguration(s) specified above and initiate registration or deletion of the DNS records by running ‘nltest.exe /dsregdns’ from the command prompt or by restarting Net Logon service. Nltest.exe is available in the Microsoft Windows Server Resource Kit CD.

Explanation
DNS records for the DNS domain could not be dynamically registered or deleted. Possible causes include: The TCP/IP properties of this network connection contain incorrect IP addresses for the preferred and alternate DNS servers. The preferred and alternate DNS servers are not running. The preferred or alternate DNS servers are configured with the incorrect root hints. The parent DNS zone contains incorrect delegation information for the child zone that is authoritative for the DNS records that could not be registered.

User Action
To initiate dynamic registration or deletion of the DNS records, do the following: Verify that the TCP/IP properties are configured with the correct IP addresses. Verify that the DNS servers are running. Verify that the DNS servers are configured with the correct root hints. Verify that the parent DNS zone contains the correct delegation information. At the command prompt, typenltest.exe /dsregdnsThe Nltest.exe program is available on the Microsoft Windows Server 2000 Resource Kit CD.

Process (PID=). Error DNS_ERROR_RCODE_NAME_ERROR (0x) occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain The query was for the SRV record for Common causes of this error include the following:- The DNS SRV records required to locate a domain controller for the domain are not registered in DNS. These records are registered with a DNS server automatically when a domain controller is added to a domain. They are updated by the domain controller at set intervals. This computer is configured to use DNS servers with following IP addresses:- One or more of the following zones do not include delegation to its child zone:For information about correcting this problem,
The PrintQueue Container could not be found because the DNS Domain name could not be retrieved. Error: %1
The DNS server was unable to complete directory service enumeration of zone %1. This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empty) is “%2”. The event data contains the error.
The DNS server encountered a packet addressed to itself on IP address %1. The packet is for the DNS name “%2”. The packet will be discarded. This condition usually indicates a configuration error. Check the following areas for possible self-send configuration errors: 1) Forwarders list. (DNS servers should not forward to themselves). 2) Master lists of secondary zones. 3) Notify lists of primary zones. 4) Delegations of subzones. Must not contain NS record for this DNS server unless subzone is also on this server. 5) Root hints. Example of self-delegation: -> This DNS server dns1.example.microsoft.com is the primary for the zone example.microsoft.com. -> The example.microsoft.com zone contains a delegation of bar.example.microsoft.com to dns1.example.microsoft.com, (bar.example.microsoft.com NS dns1.example.microsoft.com) -> BUT the bar.example.microsoft.com zone is NOT on this server. Note, you should make this delegation check (with nslookup or DNS manager) both on this DNS server and on the server(s) you delegated the subzone to. It is possible that the delegation was done correctly, but that the primary DNS for the subzone, has any incorrect NS record pointing back at this server. If this incorrect NS record is cached at this server, then the self-send could result. If found, the subzone DNS server admin should remove the offending NS record. You can use the DNS server debug logging facility to track down the cause of this problem.
Event ID 2630 — DNS Server Autoconfiguration

Related:

Leave a Reply Cancel reply

Links