Your network contains an Active Directory forest. The forest contains two domains named
contoso.com and fabrikam.com. All of the DNS servers in both of the domains run Windows
Server 2012 R2.
The network contains two servers named Server1 and Server2. Server1 hosts an Active
Directory-integrated zone for contoso.com. Server2 hosts an Active Directory-integrated
zone for fabrikam.com. Server1 and Server2 connect to each other by using a WAN link.
Client computers that connect to Server1 for name resolution cannot resolve names in
fabrikam.com.
You need to configure Server1 to resolve names in fabrikam.com. The solution must NOT
require that changes be made to the fabrikam.com zone on Server2.
What should you create?
A.
A trust anchor
B.
A stub zone
C.
A zone delegation
D.
A secondary zone
Explanation:
A stub zone is a copy of a zone that contains only those resource records necessary to
identify the authoritative Domain Name System (DNS) servers for that zone. A stub zone is
used to resolve names between separate DNS namespaces. This type of resolution may be
necessary when a corporate merger requires that the DNS servers for two separate DNS
namespaces resolve names for clients in both namespaces.
a stub zone
0
0
really never understood when to use zone delegation vs stub zones. both do the same thing.i assume delegation is for child domains
0
0
@Kurt – You would normally use zone delegation if you “managed” (owned) the parent namespace. That way you can control who YOUR DNS servers are allowing to “own” a child zone namespace. Anyone could still create a standard primary zone with the same child namespace, but anyone using your DNS for resolution (starting with your parent zone) would not be able to find it.
Stub Zones (or conditional forwarders) are generally used for resolving disjointed namespaces during integration, migrations, etc.
Had CONDITIONAL FORWARDER been an option, both Forwarder and Stub Zone would have been correct answers.
0
0