<div>
Do you have the DNS server role installed on your DC brfore doing the promotion? Have you tried to add ADDS and DNS from the Roles, then do dcpromo /adv. <br />
<br />
From there try again and see if you get the same error. <br />
<br />
You can also reference the below link. It describes 2008R2 but same concept applies. <br />
<a href="http://support.microsoft.com/kb/2002584" rel="ugc">http://support.microsoft.com/kb/2002584</a><br />
<br />
<br />
<br />
Will.
</div>


<div>
Microsoft suggests completing the installation, then installing DNS once you've rebooted.<br />
<br />
<a href="http://support.microsoft.com/kb/2002584" rel="ugc">http://support.microsoft.com/kb/2002584</a>
</div>


<div>
DNS and AD DS roles have been installed. &nbsp;Now at the promote part.<br />
<br />
Should I uninstall DNS, leaving AD DS, promote and then install DNS?
</div>


<div>
You should be able to promote the DC with DNS installed. &nbsp;Give it a go. &nbsp;If it doesn't work, fall back to promoting it, then setting up DNS.
</div>


<div>
Do the promotion. Make sure that the your DC is initially pointing to another DC until it has been fully promoted. Once promoted and DNS is installed make the primary DNS server point to itself.<br />
<br />
Will.
</div>


<div>
Your AD domain doesn't have a single-label DNS name (i.e., a name like <b>contoso </b>rather than <b>contoso.com</b>, <b>contoso,local</b>, or something like that), does it?
</div>


<div>
This problem occurs only in child domain if DNS is not setup properly between parent and child domain<br />
If parent DNS and child dns are out of sync, then during DC promotion, you cannot identify its authoritative zone (child domain DNS zone) and that's why DNS is getting grated out.<br />
Let us know if you have Something like below<br />
You have parent domain called xyz.com having replication scope to all domain sin forest<br />
Your child domain must be having xyz.com, but with replication scope to all dns servers in this domain due to some zone deletion, restoration in past. There is xyz.com zone in both domains but totally out of sync <br />
<br />
In that case this is not ideal situation and child domain simply unable to find its authoritative zone registration in AD and DNS is greyed out.<br />
<br />
Mahesh
</div>


<div>
@Mahesh<br />
<br />
Parent domain is xyz.com and there are 2 DCs in this domain. &nbsp;How can I confirm if they are replicating to all domains in forest or just in domain?<br />
Child is pdq.xyz.com and these domains replicate within the domain I believe.<br />
<br />
How can I confirm/correct this?<br />
<br />
I did promote and I it has DNS entries so is there a way to confirm<br />
?
</div>


<div>
You can go to zone properties \ general tab \ replication and check what is selected there ?<br />
<br />
All dns servers in domain or all dns servers in forest. Will tell you there replication scope<br />
<br />
parent domain zone should replicated to all dns servers in its own domain only and child also should replicate to its own domain only as a best practise.<br />
<br />
What is your name resolution strategy between parent and child domains ?<br />
<br />
Check if you have created domain dns delegation on parent DC in parent domain dns zone pointing to child domain and its DC and it do not contains any stale NS records for child DNS servers as DNS delegation is static and NS records need to be manually updated when changed.<br />
Parent domain should have dns delegation pointing to child domain dns server to resolve resources in child domain from parent domain and child domain must be having conditional forwarder on its dns server pointing to parent domain for resolving records in parent domain<br />
Alternatively you can setup secondary zones in both domains pointing to each other for name resolution<br />
Just check with nslookup if both domain DCs can resolve each other.<br />
Alternatively,<br />
Just run below commands on both domains DNS server to verify if both can resolve each other.<br />
In cmd Type nslookup, and then press ENTER.<br />
Type set type=all, and then press ENTER.<br />
Type _ldap._tcp.dc._msdcs.Domai<wbr />n_Name,<br />
Change domain name with parent domain and child domain respectively and it should resolve properly<br />
&nbsp;<br />
<a href="http://support.microsoft.com/kb/816587" rel="ugc">http://support.microsoft.com/kb/816587</a><br />
<br />
if everything is setup as per above then you should not get dns greyed out <br />
<br />
Mahesh
</div>


<div>
So I show on Parent:<br />
Type AD Integrated<br />
Replication: All DNS servers in this forest. &nbsp;Should change this?<br />
Child domain doesn't have properties to check (See attached)<br />
<br />
parent is xy.com<br />
child is uv.xy.com<br />
<br />
How do I confirm delegation settings? &nbsp;No Zone transfers and Name servers for all DCs listed.<br />
Parent preferred is self and alternate child<br />
Secondary Parent DC is self as preferred and primary parent DC as alternate<br />
I have nothing in conditional forwarders folder (see attached)<br />
<br />
so from child nslookup parent domain and vice versa?<br />
<a href="https://filedb.experts-exchange.com/incoming/2014/01_w03/828720/DNS.JPG" target="_blank" class="file-inline" title="screen 1 (68 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>DNS.JPG</a><br />
<a href="https://filedb.experts-exchange.com/incoming/2014/01_w03/828721/DNS2.JPG" target="_blank" class="file-inline" title="screen 2 (27 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>DNS2.JPG</a>
</div>


