What is a PTR record? Reverse DNS clearly explained
Published on June 19, 2026 8 min read
A PTR record links an IP address to a hostname. Learn what reverse DNS is, who sets up the PTR record, and how to check it for your email.
A PTR record links an IP address back to a hostname, which forms the basis of reverse DNS: the opposite of a normal A or AAAA lookup. If you run your own mail server or VPS, a PTR record is essential. Without a correct PTR record, major email providers such as Gmail and Yahoo can reject your outgoing mail or send it to the spam folder. If you send mail through your hosting package with LJPc, this is already taken care of for you. This article explains what a PTR record is, how reverse DNS works, who sets it up, how it is arranged at LJPc, and how to check it yourself.
What is a PTR record?
A PTR record (pointer record) points an IP address back to a hostname. It is the mirror image of the A record, which points a hostname to an IPv4 address, and the AAAA record, which points to an IPv6 address. Because it works from address to name, it is known as reverse DNS or a reverse lookup.
In the DNS standard, it is record type 12. It is defined in RFC 1035 from 1987, the same standard that describes the A record and the rest of classic DNS. Its value is a full hostname (an FQDN) such as mail.yourdomain.com, not an IP address and not an alias.
Why a PTR record matters for email
Its primary use is email delivery. On every incoming connection, a receiving mail server checks the IP address the message comes from. If that IP address has no reverse DNS entry, or points to a generic or mismatched name, many servers treat your mail as suspicious.
Since February 2024, Gmail and Yahoo have required every sender, large or small, to have valid forward and reverse DNS: a PTR record for the sending IP address and an A or AAAA record for the name in it. If you do not meet that requirement, your mail can be rejected or end up in the spam folder. Spam filters such as SpamAssassin also count a missing PTR record, or a name that looks like a dynamic address from a home connection, as a spam signal. For your own mail server, a correct PTR record is therefore a requirement in practice. For everything else that comes with your own mail server, see how to set up and run your own mail server.
Keep in mind that a PTR record is separate from SPF, DKIM, and DMARC. Those three handle authentication of your domain, while it works at the level of the IP address. You need both: flawless SPF, DKIM, and DMARC will not make up for a missing reverse entry.
How reverse DNS works: the reverse zone
Reverse DNS uses a separate branch of DNS: the reverse zone. For IPv4 this is the in-addr.arpa domain; for IPv6 it is the ip6.arpa domain.
For IPv4, the four parts (octets) of the IP address are placed in reverse order and followed by .in-addr.arpa. The reverse entry with the hostname then lives at that name. The reversed order reads awkwardly, but it lets a network block be delegated cleanly.
For IPv6, the full address is written out as 32 separate hexadecimal digits (nibbles), placed in reverse order, and followed by .ip6.arpa. Here is an example of each:
IPv4
IP address: 192.0.2.10
Reverse name: 10.2.0.192.in-addr.arpa
PTR value: mail.yourdomain.com
IPv6
IP address: 2001:db8::1
Reverse name: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa
Who sets up the PTR record?
This is where the biggest misunderstanding lies. You cannot add a PTR record to your own domain's DNS zone the way you add an A or MX record. It does not belong to your domain but to the IP address, and the reverse zone for an IP address is managed by the owner of the IP block: your hosting or VPS provider, or in some cases your internet provider.
In practice, you request it from whoever you rent the IP address from. Some providers offer a field for this in the customer panel; others set it on request. If you have a residential or dynamic IP address from a home connection, you usually cannot set one at all, and such addresses are often blocked for outgoing email anyway.
At LJPc you manage the records of your own domain, such as A, AAAA, CNAME, and MX, yourself: in Plesk if your domain comes with a hosting package, or in the customer portal if you only have DNS management with us. Manage DNS records explains how. You do not create a PTR record there: the customer portal does not offer that record type, and a PTR record you add to your domain in Plesk does not end up in the reverse zone of the IP address.
Reverse DNS at LJPc
If you send mail through your hosting package with LJPc, reverse DNS is already taken care of. All mail you send from your mailbox or your website leaves through our outgoing mail servers, and those have a PTR record for IPv4 and IPv6 that matches in both directions. The same goes for a dedicated server with LJPc: it also sends its mail through our mail servers.
Our mail servers send mail for your domain as long as its SPF record contains include:_spf.ljpc.network. With a hosting package, that is in place by default. If you edit your SPF record, keep that part in it.
If you send mail through another service, such as Microsoft 365, Google Workspace, or a newsletter service, that service takes care of the reverse DNS of its own mail servers.
If you have a VPS or another server with LJPc that sends mail itself and you need a PTR record for it, create a support ticket. The steps below apply to such a mail server of your own, whether it runs at LJPc or elsewhere.
Setting up a PTR record, step by step
The order below prevents most mistakes. Work through the steps and only check the result afterward.
- Make sure you have a fixed (static) IP address for which you are allowed to set reverse DNS.
- Choose the hostname of your mail server, for example
mail.yourdomain.com. - Create a forward record: an A record for IPv4 or an AAAA record for IPv6, pointing that hostname to the IP address. If your domain's DNS is with LJPc, you do this in Plesk or in the customer portal, as described in Manage DNS records. In Plesk, after OK, also click Update above the list; only then does the record go into your DNS zone.
- Request the PTR record from your provider, using exactly the same hostname as its value. For a server with LJPc, you do this with a support ticket.
- Configure your mail server to identify itself with that same hostname (the HELO/EHLO name).
- Check the result with the tools later in this article.
Use one clear PTR record per IP address. Multiple entries on the same IP address are technically allowed, but they cause confusion for spam filters and log files.
Forward-confirmed reverse DNS (FCrDNS)
Mail servers check not only whether a PTR record exists, but also whether it is correct in both directions. This is called forward-confirmed reverse DNS (FCrDNS), or a full-circle check:
- The IP address has a PTR record that points to a hostname.
- That hostname has an A or AAAA record that points back to exactly the same IP address.
When both directions match, the check passes. That is why it matters that the reverse entry, the forward record, and the HELO/EHLO name of your mail server all use the same hostname. If they differ, your email risks being rejected or marked as spam.
Checking your PTR record
You can look up reverse DNS yourself with standard DNS tools. Replace the example IP with your own address.
On Linux and macOS, use dig with the -x option:
dig -x 192.0.2.10 +short
On Windows, use nslookup:
nslookup 192.0.2.10
The host command works too:
host 192.0.2.10
Then confirm that the returned hostname resolves to the same IP address with a normal forward lookup, for example dig mail.yourdomain.com +short. If both resolve to the same address, your reverse DNS is in order.
Common problems
Most complaints about reverse DNS come down to a handful of causes.
| Problem | Cause | Solution |
|---|---|---|
| No PTR record | The IP address never received reverse DNS | Request a PTR record from your hosting or VPS provider |
| PTR does not match forward | The hostname in the PTR record does not point back to the same IP address | Make sure the A or AAAA record and the PTR record point to each other (FCrDNS) |
| Generic or default name | The provider set a generic name, such as static-192-0-2-10.example.net | Request a PTR record that reflects your own domain |
| Change not visible yet | The old value is still cached | Wait until the TTL of the old value has expired. You can see it in the output of dig -x without +short: the number before IN PTR. DNS propagation explains more about TTL |
| PTR set in your own zone | You tried to place the PTR record in your own domain's DNS | That is not possible; it belongs in the reverse zone held by the IP address owner |
A correctly configured PTR record is a small step with a big effect on your email delivery. If your mail still does not arrive despite a correct PTR record, see Fix email problems. Still stuck? Create a support ticket and we will look into it with you.
Frequently asked questions
What is the difference between an A record and a PTR record?
An A record points a hostname to an IP address (forward). A PTR record does the opposite: it points an IP address back to a hostname (reverse). Together they form a complete, matching link between name and address.
Can I create a PTR record in my own DNS?
No, not in your own domain's DNS zone, so also not in Plesk or in the LJPc customer portal. A PTR record lives in the reverse zone of the IP address, which is managed by the owner of the IP block. You request it from your hosting or VPS provider.
Do I need a PTR record if I do not run my own mail server?
No. If you send mail through your hosting package or your dedicated server with LJPc, it goes through our mail servers and reverse DNS is already taken care of. Services such as Microsoft 365 and Google Workspace handle the reverse DNS of their own mail servers. You only need a PTR record yourself for your own mail server with its own IP address.
How long does it take for a PTR record to work?
That mainly depends on your provider, because they set up the record. After that, other servers see the new value once the TTL of the old value has expired. You can see that TTL in the output of dig -x without +short.
What does forward-confirmed reverse DNS mean?
It means the reverse and forward records match in both directions: the IP address points to a hostname through PTR, and that hostname points back to the same IP address through an A or AAAA record. Mail servers use this as a trust signal.
Do I also need a PTR record for IPv6?
Yes, if you send mail over IPv6. If you send from an IPv6 address without valid reverse DNS, that can lead to rejections, especially at Gmail. If your server only uses IPv4, an IPv4 PTR record is enough. The outgoing mail servers of LJPc have a matching PTR record for both.