Question 3 of 7
You administer a branch office connected to the main headquarters with WAN link. Servers in the branch
office provide DNS and DHCP services. The company network has multiple domains, with a single domain
representing the branch office.
A DNS server called DC1 at the branch office holds the primary zone for the branch domain but holds no
other zone files. DNS servers at headquarters provide name resolution for hosts in other domains.
One day, you come to work to find a number of customer service complaints. They all report something
similar–clients can resolve local host names, but cannot resolve host names for other domains on the
network.
You contact the enterprise administrator and are told that the IP address for the DNS server that was being
used previously as a forwarder for the branch office has been changed to 10.155.11.15 .
What should you do to fix the problem?
0 Manually configure each client to use 10.155 .11 .15 for name resolution .
0 Change the primary zone on DC1 to an Active Directory integrated zone .
ANSWER: Configure DC1 to forward name resolution requests to 10.155.11.15 .
0 Configure DC1 as a caching-only server.
0 Modify the DHCP scope properties so that clients use 10.155.11.15 for name resolution.
Explanation
DC1 is configured to use forwarders. It sends unresolvable host name requests to a DNS server at headquarters. The IP
address for this server has changed. To fix the problem, modify the configuration of DC1 to identify 10.155.11.15 as a
forwarder.
Changing network clients to use 1 0.155.11.15 for name resolution would mean that all name resolution requests would
be sent across the WAN link. Clients should submit name resolution requests to DC1. If DC1 cannot resolve the name, it
forwards the request to the appropriate server.
Objectives
Objectives for MS 70-41 0:
403 Deploy and configure DNS service
References
LabSim for Windows Server Pro: Install and Configure, Section 5.2.
[Questions.exm 642-201 #126 [32]]