What Is a PTR Record? Reverse DNS for Mail Servers Explained

A PTR record (pointer record) is the reverse of an A record: it maps an IP address back to a hostname. Receiving mail servers look up the PTR of every IP that connects to them and expect it to name a real mail host whose forward A record resolves to the same IP. A missing or mismatched PTR is one of the oldest and most reliable spam signals, and many receivers reject mail from such IPs outright.

Quick summary

• That a PTR exists at all. No PTR usually means a residential or unassigned IP, and Gmail, Outlook and most corporate gateways refuse or defer such connections.
• That the PTR hostname resolves forward to the same IP (forward-confirmed reverse DNS).
• That the PTR looks like a mail host rather than a generic pool name such as 203-0-113-10.dynamic.isp.net, which is treated as a consumer IP.
• That the HELO or EHLO name the sender announces matches, or at least belongs to the same domain as, the PTR.
• Run nslookup 203.0.113.10 (Windows) or dig -x 203.0.113.10 (macOS, Linux). The answer is the PTR hostname.

How reverse DNS works

Reverse lookups live in a special DNS tree called in-addr.arpa (ip6.arpa for IPv6). The IP 203.0.113.10 is reversed and queried as 10.113.0.203.in-addr.arpa, and the PTR record there answers with a hostname. Because the in-addr.arpa zone for an address block belongs to whoever was allocated the block, the PTR is set by the hosting or network provider that owns the IP, not in your domain DNS panel.

Example: forward-confirmed reverse DNS

IP        203.0.113.10
PTR       10.113.0.203.in-addr.arpa  ->  mail.oqumail.com
A         mail.oqumail.com                 ->  203.0.113.10

Both directions agree = FCrDNS pass

What receivers check

• That a PTR exists at all. No PTR usually means a residential or unassigned IP, and Gmail, Outlook and most corporate gateways refuse or defer such connections.
• That the PTR hostname resolves forward to the same IP (forward-confirmed reverse DNS).
• That the PTR looks like a mail host rather than a generic pool name such as 203-0-113-10.dynamic.isp.net, which is treated as a consumer IP.
• That the HELO or EHLO name the sender announces matches, or at least belongs to the same domain as, the PTR.

How to look up a PTR record

1. Run nslookup 203.0.113.10 (Windows) or dig -x 203.0.113.10 (macOS, Linux). The answer is the PTR hostname.
2. Then run nslookup on that hostname to confirm it resolves back to the same IP.
3. Use MXToolbox Reverse Lookup if you prefer a browser.
4. If you are the sender, the delivery log for a rejected message often quotes the receiver reason, such as "PTR record does not match" or "no reverse DNS".

Common PTR mistakes

• Trying to add a PTR record in the domain DNS panel at Cloudflare or a registrar. It has no effect; the record must be set in the hosting provider control panel or by a support request.
• Setting a PTR to a hostname that has no A record, or an A record pointing to a different IP.
• Sending from a dynamic or residential IP. No PTR you can set will make that IP acceptable.
• Running mail from a cloud server whose provider only assigns a generic PTR and does not allow changes on the plan.

Why you do not need to manage PTR with OquMail

When you use OquMail, your mail leaves from OquMail servers whose IPs already have matching PTR and A records and an established history with receivers. You never touch reverse DNS; you only publish the MX, SPF, DKIM and DMARC records the dashboard shows, then confirm them with Check DNS. Setting up your own mail server is where PTR problems begin, which is one of the main reasons hosted mail is simpler for a small business.

PTR and the HELO name together

Receivers compare three things: the PTR of the connecting IP, the A record of that PTR name, and the hostname the sender announces in its EHLO greeting. When all three agree, the connection looks like a properly run mail server. When the PTR says one thing and EHLO says another, filters add points even if the mail is otherwise clean. A hosted provider keeps these consistent across all of its outbound servers.

Common questions

Do I need a PTR for my domain?

Domains do not have PTR records; IP addresses do. Your domain needs MX and TXT records. The IP your mail provider sends from needs the PTR, and that is their job.

Can one IP have several PTR records?

Technically yes, but mail receivers dislike it. One IP, one PTR, matching one A record is the expectation.

Does a PTR affect receiving mail?

Not directly. Senders connect to the host named in your MX; it is the sending side that gets judged by reverse DNS.