|Any modern version of DA will be able to do this through the interface.|
Go to: Admin Level -> DNS Administration
Scroll to the bottom to the "Add Zone" section.
Enter your information normally:
domain name: server.hostname.com
where server.hostname.com is the hostname of your server.
The IP is your server IP (license IP)
and ns1/ns2 can be any NS your server uses.
Click the "Create Reverse IP Lookup" checkbox, then click "Add".
Wait a minute or so, then go into ssh to see if it worked:
dig -x 184.108.40.206If it works, then you'll see a PTR record with your server name. If it doesn't you'll see a value that says "SOA" with likely your datacenters name beside it. This means that your datacenter has control over the lookup, so you'll have to contact them to set it up, as your server isn't queried when the lookup is done, even if it's correctly setup on your server.
For example, the IP of directadmin.com is 220.127.116.11. To check who has authority over the lookup, we can use SOA in the dig to see who controls the lookup on the IP:
server# dig SOA -x 18.104.22.168
server# dig -x 22.214.171.124
The old fashioned/manual way to add the lookup (depreciated):
To add a reverse lookup on the IP 126.96.36.199, in your named.conf (RH: /etc/named.conf FBSD: /etc/namedb/named.conf) add
Note that the IP is written backwards (188.8.131.52).
Now the domain.com. that is in bold will be what is returned with the lookup. You can apply the hostname.db file to all IPs if you want, just add one zone for each ip in the named.conf using the above method.
*Note: If you do not have authority over the reverse lookup on the IP's you'll have to contact your datacenter to get them to do it for you. This means that your server might not be used at all for the reverse lookup on the IPs, making this tutorial useless :)
© 2018 JBMC Software, Suite 173 3-11 Bellerose Drive, St Albert, AB T8N 1P7 Canada. Mon-Fri 9AM-5PM MST