Scribd
Upload
21 views11 pages

4.2 Monitoring and Debug Logging

Uploaded by

Jaja Jajagf
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
21 views11 pages

4.2 Monitoring and Debug Logging

Uploaded by

Jaja Jajagf
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 11

Welcome to Troubleshooting Tools

Monitoring and Debug Logging

In this Video:
• We will describe two troubleshooting tools from Windows DNS
Manager called Monitoring and Debug Logging.
• We will test our DNS configuration using monitoring. Then we will
perform three tests utilizing Debug Logging.
• At the completion of this lecture, you will gain valuable-work related
knowledge and experience by utilizing and implementing the tools
discussed in this lecture.
Monitoring

• From SVR-DNS1, open server manager, tools, DNS, right click on DNS
server, properties, click monitoring.
• Select a test type
Check – A simple query against this DNS server – click test now

The DNS client that’s running on the DNS server will perform a simple query, to
test if the DNS server can perform name resolution on itself. Similar to using
nslookup. A simple query is a query that this DNS server resolves without
contacting any other DNS server. A simple query does not require network access.
Click test now, and the simple query passes the test.

Now check, A recursive query to other DNS servers – This test performs a DNS
style lookup to the root. Requires network access. You can test both at the same
time, and you can set the time interval. Click test now and the recursive query test
passes.

1
Debug Logging
Purpose: What can I use debug logging for? For the purpose of this lecture
we will conduct three tests.
1. We will determine if our secondary partners are getting notified when there
are changes that have been made to the data base.
2. We will test if there are any servers or clients that are having trouble
updating their DNS records.
3. We will identify whether there are other computers performing queries on
our DNS server.
Prerequisites:
• There are two servers I will be using for these tests. A member server (SVR-
DNS1) and a domain controller (SVR-US).
• In order to setup test #1 in your lab, you will need to create a secondary zone.
Be sure to download the guide from Lecture #11 entitled Creating a
Secondary Zone.
• This test assumes that you have followed the guide and setup a secondary
zone.

2
• For this test, my member server SVR-DNS1 contains the secondary zone. The
DNS server SVR-US is my primary server.

LAB Setup Overview


• From the server SVR-US, a Primary Zone called money.com has been
created.

• From the server SVR-DNS1 a secondary zone called money.com (a read only
copy) has been created for backup purposes.

3
• From the server SVR-US, zone, money.com. Zone transfers have been
enabled.

• Notifications have been configured.

4
• When there are changes made to the zone money.com (located on the primary
svr-us) notifications will be sent to the secondary server which is SVR-DNS1.

Test #1 – Are my DNS secondary partners getting notified when I make


changes in my DNS?
From the domain controller, which in this case is SVR-US
Open server manager, tools, DNS manager, right click on the server, select
properties, then select debug logging.
• Check Log packets for debugging
• Packet direction – both outgoing and incoming
• Turn off queries/transfers, and updates – Turn on notifications
• Under log file, file path and name, in this case I type C:\SVR-US DNS
Notifications 6-12.txt
• I can also choose where I want to store the log, and the choose the size.
• The Default size is 5 GB

5
From the server SVR-US open the zone money.com, delete several of the A host
records. After making changes to the database manually on SVR-US. Verify that my
DNS secondary partner SRV-DNS1 is being notified that I have made changes to
DNS.
From SVR-DNS1, right click on the secondary zone money.com, click Transfer from
master. This will force a zone transfer. This could take some time, try pressing F5.
Open the file named SVR-US DNS Notifications 6-12.txt
We can see that SVR-US sent a notification to the server SVR-DNS1 (IP address
192.168.0.47), zone money.com proving that notifications are working.

6
Test #2 – Are my DNS clients and servers able to update their DNS
records?

By default, every windows TCP/IP client registers it’s IP address to its local DNS
server. This process is called dynamic updates. This test will verify if the client or
server is having problems updating its DNS records to the local DNS server.

Open debug logging


• Check Log packets for debugging
• Packet direction – both outgoing and incoming
• Check updates

7
• Type the name and enter the path for the text file

8
This slide shows that from SVR-US (.25) I am logging updates from both servers.
This proves that updates are working.

Test # 3 – How can I test whether another computer is querying my DNS


server.
Open Debug logging
• Check Log packets for debugging
• Packet direction – both outgoing and incoming
• Check Queries and Transfers

• Type the name and enter the path for the text file

9
10
This slide shows that I am getting queries from my Windows 10 machine (.27) and
from SVR-DNS1 (.47)

In this Video:
• We described two troubleshooting tools from Windows DNS Manager called
Monitoring and Debug Logging.
• We tested our DNS configuration using monitoring. Then we performed three
tests utilizing Debug Logging.
• You should have gained valuable-work related knowledge and experience by
utilizing and implementing the tools discussed in this lecture.

Congratulations you have completed this lecture.


Thanks for watching, and we will see you in the next lecture.

11

You might also like