You need to ensure that Server1 can host a secondary copy of the contoso.com zone

Yournetwork contains an Active Directory domain named contoso.com.
All domain controllers run Windows Server 2012. One of the domain controllers is named DC1.
The DNS zone for the contoso.com zone is Active Directory-integrated and has the default settings.
A server named Server1 is a DNS server that runs a UNIX-based operating system.
You plan to use Server1 as a secondary DNS server for the contoso.com zone.
You need to ensure that Server1 can host a secondary copy of the contoso.com zone.
What should you do?

Yournetwork contains an Active Directory domain named contoso.com.
All domain controllers run Windows Server 2012. One of the domain controllers is named DC1.
The DNS zone for the contoso.com zone is Active Directory-integrated and has the default settings.
A server named Server1 is a DNS server that runs a UNIX-based operating system.
You plan to use Server1 as a secondary DNS server for the contoso.com zone.
You need to ensure that Server1 can host a secondary copy of the contoso.com zone.
What should you do?

A.
From Windows PowerShell, run the Set-DnsServerForwarder cmdlet and specify the contoso.com
zone as a target.

B.
From Windows PowerShell, run the Set-DnsServerSetting cmdlet and specify DC1 as a target.

C.
From Windows PowerShell, run the Set-DnsServerPrimaryZone cmdlet and specify the
contoso.com zone as a target.

D.
From DNS Manager, modify the Advanced settings of DC1.

Explanation:
C)
The Set-DnsServerSecondaryZone cmdlet changes settings for an existing secondary zone on a
Domain Name System (DNS) server.
http://technet.microsoft.com/en-us/library/jj649920(v=wps.620).aspx



Leave a Reply 5

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

18 − six =


Sako_Pako

Sako_Pako

The answer does not match width the question:
Set-DnsServerSecondaryZone not equ. Set-DnsServerPrimaryZone

Dave

Dave

Actually, since the secondary is the Unix DNS server, the command wouldn’t work (maybe when PoSh on Linux has matured).

So we use “Set-DnsServerPrimaryZone -SecondaryServers” to define a secondary Name Server (and probably the notify options to enable zone transfers).

I have no idea if anything else needs to be changed besides that to support *nix DNS secondaries.

Ricky

Ricky

Repeated question from 411.

Answer is D. Here are the comment extracts from my previous study notes:

Agree with nina…..first BIND needs to be enabled to work with Unix. Bind is disabled by default. Once Bind is enabled, you can make additional changes like Zone transfer, etc.
Since they even give that step as an option, it is pretty clear they want you to activate Bind first.

From

1. DC1 has DEFAULT DNS server settings and is DNS for contoso zone which is AD Integrated
2. Server1 is UNIX (ie BIND) and will be a secondary for contoso
3. You MUST ENSURE that server1 can be a secondary for contoso

Without configuring the advanced DNS properties of server DC1 to “Enable BIND Secondaries” (Not configured by default – see point 1) even if you “Allow Zone Transfer” the transfer will not take place as you have NOT ENSURED that server1 can be a secondary.

Rogue

Rogue

70-411 question

Chris

Chris

Answer: D
Bind enabled as noted by Ricky.