Gmail's sender guidelines require valid forward and reverse DNS. Missing or generic PTRs are a classic spam signal and cause outright rejections at many gateways.
How to implement reverse DNS (PTR) records#
- Ask your hosting or ESP provider to set a PTR for each sending IP.
- Use a hostname under your domain (mail1.example.com) rather than the provider's generic name.
- Create the matching A record so forward and reverse agree.
- Use the same hostname in the SMTP HELO/EHLO banner.
How to verify it worked#
Send a test message to seed mailboxes at Gmail, Outlook, and Yahoo, then inspect the Authentication-Results and delivery headers. Repeat after any DNS or sending-platform change.
Common mistakes#
- Generic PTRs like 203-0-113-10.provider.net.
- HELO names that do not match the PTR.
Frequently asked questions#
Can I set PTR records in my own DNS?
No. PTRs live in the IP owner's reverse zone. Your hosting provider or ESP sets them, though some offer self-service.