0

As mentioned here, having a Reverse PTR record is key for successful email sending and delivery from one's own server. In order to check if it's correctly set for my server, I tried:

dig -x 111.111.111.111    #  replace with the IP of a server

but the answer is:

; <<>> DiG 9.9.5-3ubuntu0.1-Ubuntu <<>> -x 111.111.111.111
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 29789
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;xxx.xxx.xxx.xxx.in-addr.arpa.     IN      PTR

;; Query time: 27 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Sep 10 14:51:32 CEST 2017
;; MSG SIZE  rcvd: 54

I don't see anything that looks like a Reverse PTR record.

I tried with various IPs obtained from well-known websites: dig -x 151.101.1.69 (obtained from ping stackoverflow.com), and it looks the same.

Why can't I see any Reverse PTR record with dig?

Basj
  • 709
  • 3
  • 11
  • 29
  • Not every IP address has a PTR record, and the one you picked by SO is one of those (it's not used for mail...). Do this check for something mail related. Also read https://meta.serverfault.com/questions/963/what-information-should-i-include-or-obfuscate-in-my-posts - if you had posted your IP, others could check if they get a good PTR for it . – Sven Sep 10 '17 at 13:07
  • @Sven I tried the same with the IP got from `ping smtp.gmail.com` (74.125.206.109) and it's the same. I even cannot find any single working IP that has such a record. – Basj Sep 10 '17 at 13:11
  • Then there is something wrong with your client's DNS config. – Sven Sep 10 '17 at 13:14
  • "SERVER: 127.0.0.1#53" seems 127.0.0.1 isn't functioning properly. – Appleoddity Sep 10 '17 at 13:16
  • Status code was `SERVFAIL`, check the logs? – Håkan Lindqvist Sep 10 '17 at 14:34

1 Answers1

0

I tried from another server and it works:

;; ANSWER SECTION:
xxx.xxx.xxx.xxx.in-addr.arpa. 86399 IN     PTR     ns328xxxx.ip-xxx-xxx-xxx.eu.

so it should be a local server problem (as mentioned by someone in a comment).

Basj
  • 709
  • 3
  • 11
  • 29