Scribd
Upload
41 views4 pages

Wireshark DNS v7.0

Uploaded by

02fe22bcs003
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
41 views4 pages

Wireshark DNS v7.0

Uploaded by

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

Wireshark Lab: DNS v7.

0
Supplement to Computer Networking: A Top -Down
Approach, 7th ed., J.F. Kurose and K.W. Ross

“Tell me and I forget. Show me and I remember. Involve me and I


understand.” Chinese proverb

© 2005-2016, J.F Kurose and K.W. Ross, All Rights Reserved

1. Tracing DNS with Wireshark

Now that we are familiar with nslookup and ipconfig, we’re ready to get down to some
serious business. Let’s first capture the DNS packets that are generated by ordinary
Websurfing activity.

• Use ipconfig to empty the DNS cache in your host.


• Open your browser and empty your browser cache. (With Internet Explorer,
go to Tools menu and select Internet Options; then in the General tab select
Delete Files.)
• Open Wireshark and enter “ip.addr == your_IP_address” into the filter, where
you obtain your_IP_address with ipconfig. This filter removes all packets that
neither originate nor are destined to your host.
• Start packet capture in Wireshark.
• With your browser, visit the Web page: http://www.ietf.org
• Stop packet capture.

Answer the following questions. Whenever possible, when answering a question below,
you should hand in a printout of the packet(s) within the trace that you used to answer the
question asked. Annotate the printout1 to explain your answer. To print a packet, use
File->Print, choose Selected packet only, choose Packet summary line, and select the
minimum amount of packet detail that you need to answer the question.

1 What do we mean by “annotate”? If you hand in a paper copy, please highlight where in the printout
you’ve found the answer and add some text (preferably with a colored pen) noting what you found in what
you ‘ve highlight. If you hand in an electronic copy, it would be great if you could also highlight and
annotate.
1. Locate the DNS query and response messages. Are then sent over UDP or
TCP?
2. What is the destination port for the DNS query message? What is the source port
of DNS response message?
3. To what IP address is the DNS query message sent? Use ipconfig to determine the
IP address of your local DNS server. Are these two IP addresses the same?
4. Examine the DNS query message. What “Type” of DNS query is it? Does the
query message contain any “answers”?
5. Examine the DNS response message. How many “answers” are provided? What
do each of these answers contain?
6. Consider the subsequent TCP SYN packet sent by your host. Does the destination
IP address of the SYN packet correspond to any of the IP addresses provided in
the DNS response message?
7. This web page contains images. Before retrieving each image, does your host
issue new DNS queries?

Now let’s play with nslookup2.

• Start packet capture.


• Do an nslookup on www.mit.edu
• Stop packet capture.

You should get a trace that looks something like the following:

2 If you are unable to run Wireshark and capture a trace file, use the trace file dns-ethereal-trace-2 in the
zip file http://gaia.cs.umass.edu/wireshark-labs/wireshark-traces.zip
We see from the above screenshot that nslookup actually sent three DNS queries and
received three DNS responses. For the purpose of this assignment, in answering the
following questions, ignore the first two sets of queries/responses, as they are specific to
nslookup and are not normally generated by standard Internet applications. You should
instead focus on the last query and response messages.
8. What is the destination port for the DNS query message? What is the source port
of DNS response message?
9. To what IP address is the DNS query message sent? Is this the IP address of your
default local DNS server?
10. Examine the DNS query message. What “Type” of DNS query is it? Does the
query message contain any “answers”?
11. Examine the DNS response message. How many “answers” are provided? What
do each of these answers contain?
12. Provide a screenshot.

Now repeat the previous experiment, but instead issue the command:

nslookup –type=NS kletech.ac.in


Answer the following questions3 :

16. To what IP address is the DNS query message sent? Is this the IP address of your
default local DNS server?
17. Examine the DNS query message. What “Type” of DNS query is it? Does the
query message contain any “answers”?
18. Examine the DNS response message. What MIT nameservers does the response
message provide? Does this response message also provide the IP addresses of the
MIT namesers?
19. Provide a screenshot.

3 If you are unable to run Wireshark and capture a trace file, use the trace file dns-ethereal-trace-3 in the
zip file http://gaia.cs.umass.edu/wireshark-labs/wireshark-traces.zip

You might also like