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 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?

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



Leave a Reply 10

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


hater

hater

should be D?

Mark

Mark

Yes, but the question asks what do you need to do first.

And it must be AD integrated before you can use Global Names

Erik

Erik

D is right.

Microsoft says itself;

Deploying a GlobalNames zone
The specific steps for deploying a GlobalNames zone can vary somewhat, depending on the AD DS topology of your network.
–>>Step 1<<–: Create the GlobalNames zone

It doesn't get easier that that 😉

source: http://technet.microsoft.com/en-us/library/cc731744.aspx

mark

mark

The right answer is B since the server does not have Active Directory (AD) domain services installed and thus is not a Domain controller (DC). The server must first become a DC and integrate the contoso.com zone into AD.

pikapoka

pikapoka

Erik,
just above the text you quoted it is also written:
…Recommend that the GlobalNames zone be integrated with Active Directory Domain Services (AD DS). This integration with AD DS ensures easier management and future scalability.
So the correct answer is B

Bap

Bap

And just below :
“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…”

yoyoma

yoyoma

I agree that B is the correct answer. I just wish the answer was worded to include “promote Server1 to a DC and convert the contoso.com zone to an Active Directory-integrated zone”. To me since it makes no mention that the server is a DC, as it stands a member server you cannot convert DNS to AD integrated unless it is first a DC.

tata

tata

B가 맞는 답이군요.

tata

tata

should be correct answer?

Tim

Tim

Recommend, is not the same as required. You can skip the integration and create the GlobalNames zone first. It’s already established that the DNS Server server role is on Server1. Since AD DS is not necessary but recommended (a local file will do the same job), the first step is D

IMO