932
edits
Changes
m
Partially complete edit of putting reverse lookups back in.
'''Record steps, commands, and your observations in INVESTIGATION 2 in your OPS335 lab log-book'''
= INVESTIGATION 3: CONFIGURING THE DNS SERVER FOR REVERSE LOOKUPS =
As it stands now, your server will only handle forward resolution (converting names into addresses), but it is also common to need to convert addresses back into human readable names. In some situations an ISP will provide this service for you, but most organizations at least need to handle their own internal addresses. You also need to understand what information the ISP would require.
Issue the following commands on any of your VMs (once again replacing X with your network octet):
<source lang="bash">
host 192.168.X.1
host 192.168.X.2
host 192.168.X.3
host 192.168.X.4</source>
Each one should have failed because there is currently nothing that will handle this reverse lookup for you. This requires another zone on your server.
Add the following entry to your '''/etc/named.conf''' (once again replacing X with your own octet):
<pre>
zone "X.168.192.in-addr.arpa." {
type master;
file "mydb-for-192.168.X";
};
</pre>
And create the following zone file:
<pre>
$TTL 3D
@ IN SOA vm1.yoursenecaid.org. hostmaster.yoursenecaid.org.(
2016010301 ; Serial
8H ; Refresh
2H ; Retry
1W ; Expire
1D ; Negative Cache TTL
);
@ IN NS vm1.yoursenecaid.org.
vm1 IN A 192.168.X.2
2 IN PTR vm1.yoursenecaid.org.
</pre>