DNS2.JPG

DNS.JPG

<div>
Please don't change anything right now.<br />
Yes, you have single zone replicated to parent and child domain<br />
That is why you don't have conditional forwarders in child domain and delegation in parent domain as complete zone is replicated to both domains.<br />
<br />
Yes, please do nslookup from child and parent for each other as mentioned in earlier comment for verification.<br />
<br />
Can you just check zone properties on child DC (go to properties of main zone same as parent domain) and can you check there what is the replication scope please<br />
<br />
Mahesh
</div>


<div>
Is how you are saying the best practice for DNS setup?<br />
<br />
from parent DC<br />
&gt;&nbsp;_ldap._tcp.dc._msdcs.north<wbr />america.be<wbr />rgquistcom<wbr />pany.com<br />
Server: &nbsp;parentDC.bergquistcompany.<wbr />com<br />
Address: &nbsp;10.10.x.x<br />
<br />
Name: &nbsp; &nbsp;_ldap._tcp.dc._msdcs.north<wbr />america.be<wbr />rgquistcom<wbr />pany.com<br />
<br />
From child<br />
&gt;&nbsp;_ldap._tcp.dc._msdcs.bergq<wbr />uistcompan<wbr />y.com<br />
Server: &nbsp;childdc.northamerica.bergq<wbr />uistcompan<wbr />y.com<br />
Address: &nbsp;10.10.x.x<br />
<br />
Name: &nbsp; &nbsp;_ldap._tcp.dc._msdcs.bergq<wbr />uistcompan<wbr />y.com<br />
<br />
If I go to DNS on the child and look at the parent domain properties it is the same AD integrated and to all DCs in the forest. &nbsp;Again the child domain is a folder so can't go to properties on the child other than physically I am on the child dc now.<br />
<br />
Thanks again for all your help!
</div>


<div>
It looks like DNS is not according to best practises, but configuration is OK and no change is required as it will inolve some major changes \ steps \ downtime which is not advisable at this point of time.<br />
I have observed that this DNS grayed out problem occcurs offen in child domains only<br />
<br />
Just outline steps here:<br />
Export all records in parent zone under child domain sub folder<br />
Prepare dnscmd batch file (dnscmd /recordadd) for adding host A records in child domain in advance<br />
Change parent zone (domain.com) replication scope from forest to domain !!<br />
<b>Above step will simply delete parent zone from all DCs in child domain</b> -critical step<br />
delete child domain folder from parent dns zone - Force AD replication in parent domain<br />
create dns delegation in parent dns zone on parent DC pointing to child domain<br />
Point child domain PDC to itself in tcp/ip settings - I guess it is already<br />
create child.domain.com ad integrated zone in child domain PDC with replication scope as domain and ADD all child DC as NS records in that zone manually.<br />
Restart netlogon service on child PDC to populate all DNS folders and SRV records in child domain to that zone<br />
Force replication to populate that zone on all child DCs<br />
Create conditional forwarder in child domain PDC pointing to parent domain and its DNS server and store it into active directory<br />
Restore all Host (A) records for resources in child domain with dnscmd batch file created earlier<br />
<br />
All above excercise required extreme care and involves downtime.<br />
<br />
Above outlined steps actually need to be done at very intial stage when you 1st deployed child domain 1st DC in past.<br />
<br />
2008 R2 AD is smart enough to identify this and it will automatiocally create delegation in parent zone on parent DC and create child.domain.com zone in child domain exactly same as stated above in 1st shot<br />
<br />
Hence I suggest you to go with workaround provided by others and keep above in mind in case if you required to create additional child domains in feature<br />
<br />
Mahesh
</div>


<div>
So based on nslookup it appears DNS is working on new child?<br />
<br />
In future Promote then install DNS? &nbsp;And your steps if creating other child domains but for the one I have I must continue as is?
</div>


<div>
<div class="content wysiwyg-content">
Hello EE,<br />
I have a DC that I am trying to introduce into my existing child domain.<br />
Parent domain has 2 DC's <br />
Child domain has 6 DC's (one per branch office)<br />
<br />
I have a 2003 functional level and am trying to replace the 2003 with 2012. &nbsp;I have 2 DCs in with 2012 as of now, but am trying to add another and get that going along side my 2003 and eventually demote the 2003, but when I run the promote wizard it gives me greyed out DNS.<br />
&quot;DNS cannot be installed on this domain controller because this domain does not host DNS&quot;<br />
What is this? &nbsp;I've read other articles but not matching my environment so not sure what to do ?
</div>
</div>


Hello EE,
I have a DC that I am trying to introduce into my existing child domain.
Parent domain has 2 DC's 
Child domain has 6 DC's (one per branch office)

I have a 2003 functional level and am trying to replace the 2003 with 2012.  I have 2 DCs in with 2012 as of now, but am trying to add another and get that going along side my 2003 and eventually demote the 2003, but when I run the promote wizard it gives me greyed out DNS.
"DNS cannot be installed on this domain controller because this domain does not host DNS"
What is this?  I've read other articles but not matching my environment so not sure what to do ?

DNS cannot be installed on this DC because this DC does not host DNS

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.