572
edits
Changes
→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 sometimes necessary to convert addresses back into human readable names. For public IP addresses only your ISP can provide this service for you. For private networks you can set it up for your own organisation. But even if you're setting up reverse DNS on the public internet - you need to understand what information the ISP would require.
Issue the following commands on any of your VMs (once again replacing X XX with your network octet):
<source>
host 192.168.XXX.1host 192.168.XXX.2host 192.168.XXX.3host 192.168.XXX.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 XX with your own octet):
<pre>
zone "XXX.168.192.in-addr.arpa." {
type master;
file "mydb-for-192.168.XXX";
};
</pre>
1D ; Negative Cache TTL
);
@ IN NS host.yoursenecaid.ops.1 IN PTR host.yoursenecaid.ops.
</pre>