Reverse DNS for mail

Reverse DNS for mail means the PTR on your sending IP returns a hostname, and the A record for that hostname points back to the same IP. Receivers also expect that hostname to match the name your mail software uses in HELO or EHLO. When those three pieces agree, delivery is far more reliable. Shared hosting mail IPs already have reverse DNS set for you. On a VPS or dedicated server you run the mail stack, so you align the name before you send campaign mail.

Align the three names first

Pick one hostname you will keep for outbound mail and use it everywhere that matters. Set it as the HELO name in Postfix, Exim, or your Windows SMTP settings so the server no longer greets as localhost.localdomain. Request or set the PTR on the sending IP to that same hostname. Add an A record for the hostname that points at the sending IPv4 address, and add AAAA if you also send over IPv6. Then send one test message to a mailbox you control and read the Received header, not a dashboard label. That header shows the name and IP the remote side actually saw.

Check forward and reverse with dig

You can verify the loop from the command line once DNS has had time to update. The inner lookup asks for the PTR. The outer lookup asks whether that name resolves back to the same address.

dig +short $(dig +short -x 203.0.113.40)

Replace 203.0.113.40 with the IP that actually sent the message. The Received header tells you which address was used if the server has more than one. If the inner name is empty, reverse DNS is not set on that IP. If the outer address differs from the IP you queried, you have a forward and reverse mismatch. Reverse DNS is per address, so a HELO tied to one IP with a PTR on another still fails the check.

IPv6, hostnames that change, and timing

If you send mail over IPv6, that address needs a matching PTR as well. Many filters still weigh IPv4 heavily, but dual-stack sending needs a consistent story on both. Watch for cloud-init or other boot scripts that rewrite the system hostname overnight, because that can desync HELO from PTR without changing reverse DNS itself. Fix the hostname source, then recheck HELO and the dig loop. Set reverse DNS before the first real campaign, not after the first blocklist hit. Shared mail IPs are already handled. On VPS and dedicated servers, reverse DNS is part of getting outbound mail ready.