You need to ensure that when you run Nslookup, the correct name of the default server is displayed

Your network contains an Active Directory domain named contoso.com. The domain contains a domain
controller named Server1 that ha the DNS Server server role installed.
Server1 hosts a primary zone for contoso.com.
The domain contains a member server named Server2 that is configured to use Server1 as its primary DNS
server.
From Server2, you run nslookup.exe as shown in the exhibit. (Refer to the Exhibit.)

You need to ensure that when you run Nslookup, the correct name of the default server is displayed.
What should you do?

Your network contains an Active Directory domain named contoso.com. The domain contains a domain
controller named Server1 that ha the DNS Server server role installed.
Server1 hosts a primary zone for contoso.com.
The domain contains a member server named Server2 that is configured to use Server1 as its primary DNS
server.
From Server2, you run nslookup.exe as shown in the exhibit. (Refer to the Exhibit.)

You need to ensure that when you run Nslookup, the correct name of the default server is displayed.
What should you do?

A.
From Advanced TCP/IP Settings on Server1, add contoso.com to the DNS suffix list.

B.
On Server1, modify the Security settings of the contoso.com zone.

C.
On Server1, create a reverse lookup zone.

D.
From Advanced TCP/IP Settings on Server2, add contoso.com to the DNS suffix list.

Explanation:
C: Make sure that a reverse lookup zone that is authoritative for the PTR resource record exists. For more
information about adding a reverse lookup zone, see”Adding a Reverse Lookup Zone”
http://technet.microsoft.com/en-us/library/cc961417.aspx



Leave a Reply 3

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


JohnyBoy

JohnyBoy

Unable to resolve the IP 10.0.11 from IP to name.
Reverse Lookup zone requires to be created.
C