Your network contains an Active Directory domain named contoso.com. The network contains 500 client
computers that run Windows 8. All of the client computers connect to the Internet by using a web proxy.
You deploy a server named Server1 that runs WindowsServer 2012. Server1 has the DNS Server server role
installed.
You configure all of the client computers to use Server1 as their primary DNS server.
You need to prevent Server1 from attempting to resolve Internet host names for the client computers.
What should you do on Server1?

A.
Create a zone delegation for GlobalNames.contoso.com.

B.
Remove all root hints.

C.
Create a stub zone named “root”.

D.
Create a primary zone named “root”.

Explanation:
When a zone that this DNS server hostsis a stub zone, this DNS server is a source only for
information about the authoritative name servers for this zone. The zone at this server must be obtained from
another DNS server that hosts the zone. This DNS server must have network access to the remote DNS server
to copy the authoritative name server information about the zone.
Note:
You can use stub zones to:
* Keep delegated zone information current. By updating a stub zone for one of its child zones regularly, the
DNS server that hosts both the parent zone and the stub zone will maintain a current list of authoritative DNS
servers for the child zone.
* Improve name resolution. Stub zones enable a DNS server to perform recursion using the stub zone’s list of
name servers, without having to query the Internet or an internal root server for the DNS namespace.
* Simplify DNS administration. By using stub zones throughout your DNS infrastructure, you can distribute a list
of the authoritative DNS servers for a zone withoutusing secondary zones. However, stub zones do not serve
the same purpose as secondary zones, and they are not an alternative for enhancing redundancy and load
sharing.
Incorrect:
Not A:
* The DNS Server Role in Windows Server 2008 now supports the GlobalNames Zone. This has been
introduced to assist organizations to move away from WINS and allow organizations to move to an all-DNS
environment. Unlike WINS, The GlobalNames zone is not intended to be used for peer-to-peer name
resolution.
* The DNS Server Role in Windows Server 2008 now supports the GlobalNames Zone.
This has been introduced to assist organizations tomove away from WINS and allow organizations to move to
an all-DNS environment. Unlike WINS, The GlobalNames zone is not intended to be used for peer-to-peer
name resolution.
Reference: Understanding Zone Types