- Information
- AI Chat
This is a Premium Document. Some documents on Studocu are Premium. Upgrade to Premium to unlock it.
Was this document helpful?
This is a Premium Document. Some documents on Studocu are Premium. Upgrade to Premium to unlock it.
4.11.6 Explore nslookup Lab
Subject: Computer Science
835 Documents
Students shared 835 documents in this course
Level:
Standard
Was this document helpful?
This is a preview
Do you want full access? Go Premium and unlock all pages
Access to all documents
Get Unlimited Downloads
Improve your grades
Already Premium?
10/3/23, 5:17 PM
TestOut LabSim
https://labsimapp.testout.com/v6_0_572/simwindow.html?c2ltRGVmVXJsPWh0dHBzJTNBJTJGJTJGY2RuLnRlc3RvdXQuY29tJTJGX3ZlcnNpb25fNj…
1/1
Lab Report
Lab Report
Time Spent: 01:48
Score: 1/1 (100%)
Pass
Passing Score: 1/1 (100%)
TASK SUMMARY
Required Actions
Explore DNS with nslookup
EXPLANATION
Complete this lab as follows:
1. Use nslookup to query the DNS for the CorpWeb server using its fully qualified domain name.
a. Right-click Start and select Windows PowerShell (Admin).
b. At the PowerShell prompt, type nslookup CorpWeb.CorpNet.local and press Enter.
The CorpDC DNS server responds with the name resolution information for CorpWeb.
2. Use nslookup to query the CorpDC3 DNS server for CorpWeb.
a. Type nslookup CorpWeb.CorpNet.local CorpDC3.CorpNet.local and press Enter.
The CorpDC3 DNS server responds that it can't find CorpWeb. CorpDC3 does not have a DNS record for
CorpWeb.
3. Answer the questions.
What is the Problem?
The information between the DNS databases is not consistent. Since this DNS zone is an Active Directory-
integrated zone, this indicates that Active Directory is not synchronizing properly.
How would you resolve this problem?
You would likely attempt to force replication between the Active Directory domain controllers. If CorpDC held a
primary zone and CorpDC3 held a secondary zone, you would likely initiate a zone transfer to make sure that the
DNS records were consistent between servers.
How would you verify that the problem has been fixed?
After implementing the above solution, you could verify that the problem was fixed by repeating step 2. The
CorpDC3 DNS server should respond with name resolution information for CorpWeb.