Where you saw it: A bounce naming reverse DNS, a mail tester flagging rDNS, or heavy filtering at receivers that check it while everything else in your setup looks correct.
Why it happens
- The PTR record was set to a hostname that was later changed or removed on the forward side.
- The server was renamed and only one half of the DNS pair was updated.
- A hosting provider set a generic PTR record that points at their own infrastructure rather than yours.
- The IP was reassigned and the previous customer's PTR record stayed behind.
- The forward record points at a load balancer or a different address in the same range.
The fix, in order
Get the current PTR record
Run dig +short -x your.sending.ip. The answer is the hostname receivers will see when they check you.
Resolve that hostname forward
Run dig +short A on the hostname you just got. It must return the same IP you started with. Anything else is the mismatch.
Fix whichever half is wrong
PTR records are controlled by whoever owns the IP, usually your hosting or mail provider, and A records are controlled by you. Decide which one should change before opening a ticket.
Use a hostname that means something
Point it at mail.yourdomain.com rather than a generic provider hostname. Receivers weigh a PTR that matches your sending domain more favorably than one that looks like shared hosting.
Match the HELO name too
The hostname your server announces at HELO should match the PTR record. Receivers that check rDNS frequently check this as well.
dig +short -x 198.51.100.25
dig +short A mail.example.comThe second command must return the IP from the first.
How to know it worked
The short version
- dig +short -x IP returns a hostname, and dig +short A on that hostname returns the same IP.
- A mail tester reports reverse DNS as passing.
- Your HELO name matches the PTR hostname.
Questions people ask
How much does reverse DNS matter?
Enough that some receivers refuse connections without it. Deutsche Telekom is strict about it, and several large receivers weigh it in filtering. It is cheap to fix and not optional for a serious sending IP.
Who sets the PTR record?
Whoever owns the IP address block, which means your hosting or mail provider. You cannot set it in your own DNS panel.
Does this affect verification too?
Yes. Our probe hosts need matching forward and reverse DNS or some receivers refuse the connection, which shows up as lower coverage rather than as an error.