A PTR record maps an IP address back to a name — reverse DNS. Mail receivers check it on every sending server: an address without reverse DNS, or with one that does not point back, is treated as suspicious or refused.
| Type number | 12 |
| Lives under | in-addr.arpa (IPv4) and ip6.arpa (IPv6) |
| Set by | Whoever owns the IP address — your host or ISP |
| Defined in | RFC 1035 §3.5 |
Look up the PTR records of any name
One question to DNS, answered as it is — enter an IP address for its reverse DNS. You can change the record type too.
What it does
The address is written backwards under a special domain: 203.0.113.7 becomes 7.113.0.203.in-addr.arpa. Because that reverse zone belongs to the owner of the address block, you cannot publish a PTR record in your own domain’s DNS; you set it in your server provider’s panel, or ask them.
Receivers want forward-confirmed reverse DNS: the PTR name must itself have an A (or AAAA) record pointing back to the same address. Gmail rejects mail from servers without it (550 5.7.25).
How it is written
| Field | Meaning |
|---|---|
| Name | The reversed address under in-addr.arpa or ip6.arpa |
| Value | The host name |
Examples
7.113.0.203.in-addr.arpa. IN PTR mail.example.com.
The address 203.0.113.7 is mail.example.com — which should resolve back to 203.0.113.7.
Common mistakes
- Looking for the PTR setting in your domain’s DNS panel, where it cannot be set.
- A generic PTR from the host (ip-203-0-113-7.provider.net) on a mail server — valid, but it looks like a home connection to some receivers.
- A PTR name without a matching A record.
What we recommend
For every server that sends mail, set reverse DNS to a name in your own domain, and give that name an A (and AAAA) record back to the address.
Gmail 550 5.7.25: no PTR record →
Send a test email and see your server’s reverse DNS →
Sources
Checked on 25 September 2026 against these official sources:
- RFC 1035: Domain names — rfc-editor.org