You have DHCP server named Server1 that runs Windows Server 2012 R2.
Server1 has two scope production and development.
Currently, all DHCP clients register their host name in a dns zone named contoso.com.
You need to ensure that only the clients that obtain an ip address from the development scope,
register their host name in a dns zone named dev.contoso.com.
What should you do?
A.
Modify the advanced settings of the dhcp server.
B.
Run the set-dhcpserver4scope cmdlet.
C.
Modify the dns settings of the development scope.
D.
Run the add-dhcpserver4policy cmdlet.
Think this one is:
C:
Modify the DNS settings of the development scope.
i.e add the dev.contoso.com DCs as DNS servers in the options on the development scope
0
0
Indeed it’s C.
B is wrong, see https://technet.microsoft.com/en-us/library/jj590743(v=wps.630).aspx
0
0
This is poorly worded.
The correct answer is probably C.
I have a different version of this question, but one of the answers is “Modify the advanced settings of the development scope.”
I also just booted into a Hyper-V server and looked for myself. Here is the screenshot of the settings we are looking for, which you find in the scope options / advanced tab.
https://gyazo.com/6178ae1db56d44bc8b2635b16c5dec71
0
1
Please COMPLETELY disregard my above comment.
The answer is NOT C, the answer is, in fact, D.
Basically, you can create a Policy that Targets the address range in the Development Scope. Then you can right click the created Policy, go to the DNS tab and there you can specify the DNS suffix in which you want to register the clients that the Policy is targeting.
If you have ANY doubts about this entire thing, just read the below article carefully. I sat here for over an hour trying to work this in a lab until I found this link.
http://blogs.technet.com/b/teamdhcp/archive/2014/01/26/windows-server-2012-r2-enhancing-dhcp-policies-and-dns-registrations-in-dhcp-server.aspx
10
0
thanks puck:
here
Add-DhcpServerv4Policy -Name ForeignDevices -Condition OR -Fqdn NE,*.contoso.com
4
0
server options are global, scope changes must be done!!
0
0
The answer should be C. In the question, it states that the Server1 has two scope production and development. So the scope is already created. During the new scope wizard if you choose Yes I want to config now (scope options), it prompts you to set DNS option. The scope option by default is set to the parent domain (name and IP). Therefore you don’t need to add an additional zone with add-dhcpserver, you need to modify the current “development scope” setting which would be pointing to the parent domain by default, and change it to point to dev.contoso.com.
1
1
Yes i agree with you. You just need to modify the DNS settings on the scope options of the Development Scope.
0
0
Looking back at this question again, after reading carefully Puck’s link, i now think the only way to configure what’s asked in the question is through a scope policy, which in this case would validate answer D.
1
0
You would have to modify the scope options, not the DHCP advanced settings.
0
0
Its D
you can only set DNS prefix with DHCP Policy Options!
here you are given the add-dhcpserver4policy cmdlet
2
0
D
1
0
Should be D.
https://blogs.technet.microsoft.com/teamdhcp/2014/01/26/windows-server-2012-r2-enhancing-dhcp-policies-and-dns-registrations-in-dhcp-server/
3
0