You deploy an Active Directory domain named contoso.com to the network. The domain is
configured as an Active Directory-integrated zone. All domain controllers run Windows
Server
2012 and are DNS servers.
You plan to deploy a child domain named operations.contoso.com.
You need to recommend changes to the DNS infrastructure to ensure that users in the
operations department can access the servers in the contoso.com domain.
What should you include in the recommendation?
A.
A zone delegation for _msdcs.contoso.com
B.
Changes to the replication scope of contoso.com
C.
Changes to the replication scope of _msdcs.contoso.com
D.
Changes to the replication scope of operations.contoso.com
Explanation:
http://support.microsoft.com/kb/255248
Manually Create a Delegation for the Child Domain on the Parent (Root) DNS Server
1. Right-click the root zone, click New Delegation, and then click Next.
2. Type the domain name for the child domain, and then click Next.
3. Add the child DNS server to host the new zone, and then click Next. NOTE: A domain
controller that is a DNS server should have a static Transport Control Protocol/Internet
Protocol
(TCP/IP) address. Verify that this step is performed before you install DNS on the child
domain controller. If no DNS TCP/IP address exists, DNS is installed as a root server. If you
see that a
“.” folder is created after you install DNS, you must remove the root configuration. For
additional information about how to do this, click the article number below to view the article
in the Microsoft Knowledge Base:
229840 DNS Server’s Root Hints and Forwarder Pages Are Unavailable
4. On the child domain DNS server, right-click My Network Places, and then click Properties.
5. Right-click the appropriate local connection, and then click Properties.
6. Under Components checked are used by this connection, click Internet Protocol (TCP/IP),
and then click Properties.
7. Click Use the following DNS server addresses:, and then type the TCP/IP address of the
parent (root) DNS server.
How to create a DNS Parent-Child Delegation
By default, the parent.com zone’s Replication scope is set to domain-wide. This is the middle button in the zone’s replication scope properties that says “All DNS Servers in the Domain”. This means it is only available to the parent.com’s DC/DNS servers, and not to any of the child domain’s DC/DNS servers. So if you were to set the child domain DCs to use themselves as DNS, they will not find their own zone.
To overcome that, as mentioned above, you have two basic parent-child design choices:
.
1. Centralized – No delegation
If you want to use themselves for DNS in the parent and child domains, and to simplify it, you can change the parent.com zone’s Replication scope to Forest DNS Servers.
This way the zone will be available to all DC/DNS servers in the whole forest. The following link shows how to check and/or change replication scopes, that is if this is the desired design based on your company’s requirements.
How to change replication scopes: