Question

PTR reverse look up failing

  • Posted June 13, 2014

Hi On June 12th sometime ns2.digitalocean.com seems to have stopped reporting PTR records for my domains causing emails to not be delivered. Mail acceptance has been working fine since the beginning for two drops 192.241.218.28 & 198.199.94.20 and now is being rejected Any pointers as to why? thanks

on digitaldrop 192.241.218.28 from mail.log ((works))) Jun 11 02:05:07 azonde postfix/pickup[3370]: AEE68120C0B: uid=0 from=<root> Jun 11 02:05:07 azonde postfix/cleanup[3446]: AEE68120C0B: message-id=20140611090507.GA3435@azonde.info Jun 11 02:05:07 azonde postfix/qmgr[802]: AEE68120C0B: from=root@azonde.info, size=4689, nrcpt=1 (queue active) Jun 11 02:05:11 azonde postfix/smtp[3449]: AEE68120C0B: to=neilhlow@sonic.net, orig_to=neilh20@azonde.com, relay=mailin-02.mx.sonic.net[69.12.210.172]:25, delay=3.4, delays=0.04/0.01/2.7/0.67, dsn=2.0.0, status=sent (250 2.0.0 s5B957se000793 Message accepted for delivery) Jun 11 02:05:11 azonde postfix/qmgr[802]: AEE68120C0B: removed

((stopped working)) Jun 12 02:05:09 azonde postfix/smtp[4041]: 0BF8F120EA2: to=neilhlow@sonic.net, orig_to=neilh20@azonde.com, relay=mailin-01.mx.sonic.net[69.12.210.174]:25, delay=2.3, delays=0.03/0/2.3/0.04, dsn=4.3.3, status=deferred (host mailin-01.mx.sonic.net[69.12.210.174] said: 451 4.3.3 192.241.218.28 does not have matching forward and reverse dns (FAIL) [orthrus:DNS0] (in reply to RCPT TO command))

http://mxtoolbox.com/SuperTool.aspx?action=ptr%3A192.241.218.28&run=toolpage reports: ptr:192.241.218.28 ptr
No ptr Records exist

smtp diag blacklist port scan subnet tool Reported by ns2.digitalocean.com on 6/13/2014 at 12:43:33 AM (UTC -5), just for you. (History) Transcrip

Subscribe
Share

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

@ asb Does this also mean that in my OS I also need to set the hostname to actually be the FQDN instead of just the hostname?

In the DigitalOcean Control Panel, make sure that the hostname you’ve assigned to your droplet is a fully qualified domain name (FQDN). So, if your mailserver identifies itself as mail.domain.com, then you would want to make sure the name of the droplet is mail.domain.com. Until you do this rDNS is not going to be possible.