Home / server / Questions / 821179
In Process
Cédric Girard
Asked: 2016-12-17 09:04:34 +0800 CST

Reverse DNS defined, but still not found by a server

  • 772

I defined a reverse DNS for the public IP of our SMTP

http://mxtoolbox.com/SuperTool.aspx?action=ptr%3a95.131.137.225&run=toolpage

But still, the mail server of one of our customer answer

The mail system

: host mail2.domain.fr[xx.xx.xx.xx] refused to talk to me: 553 A reverse DNS record could not be found for 95.131.137.225

Final-Recipient: rfc822; [email protected] Original-Recipient: rfc822;[email protected] Action: failed Status: 4.0.0 Remote-MTA: dns; mail2.domain.fr Diagnostic-Code: smtp; 553 A reverse DNS record could not be found for 95.131.137.225

Why ?

smtp reverse-dns

1 Answers

  1. Their mail server (or more likely another DNS server in between), has already looked up that IP and cached the response. Give it a day or two and the old response should eventually expire and look up the new record. Usually it happens much quicker than this, and usually a "no record found" response is not cached as readily as a "record found" response. But maybe in this case it is configured differently. Give it time and should start working soon. If it doesn't, then their DNS config is broken or for some reason cannot talk to the necessary DNS server to get your record.

    • 1