DNS Event ID 4013 on Server 2008 Domain Controller/DC
NOYNIM specializes in IT Consulting Denver, and we strive for perfection all of the time. One of our focuses is cloud, off-premise and on-premise infrastructure. After a domain controller reboot we noticed that it took the DC 45 minutes to reboot and about 20 minutes to log into the server. Further investigation lead us to an event ID of 4013 in the DNS logs.
Event ID 4013 was present on one out of our five domain controllers at a client. We did a lot of research and found many articles relating to DNS modifications and registry changes.
Microsoft recommends that you set your primary DNS to the IP of itself on a DNS server. For example, if the DC is 192.168.0.1 then the primary DNS should be 192.168.0.1. We changed the primary IP to another DC, restarted DNS and everything worked out properly. Hope this helps some other folks out there on the internet with this issue.
Below is the log:
Log Name: DNS Server
Event ID: 4013
Task Category: None
The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.