Your network contains an Active Directory domain named contoso.com. The domain contains a member server
named Server1. Server1 runs Windows Server 2012 andhas the DHCP Server server role installed.
You create two IPv4 scopes on Server1. The scopes are configured as shown in the following table.
The DHCP clients in Subnet1 can connect to the client computers in Subnet2 by using an IP address or a
FQDN.
You discover that the DHCP clients in Subnet2 can connect to client computers in Subnet1 by using an IP
address only.
You need to ensure that the DHCP clients in both subnets can connect to any other DHCP client by usinga
FQDN.
What should you add?
A.
The 006 DNS Servers option to Subnet2
B.
The 015 DNS Domain Name option to Subnet1
C.
The 006 DNS Servers option to Subnet1
D.
The 015 DNS Domain Name option to Subnet2
Explanation:
To enable DNS on the network, you need to configureDNS clients and servers. When you configure DNS
clients, you tell the clients the IP addresses of DNS servers on the network. Usingthese addresses, clients can
communicate with DNS servers anywhere on the network, even if the servers areon different subnets.
When the network uses DHCP, you should configure DHCP to work with DNS. To do this,
you need to set theDHCP scope options 006 DNS Servers and 015 DNS Domain Name.
Issue: The DNS domain option (option 15) is not configured for one or more scopes. Impact: DHCP IPv4 clients
will not be provided with a DNS domain and will notbe able to resolve names.
Resolution:
Configure a DNS domain option as a server or scope option using the DHCP MMC: Dynamic Host
Configuration Protocol (DHCP) uses options to pass additional Internet Protocol (IP) settings toDHCP clients on
a network. Examples of DHCP options include: The default gateway IP address, The Domain Name System
(DNS) serverIP address
The DNS domain name
Membership in the Administrators or DHCP Administrators group is the minimum required to complete
thisprocedure.
To configure DNS server as a scope option or serveroption
1. Click Start, point to Administrative Tools and then click DHCP.
2. In the console tree, expand the App1icable DHCP server, expand IPv4, and then right- click Server Options
3. Click Configure Options, check 015 DNS Domain Name, type the App1icable domain name in String value:,
and then click OK.
http://support.microsoft.com/kb/300684/en-us
http://technet.microsoft.com/en-us/library/bb727109.aspx http://technet.microsoft.com/en-us/library/ee941136
(v=ws.10).aspx http://technet.microsoft.com/en-us/library/dd572752%28v=office.13%29.aspx
No. Answer is A. DNS Domain Name (015) sets up a DNS suffix, it does not solving a trouble with FQDN requests of Subnet2 users.
0
0
correct, answer must be A
0
0
Answer must be A. Adding a DNS Domain Name would not help in this situation. It mentions they cannot connect to computers using a FQDN. Adding a DNS Domain Name would only allow access using hostnames instead of FQDNs. The answer must be A to add a DNS Server.
0
0
The correct answer is ‘D’, because 006 DNS Servers option is for IPv6.
Read:
http://technet.microsoft.com/en-us/library/ee941147(v=WS.10).aspx
and for The 015 DNS Domain Name option read:
http://technet.microsoft.com/en-us/library/ee941136%20(v=ws.10).aspx
0
0
Where does it say IPv6 in your first link? Also your second link talks about the Domain Name not DNS Servers so:
A is the answer bro.
0
0
Wait,what?! 006 is for IPv4…used it a million times setting up DHCP. Anvar02’s answer says it all.
0
0
OMG, what a mish mash of answers. The correct answer is A. God save us.
0
0
Guys, the answer is ‘B’
Subnet 1 can ping both IP and FGDN of Subnet 2:
Which means, subnet2 DHCP clients registered their FQDN to DNS server successfully (015 works for subnet2), which also implies that subnet2 knows DNS server IP address(006 DNS Server works for subnet2) and DNS works for subnet 1 (006 DNS Server) of course.
Now, subnet 2 can ping IP , but not FQDN of subnet 1:
which means, DNS doesn’t work(006 not configured for subnet2) OR subnet1 didn’t register their FQDN to DNS correctly (015 not configured for subnet 1).
However, the latter one is not true, because subnet1 was able to resolve subnet2 as above stated.
Now, what’s the answer? B!!!!!
0
0
Full shit!!! In the question with Subnet_TOR and Subnet_MTL the answer is A !!! in the SAME CASE !!!
to han: in Subnet 1 (answers B and C) – all works.
0
0
to postmaster,
when subnet 1 can ping both ip and FQDN of subnet 2, it means;
A subnet 2 successfully registered their FQDN to DNS server. (Not subnet 1)
B subnet 1 was able to connect to DNS server
You can assume whatever you want, but you can switch around what computer does according to what your assumption is.
0
0
This is update after digging into this question. I spent quite of time to understand how DHCP and DNS work together.
First, the answer is A. 006 DNS server option in subnet2.
DNS A record is not registered by Clients when client gets the IP address initially. Actually DHCP server requests DNS server to create A record for the IP address lease. Client also can update if Control Panel/Network properties/Advanced/DNS/ ‘register this connections…’ is checked. When a computer joins domain (as this question says it’s domain contosolcom for both subnets), primary DNS suffix is created on clients (System settings/Computer Names/Change/Primary DNS suffix). This seems to govern DNS regstration, not DNS suffix settings in Network properties. DNS suffixes in Network properties, which is configured by DHCP 015 option is used for ‘Search’ only, not registration.
Also, the question is saying ‘FQDN’ which means, clients doesn’t have to use DNS suffix for search. the domain dns suffix is already provided to the pinging.
For this reason, DNS Suffix doesn’t play any role in this senario. However, the reason for subnet 2 can not ping subnet 1 by FQDN still has two possibilities to think of. subnet 1 clients were not registered to DNS server correctly or subnet 2 can’t find DNS server. But the the former reason is not in the 4 choices of this question, so Answer is A.
I apologizes making confused to readers by my previous comments.
0
0
Hans answer us utterly confusing.
Has nothing to do with “clients were not registered” nor with “can not ping subnet1”. Nowhere says “ping” on the question.
0
0
If subnet2 can’t find DNS server, subnet2 dns client won’t be able to register in the dns server, if this is the case, I don’t understand why DHCP clients in Subnet1 can connect to the client computers in Subnet2 by using an IP address or a FQDN.
0
0
015 Subnet2 Option D
Clear answer from technet. See this
https://technet.microsoft.com/en-us/library/ee941136(v=ws.10).aspx
Who agrees left a comment below my answer so no body get confused any more!
0
0
No. You do not need 015. You are already pinging the machine by FQDN. FQDN includes the DNS Domain name in it. Therefore adding feature 015 is redudant.
You need to add 006 so when you ping by FQDN, it will connect to the SERVER SPECIFIED IN 006 SO IT CAN RETURN YOU AN IP ADDRESS
CAPICHE?
ANSWER IS “A”
0
0
Domain -> any member has Primary DNS Suffix equal domain name:
computer – properties – adnvanced -computer name -change – more
if different from 015 DNS Domain Name,
view ipconfig /all -> DNS Suffix Search List – Primary DNS Suffix will be first,
so it doen’t matter 015 DNS Domain Name in DHCP with domain.
Wrong question.
0
0
Correct answer is A
“You discover that the DHCP clients in Subnet2 can connect to client computers in Subnet1 by using an ***IP address*** only.”
from: https://technet.microsoft.com/en-us/library/ee941180%28v=ws.10%29.aspx
Issue: The DNS server option (option 6) is not configured for one or more scopes.
Impact: DHCPv4 clients will be unable to resolve DNS names.
Resolution: Configure the DNS server as a scope or server option using the DHCP MMC.
from:https://technet.microsoft.com/en-us/library/ee941136%28v=WS.10%29.aspx:
Issue: The DNS domain option (option 15) is not configured for one or more scopes.
Impact: DHCP IPv4 clients will not be provided with a DNS domain and will not be able to resolve names.
Resolution: Configure a DNS domain option as a server or scope option using the DHCP MMC.
0
0
You need server address (006) not domain name (015) for subnet 2
Answer A
0
0
option a is right as many web sites are answering option a as answer
0
0