Your network contains an Active Directory domain named contoso.com. The network contains 500
client computers that run Windows 8. All of the client computers connect to the Internet by using a
web proxy.
You deploy a server named Server1 that runs Windows Server 2012 R2. Server1 has the DNS Server
server role installed.
You configure all of the client computers to use Server1 as their primary DNS server.
You need to prevent Server1 from attempting to resolve Internet host names for the client
computers.
What should you do on Server1?
A.
Create a primary zone named “root”.
B.
Create a primary zone named “GlobalNames”.
C.
Create a forwarder that points to 169.254.0.1.
D.
Create a primary zone named “.”.
Should be D.
No such thing as A.
0
0
I agree with Ricky
0
0
A is the correct answer. “.” has a name and it’s called the Root Zone. It’s used to prevent access to the Internet.
https://support.microsoft.com/en-us/kb/298148
Also mentioned in PluralSight Windows Server 2012 R2 (70-410) Core Network Services.
0
0
When a zone that this DNS server hostsis a stub zone, this DNS server is a
source only for information about the authoritativename servers for this zone. The zone at this server must be
obtained from another DNS server that hosts the zone. This DNS server must have network access to the
remote DNS server to copy the authoritative name server information about the zone.
Note:
You can use stub zones to:
* Keep delegated zone information current. By updating a stub zone for one of its child zones regularly, the
DNS server that hosts both the parent zone and the stub zone will maintain a current list of authoritative DNS
servers for the child zone.
* Improve name resolution. Stub zones enable a DNS server to perform recursion using the stub zone’s list of
name servers, without having to query the Internet or an internal root server for the DNS namespace.
* Simplify DNS administration. By using stub zones throughout your DNS infrastructure, you can distribute a list
of the authoritative DNS servers for a zone withoutusing secondary zones. However, stub zones do not serve
the same purpose as secondary zones, and they are not an alternative for enhancing redundancy and load
sharing.
Incorrect:
Not B:
* The DNS Server Role in Windows Server 2008 now supports the GlobalNames Zone. This has been
introduced to assist organizations to move away from WINS and allow organizations to move to an all-DNS
environment. Unlike WINS, The GlobalNames zone is not intended to be used for peer-to-peer name
resolution.
* The DNS Server Role in Windows Server 2008 now supports the GlobalNames Zone. This has been
introduced to assist organizations to move away from WINS and allow organizations to move to an all-DNS
environment. Unlike WINS, The GlobalNames zone is not intended to be used for peer-to-peer name
resolution.
Reference: Understanding Zone Types
0
0
Forget this bullshit
3
0
Answer is D
@Eric – check the heading of your linked article. It kind of gives you a clue 😉
When you add a “.” zone to DNS server 1, it acts as it is the root of the internet, which of course it is not. However, because server 1 acts as if is the root of the internet, queries will go no further than server 1. Goal achieved 🙂
0
0
“You need to prevent Server1 from attempting to resolve Internet host names for the client
computers.”
If you create a root zone, then Server 1 still **ATTEMPTS** to resolve Internet host names for client computers. If you configure a forwarder to a non-existent, non-internet enabled device, then Server1 will not be the one attempting to resolve the Internet host names – another device will.
0
0
Another question from another website that gives the answer.
Sample Question 21
Microsoft Question:
Your network contains an Active Directory domain named contoso.com. The network contains 500 client computers that run Windows 8. All of the client computers connect to the Internet by using a web proxy. You deploy a server named Server1 that runs Windows Server 2012. Server1 has the DNS Server server role installed. You configure all of the client computers to use Server1 as their primary DNS server.You need to prevent Server1 from attempting to resolve Internet host names for the client computers. What should you do on Server1?
A. Configure the Security settings of the contoso.com zone.
B. Remove all root hints.
C. Create a primary zone named “.”.
D. Create a primary zone named “root”.
E. Create a primary zone named “GlobalNames”.
F. Create a forwarder that points to 169.254.0.1.
G. Create a stub zone named “root”.
H. Create a zone delegation for GlobalNames.contoso.com.
Answer: B,C
Explanation:
B. necessary to remove the default root hints files
C. install a root (.) zone on all internal DNS servers to prevent name resolution on the Internet http://support.microsoft.com/kb/298148
0
0
Another website has a question of the same kind.
Your network contains an Active Directory domain named contoso.com. The network contains 500 client computers that run Windows 8. All of the client computers connect to the Internet by using a web proxy. You deploy a server named Server1 that runs Windows Server 2012. Server1 has the DNS Server server role installed. You configure all of the client computers to use Server1 as their primary DNS server.You need to prevent Server1 from attempting to resolve Internet host names for the client computers. What should you do on Server1?
A. Configure the Security settings of the contoso.com zone.
B. Remove all root hints.
C. Create a primary zone named “.”.
D. Create a primary zone named “root”.
E. Create a primary zone named “GlobalNames”.
F. Create a forwarder that points to 169.254.0.1.
G. Create a stub zone named “root”.
H. Create a zone delegation for GlobalNames.contoso.com.
Answer: B,C
Explanation:
B. necessary to remove the default root hints files
C. install a root (.) zone on all internal DNS servers to prevent name resolution on the Internet http://support.microsoft.com/kb/298148
0
0
Another website has a question of the same kind.
See question 169 for details.
I can’t put in duplicate information.
install a root (.) zone on all internal DNS servers to prevent name resolution on the Internet http://support.microsoft.com/kb/298148
0
0
This is way wrong. There’s no such thing as a primary zone called “root”, it’s “.”.
0
0
When you install DNS on a Windows server that does not have a connection to the Internet, the zone for the domain is created and a root zone, also known as a dot zone, is also created. This root zone may prevent access to the Internet for DNS and for clients of the DNS. If there is a root zone, there are no other zones other than those that are listed with DNS, and you cannot configure forwarders or root hint servers.
Root domain
This is the top of the tree, representing an unnamed level; it is sometimes shown as two empty quotation marks (“”), indicating a null value. When used in a DNS domain name, it is stated by a trailing period (.) to designate that the name is located at the root or highest level of the domain hierarchy. In this instance, the DNS domain name is considered to be complete and points to an exact location in the tree of names. Names stated this way are called fully qualified domain names (FQDNs).
0
0
D.
https://support.microsoft.com/en-us/help/298148/how-to-remove-the-root-zone-dot-zone
from microsoft website:
“…To remove a root zone, follow these steps:
Click Start, point to
Programs, point to Administrative Tools, and then click DNS.
Expand Server, and then expand
Forward Lookup Zone.
Right-click the folder that is named “.” (period), click
Delete, click Yes to confirm…”
0
0
When you install DNS on a Windows 2000 server that does not have a connection to the Internet, the zone for the domain is created and a root zone, also known as a dot zone, is also created. This root zone may prevent access to the Internet for DNS and for clients of the DNS. If there is a root zone, there are no other zones other than those that are listed with DNS, and you cannot configure forwarders or root hint servers. For these reasons, you may have to remove the root zone.
0
0