You need to ensure that client computers can resolve single-label names to IP addresses

Your network contains multiple subnets.
On one of the subnets, you deploy a server named Server1 that runs Windows Server 2012.
You install the DNS Server server role on Server1, and then you create a standard primary zone named
contoso.com.
You need to ensure that client computers can resolve single-label names to IP addresses.
What should you do first?

Your network contains multiple subnets.
On one of the subnets, you deploy a server named Server1 that runs Windows Server 2012.
You install the DNS Server server role on Server1, and then you create a standard primary zone named
contoso.com.
You need to ensure that client computers can resolve single-label names to IP addresses.
What should you do first?

A.
Create a reverse lookup zone.

B.
Convert the contoso.com zone to an Active Directory-integrated zone.

C.
Configure dynamic updates for contoso.com.

D.
Create a GlobalNames zone.

Explanation:
Use GlobalNames zones in Windows Server 2008 to take advantage of single-label names Providing SingleLabel DNS Name Resolution:
While Domain Name System (DNS) is the predominant name-resolution technology in TCP/IP networks,
Windows Internet Name Service (WINS) is deployed inmany networks as an alternative nameresolutionprotocol.
GlobalNames Zone (GNZ) feature:
The GNZ feature is designed to enable DNS resolution of these single-label, static, global names.
You can deploy a GNZ in a single forest or across multiple forests. GNZ is intended to aid the retirement of
WINS. It is not a replacement for WINS. GNZ is not intended tosupport the single-label name resolutionof
records that are registered dynamically and therefore not managedby IT administrators. GNZ does make it
possible for you to provide single-label name resolution of a fixed set ofhost computers whose names are
guaranteed to be both global and unique.
http://technet.microsoft.com/en-us/library/cc731744.aspx http://technet.microsoft.com/en-us/library/cc816610
(v=ws.10).aspx

Show Hint

Leave a Reply 9

Your email address will not be published. Required fields are marked *

mslover

mslover

D

To provide maximum performance and scalability, it is recommended that the GlobalNames zone be integrated with AD DS and that each authoritative DNS server be configured with a local copy of the GlobalNames zone. AD DS integration of the GlobalNames zone is required to support deployment of the GlobalNames zone across multiple forests.

https://technet.microsoft.com/en-us/library/cc753635%28v=ws.10%29.aspx

Reply

pietk

pietk

The first step in deploying a GlobalNames zone is to create the zone on a DNS server that is a domain controller running Windows Server 2008. The GlobalNames zone is not a special zone type; rather, it is simply an AD DS-integrated forward lookup zone that is called GlobalNames. For information about creating a primary forward lookup zone, see Add a Forward Lookup Zone.

you must convert to ad

Reply

Exo-L

Exo-L

I think it should be reverse lookup zone!!! It wasn’t mentioned in the question that they want single labeled names to be resolved? So why is the answer globalnames zone?

Reply

Exo-L

Exo-L

Excuse me, I didn’t read the question carefully

Reply

Barnay

Barnay

I am still confusing with the global name zone to support single label names to IP addresses. How about for Convert the contoso.com zone to an Active Directory-integrated zone. it may need first to be effect.

Any

Reply

Joe

Joe

step 1 – run following cmd on authoritative DNS Server:

DNScmd (servername) /config /enableglobalnamessupport 1

step 2 – create an AD integrated zone called -GlobalNames that is forest wide with dynamic updates disabled.

Then add a CNAME for each single-label required.

So yeah..D.

Reply