dig -x 1.2.3.4
If 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.server# dig SOA -x 66.51.122.131
; <<>> DiG 9.6.1-P1 <<>> SOA -x 66.51.122.131
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49196
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;131.122.51.66.in-addr.arpa. IN SOA
;; AUTHORITY SECTION:
122.51.66.in-addr.arpa. 1681 IN SOA tera-byte.com. hostmaster.tera-byte.com. 2010032522 3600 900 604800 1800
server# dig -x 66.51.122.131
; <<>> DiG 9.6.1-P1 <<>> -x 66.51.122.131
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36799
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3
;; QUESTION SECTION:
;131.122.51.66.in-addr.arpa. IN PTR
;; ANSWER SECTION:
131.122.51.66.in-addr.arpa. 3319 IN PTR ip-66-51-122-131.tera-byte.com.
zone "4.3.2.1.in-addr.arpa" IN {
type master;
file "/var/named/hostname.db";
};
$TTL 0
@ IN SOA ns1.domain.com. root.domain.com. (
2004022000
7200
3600
1209600
86400 )
NS ns1.domain.com.
NS ns2.domain.com.
PTR domain.com.