IT 3100: Systems Design and Administration I
Domain Name System (DNS) Reverse Domain
Due according to the class schedule.
In this assignment you will modify your authoritative domain name servers to serve reverse DNS (PTR) records. You will register the reverse domain name with the registrar and configure IP to name translations in your authoritative servers.
Throughout the semester these servers must be functioning correctly. As systems are added, removed or changed in your domain, these servers must stay current.
Register a reverse domain
Identify the correct reverse zone for your ip addresses.
Register your reverse domain name with the registrar.
Email the fully qualified domain names of your two name servers, and the name of your reverse zone to the instructor.
The format of this message should be two text lines of this form:
0-22.214.171.124.in-addr.arpa [ "ns1.dsutux.us.", "ns2.dsutux.us.", ],
Of course, substitute the correct information for your zone.
Note the trailing “.” on the hostnames. The subject must include
IT3100 Reverse DNS.
Configure the master authoritative name server
Configure the master authoritative server to also be the master for your reverse domain.
Be sure to include PTR records for all
A entries in your
Configure the slave authoritative name server
Configure the slave authoritative server to transfer the reverse zone data from the master.
The following details are required:
- Your reverse zone is
aaais the first number in your control, and
bbbis the last number in your control.
cccis something like 214, 215, 216, etc. depending on your assigned numbers. For example, my zone is
Arecord in your main forward zone should have a matching
PTRrecord in your reverse zone.
- Allow hosts from any IP address to lookup information about your domain.
- Only allow your secondary name servers (and localhost) to transfer the entire zone.
- The master should automatically notify your secondary servers of changes to your zone.
Verify that your domain is being served correctly. There are at least the following cases to consider:
- The query is from one of your authoritative servers.
- The query is from one of your other systems.
- The query is from a system in the CIT network.
The query is from a system outside CIT network.
The query is for an existing translation.
The query is for a non-existing translation.
The query is for an IP outside your range.
The query uses a caching lookup server in the CIT network.
The query uses a caching lookup server in the DSU network.
The query uses a caching lookup server outside the DSU and CIT networks.
Check for combinations and look for the correct results.
Submission File Format
The submission file is a UNIX text file, and must have this format, exactly!
The file must be named
master: ip_address_of_your_master slave: ip_address_of_your_slave domain: name.of.your.domain ns1: name.of.your.ns1 ns2: name.of.your.ns2 hosts: names.of.hosts.in.your.domain:ip.of.host, names.of.hosts.in.your.domain:ip.of.host reverse: name.of.your.reverse.domain
For example, my file would look like this:
master: 126.96.36.199 slave: 188.8.131.52 domain: dsutux.us ns1: ns1.dsutux.us ns2: ns2.dsutux.us hosts: mail.dsutux.us:184.108.40.206, www.dsutux.us:220.127.116.11, ns1.dsutux.us:18.104.22.168, ns2.dsutux.us:22.214.171.124, users.dsutux.us:126.96.36.199, resources.dsutux.us:188.8.131.52 reverse: 0-184.108.40.206.in-addr.arpa
Submission and Passoff
- Use the Submisions link at the
top of the page to submit your text file to the
Last Updated 08/07/2020