5

Server 2012 R2 (before the 2nd DC is added)

There are an amazing number of web pages that attempt to address Event ID 4013 including these on serverfault: link1, link2, link3 (though this last post is for multiple DC's). This last link even recommends to hack the registry to turn off this check but Microsoft strongly recommends against that for a production network in this link. Even though that last link is for Server 2003 I assume and think this recommendation still applies.

I'm getting this error after having just created the first DNS server on the domain and I'm trying to resolve the important errors before moving on. Having studied this Event ID much I'd like to ask about the last line of the General comments which says:

"This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed."

Doesn't this really mean if the error doesn't show up 2 minutes later the problem is resolved, so I can really ignore this error if it only occurs when this server has to be rebooted/restarted such as after a UPS commanded shutdown, etc.? Or are there scenarios where I really need to keep searching for the issue?

6

Yes you may safely ignore it, unless it keeps happening repeatedly long after the domain controller/DNS server has rebooted.

The warning should only occur when you reboot the domain controller or otherwise restart AD and DNS.

The reason this happens is simple - DNS hosts Active Directory-integrated zones, and therefore cannot finish initializing until Active Directory is up and running and healthy. But since you just rebooted, Active Directory is not finished starting yet. But Active Directory can't finish starting without access to a DNS server. So you see, AD and DNS are waiting on each other. (But eventually, a timeout occurs, a warning event is logged, and AD and DNS will eventually both start normally.)

The correct way to avoid this issue is to have more than one domain controller, and have each domain controller point to the other as its primary DNS resolver.

But if you're unwilling to add another domain controller to your environment, then you can safely just live with the warning events.

  • Perfect explanation and confirmation. Thx. See my comment below to Joe re your advice about the 2nd DC. – Alan Jul 9 '15 at 16:39
3

This is fairly normal for a single DC environment, due to the order and nature of components as they start up (the networking stack, DNS and AD) and the reliance of AD on DNS.

Do you see Event ID 4 and 2 after the Event ID 4013? If so, then everything is OK.

As a best practice, you should have at least two Domain Controllers and each Domain Controller should use it's partner DC for primary DNS, itself for secondary DNS and 127.0.0.1 as tertiary DNS.

  • I do not see Event ID 4 & 2 at all. I had read about those but since I don't have them I didn't know how to process that info. But thanks for confirming the lack of those 2 Event ID's is a good sign. I will be bringing up a 2nd DC sometime soon, but since everything 'cratered' once, I'm taking things a little more slowly since this is no longer a test environment but rather it will become my production environment. Will do regarding secondary/tertiary DNS. I will also post a question about tertiary DNS in a different thread. – Alan Jul 9 '15 at 16:40
  • To be clear, you're looking at the DNS Server event log, correct? – joeqwerty Jul 9 '15 at 16:46
  • I'm clicking on Server Manager > DNS and looking in the Events listing. – Alan Jul 9 '15 at 17:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.