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.
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 support the resolution of names in fabrikam.com.
The solution must ensure that users in contoso.com can resolve names in fabrikam.com if the WAN link fails.
What should you do on Server1?
A.
Create a stub zone.
B.
Create a secondary zone.
C.
Add a forwarder.
D.
Create a conditional forwarder.
Explanation:
to me none of the answers is correct !
indeed, in spite of the correct comment below, zones here are AD-integrated zones, so no secondary zone is
possible (and so far there’s nothing new about thatin 2012)
but let’s say that a secondary zone is the only answer that meets the WAN link failure requirement.
so let’s imagine that they imply the modification of the zone type on Server2 to a standard primary zone first
(before configuring a secondary zone on server1)
=========
OLD EXPLANATIONS
http://technet.microsoft.com/en-us/library/cc771898(v=ws.10).aspx
Stub zone doesn’t host the records themselves
Forwarder and conditional forwarders simply give instructions on where to forward DNS requests to.
http://technet.microsoft.com/en-us/library/cc779197%28v=ws.10%29.aspx
States STUB-ZONES.
Is still valid.
Answer must be A.
read carefully and check what a stub zone consists of.
just does not work if WAN link fails…
B is only answer possible
The answer is Create a Secondary Zone. The key is users must resolve names if the WAN link fails. According to https://technet.microsoft.com/en-us/library/cc775397(v=ws.10).aspx DNS will stop using the Stub zone data if it can’t get updates.
Stub zone updates involve the following conditions:
• If an update fails, the Retry interval of the SOA resource record determines when the update is retried.
• Once the Retry interval has expired without a successful update, the expiration time as specified in the Expires field of the SOA resource record determines when the DNS server stops using the stub zone data.
What’s the point of being able to resolve names for a remote site if the WAN link goes down? If the link goes down you can’t get to any hosts on the other side of it anyway; even if you resolve the name it’s just going to time out trying to connect to an unreachable host. I think if you saw a question like this on the test, the condition would be more along the lines of minimizing traffic over the WAN link.
What I’d like to know is: when Active Directory replicates the DNS database for a given zone, is it replicated to just the one domain or the entire forest? If it replicates to the domain, you would need to create a stub zone. If replication is forest-wide, you wouldn’t have to do anything since the DNS database would already replicate as part of normal Active Directory replication.
I didn’t see the point of this either. If you have an alternate route to reach the servers if the WAN link goes down, then that link should work for DNS as well. And if you don’t have an alt route, what’s the point?
None of the answers seem to work. AD-integrated zones are all primary zones, and none of the other options would work if the link is down.