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.
Create a GlobalNames zone.
D.
Configure dynamic updates for contoso.com.
Explanation:
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
C
It’s really annoying that you’re almost always the first to answer every question and if we glance at the bottom quickly, we see your dumb answer before even reading the question.
Keep your answer to yourself. Nobody thinks you’re super smart.
stopit I guess you should stopit. It is so nice of Saad to confirm the answers. So instead of thanking him you are bitching. GTFOOH.
Deploying a GlobalNames Zone
https://technet.microsoft.com/en-gb/library/cc731744.aspx
I disagree. The comments section is for comments, not to answer the question. Really, we can disagree and discuss the solutions given, but the Comment section isn’t to just put your answer down. Any asshole can do that.
Don’t Global Names Zones have to be AD integrated so surely the answer is B
is it c or d
Although a GlobalNames zone is required in order to resolve single-label names, GNZs
must be AD-integrated.
Since this is a standard primary zone (as opposed to an ADDS primary zone), we must first
integrate the zone into Active Directory
It is “B”
“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/cc771566.aspx
it should be B
GlobalNames zone need to be Integrated with ADDS first
C is 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.
It’s not B. B states:
B.Convert the contoso.com zone to an Active Directory-integrated zone.
We don’t need contoso.com to be Directory-integrated. We need GlobalNames to be directory-integrated which we can choose while creating GlobalNames primary zone.
Answer is simply C.
I disagree. I think it is B
You can only choose GlobalNames to be directory-integrated IF DNS server is a writeable domain controller!
In this case, there is no mentioned about AD is installed on the server where the primary zone is, only DNS is installed.
“You install the DNS Server server role on Server1, and then you create a standard primary
zone named contoso.com.”
The very first thing you have to do is now to install AD-DS on this server, then make your primary zone AD integrated and at least you have to create the GlobalName Zone.
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(…)
https://technet.microsoft.com/en-us/library/cc731744(v=ws.11).aspx
I agree with branislav. The question mentions nothing about the DNS server being DC or on a domain.
“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”