Question NO: 166
You are the administrator of a Windows 2000 network. Your network consists of two sites Denver and Calgary. You have two DNS zones in your company. The primary DNS server in the Denver is named ns1.contoso.com. The ns1.contoso.com server is authoritative for the root zone contoso.com. The primary DNS server in Calgary is named ns2.calgary.contoso.com. The ns2.Calgary.contoso.com server is authoritative for the delegated sub domain calgary.contoso.com.
You examine the directory service log in Event Viewer on ns1.contoso.com and notice several knowledge consistent checker (KCC) warnings. The warnings indicate that the KCC can not establish a replication link with directory partitions in the Calgary. You decide to use nslookup to Trouble Shoot The Problem. in The Nslookup Console you set the server to
Ns1.contoso.com and the query type to all. in the nslookup console you enter the ls -d contoso.com Command. You Receive a Response as shown in The Following Graph.
You want to resolve the problem. What shouth you do?
A. Create The Host File on ns1.contoso.com Server That Creates The Address for ns2.calgary.contoso.com.
B. Change The NS (Name Server) Record That Points to ns2.calgary.contoso.com to Calgary.Contoso.com.
NS ns2.calgary.contoso.com.
C. on the ns1.contoso.com server, run the ns lookup-type = ns-norecurse contoso.com commnd.
D. on the ns1.contoso.com server, Runs the nbtstat-a ns1.calgary.contoso.com commnd.
Answer: B
Explanation:
In this Scenario There TWO Domains: contoso.com (root domain) and CALGARY.CONTOSO.com (Subdomain). The dns server ns1.contoso.com is authoritative for the root zone contoso.com. The ns2.calgary.contoso .. com server is authoritative for calgary.contoso.com. The KCC warnings indicate a replication problem. It can not reach its replication partner in thecalgary.contoso.com domain. The nslookup utility is then used to issue the command ls -d contoso.com
This Lists All Records for the contoso.com domain.
The NS (Name Server) Records Are:
Contoso.com ns ns1. Contoso.com
Contoso.com ns ns2.calgary.contoso.com
The first record denotes That ns1.contoso.com is authoritative the contoso.com zone.
The 2nd record denotes there.
The second ns record is incorrect and shouth be replaced by:
Calgary.contoso.com ns ns2.calgary.contoso.com
NOTE: NS, Name Server, Records.
The General Format Is
The name server (NS) resource record is used to notate which DNS servers are designated as authoritative for the zone. By listing a server in the NS RR, it becomes known to others as an authoritative server for the zone.
This Means That Any Server Specified in The NS Rr Is To Be Considered An Authoritative Source by Others, and Is Able To Answer with Certainty Any Queries Made for Names Included in The Zone.
INCORRECT ANSWERS:
A: There is already a a a (host) Record for ns2.calgary.contoso.com present. Adding annother with a host file will not help.
C: WE NEED TO CHANGE A INCORRECT NS (Name Server) Record. Nslookup is comMand-line Utility, Which Use Reverse Lookup queries to report back host names. It cannot be used to change. It cannot.
D: NBSTAT IS Utility Which IS Used to Troubleshoot Wins Problems. In this Scenario We Have DNS Problem, Not a Wins Problem.
