You migrate prod SMTP to a new dedicated IP. Internal tests pass. B2B customers complain: "Alerts hit spam since Tuesday." SPF/DKIM score perfect. Digging: PTR points to ip-54-37-xxx.pool.example.net while the server says HELO mail.example.com.
Reverse DNS is the IP identity card for spam filters. Neglectable on a blog; critical on transactional mail or poorly isolated shared outbound relays.
Forward vs reverse
Forward DNS: name → IP. Reverse (PTR): IP → name. Only the IP block holder publishes PTR via .in-addr.arpa or .ip6.arpa.
Many teams configure A/MX/SPF but forget a PTR ticket at OVH, Scaleway, AWS, or Hetzner.
FCrDNS and HELO
Forward-confirmed reverse DNS: PTR(A) = originating IP.
| Element | Good | Bad |
|---|---|---|
| PTR | mail.example.com | generic pool |
| A record | same IP | missing/other IP |
| HELO | mail.example.com | localhost/raw IP |
Test: dig -x IP then dig mail.example.com A.
Delegation at the host
On VPS/cloud, PTR is set in panel or via support API. Plan before IP cutover: PTR propagation can take hours.
On shared outbound IP, you often inherit generic PTR — reason to use an ESP or dedicated IP for pro mail.
IPv6 and multi-IP
Each outbound SMTP IP needs consistency. ESP rotation pools handle this; self-hosted, document every IP in spam incident runbooks.
Continuous monitoring
Alert if PTR vanishes after migration, rebuild, or /64 change. Include rDNS in post-deploy checks alongside TLS and SPF.
IP deliverability checklist
- Request custom PTR aligned with SMTP hostname.
- Create forward A record to same IP (FCrDNS).
- Configure matching HELO/EHLO.
- Verify SPF includes hostname if direct send.
- Test
dig -x IPexternally. - Send mail-tester.com sample and note rDNS score.
- Monitor alert if PTR changes after reboot/migration.
- Separate transactional and marketing IP.
- Document support PTR ticket per IP.
- Review after cloud instance upgrade (IP change).
Each step takes minutes except PTR propagation — plan before major mail campaign or client requiring IP whitelist.
Marketing teams sometimes ask to "send from Mailchimp AND the server" without understanding two IPs mean two PTRs and two reputations to warm. Document which channel uses which IP before opening port 25 on a new instance.
When moving to a new host, PTR does not migrate automatically with the SQL dump: plan it in the same window as IP cutover, not after spam complaints.
Enterprise B2B filters whitelist by IP and check rDNS: missing PTR blocks whole contracts, not just the founder's Gmail inbox.
Deliverability monitoring
Set up Gmail Postmaster Tools and Microsoft SNDS for IP reputation tracking after any rDNS or IP change.
Inbox placement tests weekly during IP warm-up — not only spam score snapshots.
Document rDNS in onboarding checklist for any new outbound mail infrastructure.
Operational summary
FCrDNS alignment (PTR, A, HELO) supports mail deliverability alongside SPF/DKIM/DMARC. Request PTR before sending from new IP. Warm IP reputation gradually. Monitor Postmaster Tools after any mail infrastructure change.
Keep a dated runbook, before/after metrics, post-incident review — cumulative discipline beats Friday night panic.
Keep a dated runbook, before/after metrics, post-incident review — cumulative discipline beats Friday night panic.
Keep a dated runbook, before/after metrics, post-incident review — cumulative discipline beats Friday night panic.
Keep a dated runbook, before/after metrics, post-incident review — cumulative discipline beats Friday night panic.
Keep a dated runbook, before/after metrics, post-incident review — cumulative discipline beats Friday night panic.
Keep a dated runbook, before/after metrics, post-incident review — cumulative discipline beats Friday night panic.
IP warm-up
Two-week volume ramp post migration. Documented PTR ticket — support sometimes slow.
Decide and move forward without blind spots
- Request a custom PTR aligned with the SMTP hostname — host or cloud support ticket with noted propagation delay.
- Create forward A (FCrDNS) — PTR must resolve to the same IP that sends mail.
- Align HELO/EHLO — match PTR; verify SPF if sending directly from the VPS.
- Test externally —
dig -x IPand mail-tester.com before campaigns or clients requiring IP whitelisting. - Separate transactional and marketing IP — two reputations, two documented PTR tickets.
Compare VPS and dedicated mail offers in our directory and comparison tool; our guides cover deliverability.
Frequently asked questions
Who configures PTR?
The IP block owner — often your host or cloud provider. You request PTR; you do not create it in forward DNS.
Must PTR equal SMTP hostname?
PTR must resolve to a name that forward-resolves to the same IP (FCrDNS). HELO/EHLO should match that name.
Impact on Gmail and Microsoft?
They often penalize missing PTR, generic ip-xx.pool PTR, or HELO/PTR mismatch — especially on new IPs or transactional volume.
What about IPv6?
Same logic: nibble format, provider rDNS delegation, AAAA/PTR/HELO consistency.
Before sending the first prod mail from a new IP, verify FCrDNS — not after the first spam ticket.