Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I seem to have an issue with our AD/DNS, the structure looks like:

screen from DNS

but the BPA gives me an error:

The Active Directory integrated DNS zone _msdcs.<domain> was not found.

DNS queries for the Active Directory integrated zone _msdcs.<domain> might fail.

Restore the Active Directory integrated DNS zone _msdcs.<domain>

Now we've got 4 DC's in total: 2 running Server 2008 R2, 2 running Server 2003. The older ones will be retired sometime this year. Actually everything seems to be working ok (if something isn't then we don't know about it), we've got quite a few .NET applications authenticating against AD, no DNS issues from what I can tell and various bits on the network point to all 4 controllers.

Furthermore a dcdiag /dnsall comes up with all passes. Is this something I should be worried about?

share|improve this question
up vote 2 down vote accepted

Well, notwithstanding the fact that a Google search for The Active Directory integrated DNS zone _msdcs.<domain> was not found would have told you the same thing, much faster...

This is an issue you see in domains created under Windows 2000 and elevated to 2008, that doesn't actually usually create problems. (But it's pretty trivial to correct, so you may as well correct it, right?) See this thread here, Tim Baldwin's answer (mostly quoted below) is correct.

Win2000 implemented _msdcs as a subfolder of the DNS zone. The recommended config for 2003 and 2008 AD-Integrated DNS zones, is that _msdcs be moved to a separate AD-integrated primary zone as _msdcs.ForestFQDN. However, the zones created in 2000 are not changed to this config when DNS is upgraded or migrated 2003 or 2008.

To fix this you need to manually create a new "separate"active directory integrated primary zone _msdcs.ForestFQDN and remove the old subfolder under the existing primary zone. (after successful config and replication). Then run your best practices analyzer in 2008R2 and see the problem is no longer...

share|improve this answer
It seems my google powers are fading... thanks for your help. – hyp Sep 26 '12 at 10:07

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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