[go: up one dir, main page]

0% found this document useful (0 votes)
38 views5 pages

DNS Report Format1

The report details a DNS lab exercise conducted by Yashdeep, including the IP address of the campus and DNS servers. It outlines the results of DNS queries, the structure of DNS messages, and the interpretation of query and response sections. Key technical details such as IP addresses, port numbers, and flags in DNS messages are also provided.

Uploaded by

ayushvre1shete
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
38 views5 pages

DNS Report Format1

The report details a DNS lab exercise conducted by Yashdeep, including the IP address of the campus and DNS servers. It outlines the results of DNS queries, the structure of DNS messages, and the interpretation of query and response sections. Key technical details such as IP addresses, port numbers, and flags in DNS messages are also provided.

Uploaded by

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

Report for Lab 2-6: DNS

Name: Yashdeep Student ID: 123CS0077 Date: 21 Jan 2025

Part I

1 IP address of your campus: 173.236.138.213

2
Name and IP addresses of DNS servers who can provide and authoritative answers to your query:

iiitk.ac.in. 2320 IN NS ns1.dreamhost.com.

iiitk.ac.in. 2320 IN NS ns3.dreamhost.com.

iiitk.ac.in. 2320 IN NS ns2.dreamhost.com.


3
Result and interpretation of query with trace option:

 The IP address 173.236.138.213 is the final result.


 The query starts at the root servers and traverses the DNS hierarchy:
1. Root servers → Provide .org TLD nameservers.
2. TLD nameservers → Provide the authoritative nameservers for iiitk.ac.in.

3. Authoritative nameservers → Provide the A record for iiitk.ac.in


4
IP of your mail server:

iiitk.ac.in. 300 IN MX 5 ALT1.ASPMX.L.GOOGLE.COM.

iiitk.ac.in. 300 IN MX 5 ALT2.ASPMX.L.GOOGLE.COM.

iiitk.ac.in. 300 IN MX 10 ALT3.ASPMX.L.GOOGLE.COM.

iiitk.ac.in. 300 IN MX 10 ALT4.ASPMX.L.GOOGLE.COM.

iiitk.ac.in. 300 IN MX 1 ASPMX.L.GOOGLE.COM.


Part II

1 Host name: DESKTOP-TAR1TKK

2 Connection-Specific DNS suffix: No connection specific DNS Prefix since using DHCP

3 Physical (data-link layer) address: 98-E7-43-1D-4D-27

4
IP address:

IPv4 Address: 172.16.100.30


5 IP address of the Default Gateway: 172.16.100.1

Part III
1 Do DNS messages use the service of UDP or TCP? UDP

2 Source and destination port numbers of the query message: Source: 60493 Destination: 53

3 Source and destination port numbers of the response message: Source: 53 Destination: 60493

4 IP address and network to which the query message is sent: 8.8.8.8 (Network : Google DNS
Server)
5
Query message ID number: 0xd609

Response message ID number? 0xd609

Purpose of ID number: The ID Number in DNS request and response packets serves as a
unique identifier to match queries with their corresponding responses.
6 Number of bits in flag fields in DNS message: 16 bits

7 Which bit determines if the message is query or response? First (or most significant) bit

8
Which bits are only used in the response message?

1. Response (R) Bit ( 1st bit)


2. Authoritative Answer (AA) (5th bit)
3. Recursion Available (RA) (8th bit)
4. Response Code (RCODE) (last 4 bits)

Purpose of these bits:

1. Indicates whether the message is a query (0) or a response (1).


2. Indicates if the responding server is authoritative for the queried domain.
3. Indicates if the server supports recursion for the client.
4. Specifies the status of the response.

9
Number of question records in the query: 1 Number of answer records in the query: 0

Number authority records in the query: 0 Number of addition records in the query: 0
1
0 Interpret the information in the Question and Answer sections of the packets:

Question Section:

Purpose: Describes the client’s query.

Fields:

o Name: The domain name being queried (e.g., example.com).


o Type: The record type requested (e.g., A, AAAA, MX).
o Class: Usually IN (Internet).

Answer Section:
Purpose: Contains the server’s response.

Fields:

o Name: The domain name in the response.


o Type: The record type returned (e.g., A, MX).
o TTL: Time to Live for caching.
o Data: Resolved information (e.g., IP address for A records).

Screenshots

You might also like