I have two Server 2012 Domain Controllers. Each has DNS and DHCP with failover. The NIC properties of each server have the primary DNS pointing to the other server and the secondary DNS pointing to itself (127.0.0.1).
When I reboot these servers...or when I restart the Netlogon service and DNS service in that order, I get three event 5781 NETLOGON warnings...
-
Dynamic registration or deletion of one or more DNS records associated with DNS domain 'company.local.' 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 on the domain controller or by restarting Net Logon service on the domain controller.
-
Dynamic registration or deletion of one or more DNS records associated with DNS domain 'DomainDnsZones.company.local.' 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 on the domain controller or by restarting Net Logon service on the domain controller.
-
Dynamic registration or deletion of one or more DNS records associated with DNS domain 'ForestDnsZones.company.local.' 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 on the domain controller or by restarting Net Logon service on the domain controller.
Also, under my Forward Lookup Zones, I have a _msdcs.company.local zone. Then, under the company.local zone I have a greyed _msdcs. The greyed _msdcs contains the two DCs. This greyed _msdcs did contain the name of a demoted DC but I replaced it with our two current DCs. I found a post online where it was recommended to delete the greyed _msdcs and the _msdcs.company.local zone and restart the netlogon service to recreate these. Don't know if that applies in my case.
My Reverse Lookup Zone does not have a PTR record for the two Name Servers. It just has the two NS records. Any ideas?