1,760
edits
Changes
→Running and testing the DNS server
* use the "ss" command or the netstat command - what information should you look for?
== Test the correctness of your DNS server's responses ==
* <font color='blue'><b>use the nslookup DNS client command line utility to query your DNS server for SOA, NS, A, and PTR resource records.</b></font>Capture the DNS query commands and their corresponding outputs to a file named "[student-id]-lab2-test-output.txt"
For example, if an authoritative DNS server with IP address 192.168.99,53 has the cp.net zone file:
<pre>
Address: 192.168.99.25
</pre>
== Capture and study the DNS query traffic ==
* Run the appropriate "tcpdump" command on your DNS server to capture all DNS query and response packets to a file and name the tcpdump capture file as [student-id]-lab2-dns-packet. While tcpdump is running on your DNS server, repeat all the DNS queries (SOA, NS, A, PTR) on your host. If you have firewall (iptables or firewalld) running on your DNS server, make sure that the port for DNS are opened on the firewall.
= Completing the Lab =
* Create the directory /root/lab2 on your DNS server.
* Make a copy of the DNS server configuration file "named.conf" to the /root/lab2 directory and named it as "named.conf.txt"
* Copy your forward lookup zone file "my-zone.txt" to the /root/lab2 directory.
* Copy your reverse lookup zone file "rev-zone.txt" to the /root/lab2 directory.
* Upload all the files in the "/root/lab2" directory to blackboard by the due date.