PTR Record and Reverse DNS for Email Server
DOMAIN

What Is a PTR Record?

A PTR Record (Pointer Record) is a type of DNS record that works in the opposite direction of an A Record. Instead of mapping a domain name to an IP address (Forward DNS), a PTR Record maps an IP address back to a domain name. This process is called Reverse DNS or rDNS.

For example, if your server has the IP address 203.0.113.50 and you configure a PTR Record pointing to mail.yourdomain.com, anyone performing a Reverse DNS Lookup on that IP will receive mail.yourdomain.com as the answer.

PTR Records are stored in a special DNS zone called in-addr.arpa for IPv4 (and ip6.arpa for IPv6). The IP address is reversed before being placed in this zone — for example, 203.0.113.50 becomes 50.113.0.203.in-addr.arpa.

Why Email Servers Need PTR Records

For email servers, having a correct PTR Record is a critical baseline requirement. Most receiving mail servers check Reverse DNS before accepting or filtering incoming emails. The main reasons are:

Golden rule: Your mail server's PTR Record must match the hostname declared in the SMTP EHLO/HELO command, and that hostname must resolve back to the same IP via its A Record. All three must be consistent — otherwise your emails risk being rejected or landing in spam.

Forward DNS vs Reverse DNS

To clarify the difference between the two processes:

Forward DNS (A Record)

Reverse DNS (PTR Record)

How to Configure a PTR Record

An important point: PTR Records are not configured in your domain's DNS panel like A Records or MX Records. They must be set at your IP address provider (your ISP or hosting provider) directly, because the in-addr.arpa zone is controlled by the owner of the IP block.

For VPS or Dedicated Servers

  1. Log in to your VPS/server provider's control panel.
  2. Find the "Reverse DNS", "PTR Record", or "rDNS" section.
  3. Enter the IP address you want to configure.
  4. Enter the hostname you want the IP to point to, e.g. mail.yourdomain.com.
  5. Save the setting and wait 24–48 hours for DNS propagation.

For Shared Hosting

On shared hosting, you typically cannot set PTR Records yourself because the IP address is shared among multiple customers. Your options are:

How to Check a PTR Record

You can verify your PTR Record in several ways:

Via Command Line (Linux/macOS)

Via Online Tools

Visit MXToolbox (mxtoolbox.com), choose "Reverse Lookup," and enter your IP address. The tool will display the current PTR Record along with any warnings.

PTR Records with IPv6: What You Need to Know

As IPv6 adoption grows, configuring PTR Records for IPv6 addresses is slightly more complex than for IPv4. An IPv6 address is 128 bits long, represented as 32 hexadecimal characters. Before it is placed in the ip6.arpa zone, every character must be reversed and separated by dots. For example:

IPv6:     2001:0db8:85a3:0000:0000:8a2e:0370:7334
ip6.arpa: 4.3.3.7.0.7.3.0.e.2.a.8.0.0.0.0.0.0.0.0.3.a.5.8.8.b.d.0.1.0.0.2.ip6.arpa

Many modern mail servers check Reverse DNS for both IPv4 and IPv6. If your server sends email over IPv6, setting a PTR Record for the IPv6 address is equally important. Request it from your IP provider in the same way as for IPv4.

Reading PTR Record Lookup Output

Understanding what a successful and a missing PTR Record looks like in practice helps you diagnose deliverability issues quickly.

Output from dig -x (PTR configured correctly)

$ dig -x 203.0.113.50

; <<>> DiG 9.16.1 <<>> -x 203.0.113.50
;; ANSWER SECTION:
50.113.0.203.in-addr.arpa. 3600 IN PTR mail.yourdomain.com.

;; Query time: 45 msec
;; SERVER: 8.8.8.8#53

Output from host (quick check)

$ host 203.0.113.50
50.113.0.203.in-addr.arpa domain name pointer mail.yourdomain.com.

If no PTR Record is set, the response will be NXDOMAIN or Host not found: 3(NXDOMAIN). This signals that the IP has no Reverse DNS configured and outgoing email from that server faces a high risk of rejection or spam classification by receiving mail servers.

Common PTR Record Problems and How to Fix Them

In practice, several PTR-related issues cause email deliverability problems. Here are the most common ones and how to resolve them:

Problem Cause Fix
PTR does not match EHLO Mail server hostname differs from PTR value Update the EHLO hostname in your mail server config to match PTR
PTR does not match A Record Forward DNS points to a different IP Check A record for the hostname and align it with the actual IP
Slow propagation Original TTL was set high Wait for old TTL to expire, or reduce TTL in advance before changing
Cannot set PTR yourself Shared hosting with a shared IP Request dedicated IP or use an SMTP relay with PTR already configured

PTR Records and Other Email Authentication Standards

A PTR Record is just one piece of a complete email authentication setup. It should be combined with:

Frequently Asked Questions

Will emails go to spam if I don't have a PTR Record?

There is a high probability that emails will be rejected or placed in the spam folder, especially when sending to Gmail, Outlook, and Yahoo, which perform strict Reverse DNS checks. Some mail servers may refuse the connection entirely without even accepting the email.

Does the PTR Record have to match the root domain?

Not necessarily — it just needs to be a hostname that has an A Record pointing back to the same IP. For example, mail.yourdomain.com or smtp.yourdomain.com both work. The key is that Forward and Reverse DNS are consistent — a property known as FCrDNS (Forward-Confirmed Reverse DNS).

How long does PTR Record propagation take?

Like any DNS record, PTR Records have a TTL. In general, global propagation takes 24–48 hours, though it can be faster if the zone TTL is set low.

Register a Domain with AsiaGB

Starting from ฿350/year (.com) or ฿250/year (.co.th) with free DNS Management — manage PTR Records and full DNS configuration easily.

View Domain Pricing →