Your network contains multiple subnets.
On one of the subnets, you deploy a server named Server1 that runs Windows Server 2012 R2.
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:
Although a GlobalNames zone is required in order to resolve single-label names, GNZs must be ADintegrated.
Since this is a standard primary zone (as opposed to an ADDS primary zone), we must first integrate
the zone into Active Directory.
References:
Exam Ref: 70-410: Installing and Configuring Windows Server 2012 R2, Chapter4: Deploying and
configuring core network services, Objective 4.3: Deploy and Configure the DNS service, p.233
http://technet.microsoft.com/en-us/library/cc731744.aspx
D
1
1
I think D – Create a GlobalNames Zone.
You should use GlobalNames zone to take advantage of single-label names.
This will also ensure that the zone remains valid.
References:
Exam Ref: 70-410: Installing and Configuring Windows Server 2012 R2, Chapter4:
Deploying and configuring core network services, Objective 4.3: Deploy and Configure the DNS service, p.233
http://technet.microsoft.com/en-us/library/cc731744.aspx
1
0
Answer here is B, as the question is, what should you do first? and since it’s a standard Primary Zone which means not Active Diretory Integrated and GlobalNames Zone must be Active Directory Integrated, so you need first to integrate the standard Zone into an Active Directory.
0
0
The question is What should you do first?
Answer is B.
0
0
Answer is D:
Step 1: Create the GlobalNames zone
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.
https://technet.microsoft.com/en-us/library/cc731744.aspx
0
0
Globalnamezone “it is simply an AD DS-integrated forward lookup zone that is called GlobalNames” but the question is that you create a standard primary zone named contoso.com.
so before we can create GlobalName, dont we need to change the standard primary zone? we should be doing B and then following by D isnt it?
0
0
The answer here cannot be B though as the question doesn’t state if the server has a ADDS domain it just says it has DNS server installed. D is the better Answer.
0
0
D IS THE CORRECT ANSWER
0
0
And this is why dumps alone are a bad idea. Same site, different version, same question. Really even the explanation here doesn’t gel with the reference link. D is the correct answer. http://www.aiotestking.com/microsoft/you-need-to-ensure-that-client-computers-can-resolve-single-label-names-to-ip-addresses-2/
0
0
B. GlobalNames zone must be create on a DNS server that is a domain controller. The question not say that server is already domain controler it say “You install the DNS Server server role on Server1”. So B is correct if we want convert dns zone to integrated with ad we must add ad role
0
0
D seems to be the correct answer. The zone must be named GlobalNames. The zone that’s already created its named Contoso.com
https://www.petri.com/using-globalnames-zone-window-server-2008
How and Why to Implement a GlobalNames DNS Zone in Windows Server 2008 and Above
http://www.dell.com/support/article/us/en/19/SLN156516/en
The procedure for creating a GlobalNames zone in Windows Server is as follows:
In the DNS console, right-click Forward Lookup Zones and select New Zone.
Follow the prompts in the New Zone wizard to create the zone.
The zone must be named GlobalNames.
=============================
For best results, make the zone AD-integrated and configure it to replicate to every DNS server in the forest.
Enable GlobalNames support by typing the following at an administrative command prompt:
dnscmd /config /enableglobalnamessupport 1
The final step is crucial, as the GlobalNames zone will not function without it. Once the zone is created, simply create CNAME records within it for every FQDN that you want to abbreviate. There’s one very important caveat to using the GlobalNames zone: the CNAME records within it cannot be dynamically updated, so they should only correspond to machines with static IP addresses.
0
0
To help organizations migrate to DNS for all name resolution, the DNS Server role in Windows Server 2008 supports a special 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.
0
0
B is the correct answer.
GlobalNameZones are only available in Active Directory Integrated DNS zones. In order to create a GNZ, you would first need to convert the standard primary zone into an AD Integrated Zone. The fact that the question doesn’t say whether or not Server1 is a DC is irrelevant.
“The GlobalNames zone is not a special zone type; rather, it is simply an AD DS-integrated forward lookup zone that is called GlobalNames.”
https://technet.microsoft.com/en-us/library/cc731744(v=ws.11).aspx
2
0
These questions are a real pain…
The question states that Server1 is a member server. (otherwise it would state a domain controller) and that contoso is a primary zone ( what also tells us this is a member server)
Al thou Microsoft “Recommends” that a globalNames zone is AD integrated for scalability and management purposes. You can perfectly create a Globalnames zone on a DNS member server. From what I gathered and tested in my lab.
The quickest way is to just create against recommendation of Microsoft a Globalnames primary zone. Answer D.
But if you want to do it as Microsoft recommends you should make server 1 a DC and then integrate the contoso zone in to AD. Answer B.
Now comes my question what is the right way to do it? If you ask me this is a bit far fetched for 70-410. I would consider this advanced DNS stuff. 411 or 412.
0
0