### [PTR Records Explained: Reverse DNS for Email Deliverability [2026 Guide]](https://wpmailsmtp.com/what-is-ptr-dns-record/)

**Published:** September 2, 2021
**Author:** Rachel Adnyana

**Excerpt:** Feeling confused about PTR DNS records? Authenticating your sending domain with DNS records can help with improving email deliverability. In this post, we'll explain everything you need to know about PTR records, including whether or not you should create one and how to do so.

**Content:**

**Short version:** A PTR (pointer) DNS record maps an IP address back to a domain name — the exact reverse of an A record. If you send email from your own server or cloud instance, mailbox providers like Gmail, Yahoo, and Outlook check for a valid PTR record before they trust your messages. Most WordPress users don’t need to create one themselves — your hosting or transactional email provider handles it. But if you’re sending from a VPS or cloud instance, missing or “generic” PTR records are one of the most common reasons emails land in spam.

QuestionAnswer**What is a PTR record?**A reverse DNS record that maps an IP address to a domain name.**Why does it matter?**Gmail, Yahoo, and Outlook require a valid PTR record (and FCrDNS match) to accept email from your IP.**Do I need to create one?**Only if you control your sending IP (VPS, cloud, dedicated server). Transactional providers and shared hosts handle it for you.**How do I check mine?**Run `dig -x [your-IP]` in a terminal, or use a reverse DNS lookup tool.- [What Is a PTR Record?](#what-is-dns-ptr-record)
- [How PTR Records Work](#how-ptr-records-work)
- [PTR Record Syntax and Examples](#ptr-record-syntax-examples)
- [PTR Records and Email Deliverability — The 2026 Picture](#ptr-email-deliverability)
- [Do I Need a PTR Record? A Decision Framework](#do-i-need-dns-ptr-record)
- [How to Check Your PTR Record](#how-to-check-ptr-record)
- [How to Set Up or Fix a PTR Record](#how-to-set-up-ptr-record)
- [PTR Record Troubleshooting](#ptr-troubleshooting)
- [PTR + the Rest of Your Deliverability Stack](#ptr-deliverability-stack)
- [FAQs on PTR DNS Records](#ptr-faqs)

## What Is a PTR Record?

A PTR (pointer) record is a DNS record that maps an IP address to a domain name. It’s stored in a special part of DNS called the *reverse DNS zone* — not in the same zone where you set your A, MX, and TXT records.

PTR records exist because regular DNS works in only one direction: domain → IP. Type `example.com` into a browser and your computer asks DNS for the matching IP address. PTR records flip that around — given an IP, what domain claims it?

That answer matters for one big reason: **trust**. When your mail server connects to Gmail and announces “I’m sending email for example.com,” Gmail wants to verify the IP actually belongs to that domain. A PTR record is how it does that check.

PTR records live under two special top-level domains: `.in-addr.arpa` for IPv4 addresses and `.ip6.arpa` for IPv6 (the `.arpa` domain is reserved for internet infrastructure use). We’ll show what that looks like in a minute.

## How PTR Records Work

To understand PTR records, it helps to compare them to A records — the most common DNS record type.

### A records: domain → IP (forward lookup)

An A record points a domain to an IP. Here’s an example from a Cloudflare DNS dashboard:

![Example of an A record in Cloudflare DNS](https://wpmailsmtp.com/wp-content/uploads/2021/04/cloudflare-dns-example.png)This says: `example.com` lives at `1.1.1.1`. When someone types your domain into a browser, their computer queries DNS, finds the A record, gets the IP, and connects to your server.

### PTR records: IP → domain (reverse lookup)

A PTR record does the opposite. Given `1.1.1.1`, it answers: “this IP belongs to `mail.example.com`.”

![Forward DNS vs reverse DNS diagram showing A records mapping domains to IPs and PTR records mapping IPs to domains](https://wpmailsmtp.com/wp-content/uploads/2026/01/forward-vs-reverse-dns-diagram.png)The crucial difference is **who controls each zone**:

- **A records** live in your domain’s DNS zone, which you control through your registrar or DNS provider (Cloudflare, GoDaddy, Route 53, etc.).
- **PTR records** live in the reverse DNS zone, which is controlled by whoever owns the IP block — almost always your hosting or cloud provider, not you.

This is why most people can’t simply log in somewhere and add a PTR record themselves. To change yours, you usually need to go through your hosting provider.

## PTR Record Syntax and Examples

A PTR record has a specific format. Here’s what one looks like in zone-file syntax for the IPv4 address `192.0.2.10` pointing to `mail.example.com`:

```

10.2.0.192.in-addr.arpa.    IN    PTR    mail.example.com.
```

Notice that the IP is *reversed*: `192.0.2.10` becomes `10.2.0.192` in the record name. That reversal is intentional — it lets DNS organize reverse lookups hierarchically the same way it organizes forward lookups (from broad to specific, right to left).

For an IPv6 address like `2001:db8::1`, the PTR record lives under `.ip6.arpa`, with each hex digit reversed and dot-separated:

```

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.    IN    PTR    mail.example.com.
```

When you run a reverse DNS lookup, you’ll see the result in a simpler form — just the IP and the domain it points to:

```

192.0.2.10 → mail.example.com
```

Same information, formatted for humans.

## PTR Records and Email Deliverability — The 2026 Picture

This is where PTR records earn their keep. Without a valid one, your email is almost guaranteed to land in spam — or be rejected outright.

### The 2024 inflection point

In February 2024, Gmail and Yahoo rolled out bulk sender requirements that made email authentication non-negotiable for anyone sending more than 5,000 messages a day to their users. The checklist:

- SPF and DKIM authentication on every message
- A DMARC policy (at minimum `p=none`)
- Valid forward and reverse DNS records — that’s where PTR comes in
- One-click unsubscribe headers on bulk mail
- Spam complaint rates kept below 0.3%

Microsoft followed in May 2025 with equivalent requirements for Outlook.com, Hotmail, and Live.com. Since November 2025, Gmail moved from temporarily deferring non-compliant messages to **permanently rejecting them**.

Even if you send fewer than 5,000 emails a day, these checks are now baked into the wider deliverability system. A missing PTR record hurts sender reputation across the board.

### How Gmail uses PTR

Gmail performs a reverse DNS lookup on every incoming SMTP connection. If the sending IP doesn’t have a PTR record — or the PTR doesn’t match the domain claimed in the SMTP `HELO`/`EHLO` greeting — the message is penalized or rejected with a `421-4.7.0` or similar error.

![Gmail 'Be careful with this message' warning shown on emails that fail authentication checks](https://wpmailsmtp.com/wp-content/uploads/2021/02/be-careful-with-this-message-error.png)### How Outlook (Microsoft) uses PTR

Microsoft’s filters are notoriously aggressive about PTR. Connections from IPs without reverse DNS are routinely refused with errors explicitly mentioning the missing PTR. The Smart Network Data Services (SNDS) dashboard also requires PTR-resolvable IPs to even register your sending pool.

### How Yahoo uses PTR

Yahoo’s checks mirror Gmail’s: reverse DNS is required for IPs sending above the bulk-sender threshold, and “generic” or missing PTRs cap your sender reputation no matter how clean the rest of your authentication is.

### FCrDNS in plain English

**FCrDNS** stands for *Forward-Confirmed Reverse DNS*. It’s a two-step trust check:

1. Take the sending IP. Look up the PTR record. Note the domain you get back.
2. Take that domain. Look up its A (or AAAA) record. Does it point back to the same IP?

If both lookups agree, FCrDNS passes. If they don’t, the sending IP is treated as suspect — even if a PTR record technically exists. Think of it as the email-delivery equivalent of showing two pieces of matching ID.

### What “generic PTR” means — and why it’s a deliverability problem

When you spin up a server on AWS, Google Cloud, Azure, or DigitalOcean, the provider automatically assigns a default PTR record. It looks something like this:

```

ec2-203-0-113-25.compute-1.amazonaws.com
```

That’s a valid PTR record, technically. But mail filters treat it as a strong signal that the IP belongs to a generic cloud instance — not a dedicated mail server with a managed reputation. Generic PTRs are heavily associated with spam and abuse because every spammer who spins up a cloud VM gets one by default.

For real-world sending, you need a **custom PTR** that matches your sending domain (for example, `mail.example.com`), and your domain’s A record needs to point back to the same IP. That’s FCrDNS working as intended.

## Do I Need a PTR Record? A Decision Framework

Yes — every email sender benefits from a valid PTR. The real question is whether *you* need to create one, or whether someone else has already done it for you.

### You don’t need to create a PTR record if:

- You send email through a transactional or marketing provider — SendLayer, SendGrid, Mailgun, Brevo, Amazon SES, Postmark, SparkPost. They control the sending IPs and manage PTR records for you.
- You use Google Workspace, Microsoft 365, Zoho Mail, or similar hosted email. Same story.
- You’re on standard shared WordPress hosting and send through your host’s mail server. The host owns the IP and the PTR.

### You probably do need to create or fix a PTR record if:

- You’re running your own mail server on a VPS or cloud instance (DigitalOcean droplet, EC2, Azure VM, Linode, Vultr, etc.).
- You have a dedicated IP from an email provider and want your branded domain to resolve to it. Some providers like Amazon SES require you to request the PTR explicitly.
- Your provider’s default PTR is generic (like `ec2-...amazonaws.com`) and you want a custom one tied to your domain.

For 90% of WordPress users, the simplest move is to use [WP Mail SMTP](https://wpmailsmtp.com/pricing/) with a transactional email provider — your PTR concerns disappear because the provider handles all reverse DNS for the sending IPs.

## How to Check Your PTR Record

You can check any PTR record in under a minute with a command-line tool or a free online lookup.

### With `dig` (Linux, macOS, WSL)

The fastest way is the `dig` command with the `-x` flag, which tells `dig` to perform a reverse lookup:

```

dig -x 192.0.2.10
```

The ANSWER SECTION of the output will show you the PTR record. If you see `NXDOMAIN` or nothing returned, no PTR record exists for that IP.

### With `nslookup` (Windows, macOS, Linux)

```

nslookup 192.0.2.10
```

Same idea. It’ll print the domain name attached to that IP, or tell you the lookup failed.

### With an online tool

If you’d rather not touch a terminal, free reverse DNS lookup tools work fine. Enter the IP, hit lookup, and you’ll get the PTR back.

### How to confirm FCrDNS

Once you’ve found the PTR, run a forward lookup on the domain it returned:

```

dig A mail.example.com
```

If the IP that comes back matches the IP you started with, FCrDNS passes. If not, you’ve got a mismatch to fix (see the troubleshooting section below).

## How to Set Up or Fix a PTR Record

PTR records are set with whoever owns your IP. That’s almost always your hosting or cloud provider — not your DNS registrar. Here’s how to request or configure a PTR record with the major providers.

### Amazon Web Services (Route 53 / EC2 / SES)

For EC2 instances and Elastic IPs, AWS provides an official form to request a custom PTR. Before AWS approves the request, you’ll need to verify that you control the domain you’re pointing to — the forward A record needs to resolve to the EC2 IP first. AWS also limits PTR requests for accounts with low SES sending limits, so you may need to request a sending limit increase before they’ll process it. Full instructions live in [AWS’s reverse DNS guide](https://aws.amazon.com/premiumsupport/knowledge-center/route-53-reverse-dns/).

### Google Cloud

For Compute Engine VMs with static external IPs, you can set the PTR through the `gcloud` CLI or the console using the `--public-ptr` flag when creating or modifying the instance. As with AWS, the forward DNS must already point to the IP before Google will accept the PTR record. The official walkthrough is in the [Google Cloud documentation](https://cloud.google.com/compute/docs/instances/create-ptr-record).

### Microsoft Azure

Azure lets you set reverse DNS on a public IP resource through the Azure CLI:

```

az network public-ip update --resource-group MyResourceGroup --name MyPublicIP --reverse-fqdn mail.example.com.
```

You can also set it through PowerShell or the Azure portal. As with the other clouds, the forward DNS must already point to the IP. Note: Azure VMs also have outbound SMTP port 25 blocked by default. Email sending from Azure usually requires opening a support request to unblock it, in addition to setting the PTR.

### DigitalOcean

DigitalOcean automatically creates a PTR for any droplet whose name matches a valid, resolvable FQDN. So if you name your droplet `mail.example.com` and the domain’s A record points to that droplet’s IP, the PTR is set automatically. If the droplet name and the domain don’t match, the PTR won’t update. To change a PTR after the fact, rename the droplet to the desired FQDN.

### Linode (Akamai)

In the Linode cloud manager, open your Linode’s Network tab and find the IP you want to update. Click the three-dot menu next to the IP and choose **Edit RDNS**. Enter the FQDN — the forward DNS needs to point to that IP first, or Linode will refuse to set the PTR.

### Vultr

Vultr exposes a Reverse DNS section under each instance’s network settings. Enter your FQDN, save, and it propagates within a few minutes. As always, set the A record first.

### Cloudflare

Cloudflare doesn’t host mail servers, and it doesn’t set PTR records for your origin IPs. PTRs are still managed by whoever owns the IP — typically your hosting provider behind Cloudflare. The only exception is Cloudflare Magic Transit or BYOIP customers, who can manage PTRs through Cloudflare for IPs they bring to the platform.

### “I’m on shared hosting — what now?”

If you’re on Bluehost, SiteGround, HostGator, Kinsta, WP Engine, or any other shared or managed WordPress host:

1. **Don’t worry about creating a PTR.** Your host owns the sending IP and almost always has one set already.
2. **Use WP Mail SMTP with a transactional provider** instead of relying on the host’s mail server. PHP `mail()` from a shared IP, even with a valid PTR, has limited deliverability because the IP’s reputation is shared across thousands of other sites. Our [guide to DNS email configuration](https://wpmailsmtp.com/a-beginners-guide-to-dns-email-configuration/) walks through the setup.
3. If you’ve ruled out everything else and suspect the PTR is the issue, open a support ticket with your host and ask them to confirm the PTR record for the IP your mail is sending from. Most can verify or update it within a few hours.

## PTR Record Troubleshooting

Here are the four most common PTR problems and how to fix each one.

### 1. No PTR record at all

Reverse lookup returns `NXDOMAIN` or nothing. Email providers will reject or heavily filter your mail. **Fix:** contact your IP owner (cloud or hosting provider) and request a PTR pointing to your sending domain. Confirm with `dig -x` once it propagates.

### 2. FCrDNS mismatch

The PTR exists, but the domain it points to doesn’t resolve back to the same IP. Common causes: someone changed the A record, you updated the PTR before the forward DNS, or the PTR points to a domain you don’t fully control. **Fix:** align the records. The forward DNS (A or AAAA) for the domain in your PTR needs to resolve to the IP that PTR is set on.

### 3. Generic cloud-provider PTR

The PTR exists, but it’s something like `ec2-203-0-113-25.compute-1.amazonaws.com` or `vm-203-0-113-25.googleusercontent.com`. Technically valid, but treated with suspicion by mail filters. **Fix:** request a custom PTR matching your sending domain using the provider-specific instructions above.

### 4. Multiple PTRs on one IP

Some providers technically allow more than one PTR record per IP. Mail filters generally use only the first response and may flag inconsistencies as suspicious. **Fix:** consolidate to a single PTR per IP that matches your primary sending domain.

## PTR + the Rest of Your Deliverability Stack

PTR is one piece of a larger system. To get the most out of it, pair it with these other email authentication records:

- **SPF (Sender Policy Framework):** Tells receiving servers which IPs are allowed to send mail for your domain. See our guide on [SPF, DKIM, and DMARC](https://wpmailsmtp.com/dmarc-spf-dkim/) for setup details. If you’ve ended up with two SPF records by accident, follow [our merge guide](https://wpmailsmtp.com/fix-multiple-spf-records/).
- **DKIM (DomainKeys Identified Mail):** Cryptographically signs every email so the recipient can verify the message wasn’t altered in transit. If your DKIM key is too long for a single TXT record, our [DKIM splitting guide](https://wpmailsmtp.com/solved-how-to-split-a-dkim-record/) walks through the fix.
- **DMARC (Domain-based Message Authentication, Reporting, and Conformance):** Tells receiving servers what to do when SPF or DKIM fails — pass, quarantine, or reject. Read our [DMARC record guide](https://wpmailsmtp.com/how-to-create-dmarc-record/) for setup.
- **BIMI (Brand Indicators for Message Identification):** Displays your brand logo next to authenticated emails in supported inboxes. Requires DMARC at `p=quarantine` or `p=reject`. Our [BIMI explainer](https://wpmailsmtp.com/what-is-bimi/) covers the prerequisites.
- **Google Postmaster Tools:** Once your records are clean, Postmaster Tools gives you visibility into how Gmail rates your sender reputation, spam complaint rates, and authentication pass rates. See our [Postmaster Tools setup guide](https://wpmailsmtp.com/how-to-set-up-google-postmaster-tools/).

WP Mail SMTP includes a built-in Domain Checker that validates these records automatically every time you send a test email — so you’ll know immediately if something is broken or missing.

![WP Mail SMTP Domain Checker results showing SPF, DKIM, and DMARC validation](https://wpmailsmtp.com/wp-content/uploads/2021/08/domain-check-results-1.png)## FAQs on PTR DNS Records

### How do I find my PTR record?

Run `dig -x [your-IP]` from a terminal, or use a reverse DNS lookup tool with your sending IP. The result will show the domain name your IP currently resolves to. If no record exists, the lookup returns `NXDOMAIN`.

### What should my PTR record be?

A custom PTR matching your sending domain — for example, `mail.example.com` for an IP that sends mail on behalf of example.com. The domain in the PTR should also have a forward DNS record pointing back to the same IP. That match between forward and reverse lookups is FCrDNS, and it’s what mailbox providers expect.

### What is an example of a PTR record?

In zone-file format: `10.2.0.192.in-addr.arpa. IN PTR mail.example.com.` In a lookup result, it appears in the simpler form `192.0.2.10 → mail.example.com`. The zone-file form reverses the IP and appends `.in-addr.arpa` because reverse DNS is organized hierarchically, from most specific to least specific.

### Are PTR records still used?

Yes — more than ever. Since Gmail, Yahoo, and Microsoft tightened their bulk sender requirements between 2024 and 2025, valid PTR records are effectively mandatory for any IP that sends email. Missing or generic PTRs are now a leading cause of mail being rejected outright or routed to spam.

### What does PTR stand for?

PTR stands for *pointer*. The record “points” from an IP address to a domain name, which is the opposite direction of a standard A record.

### What’s the difference between PTR and rDNS?

rDNS (reverse DNS) is the general concept of looking up a domain from an IP. PTR is the specific DNS record type that makes rDNS work. Every rDNS lookup is a PTR lookup under the hood.

### Who manages PTR records?

The owner of the IP address — usually your hosting or cloud provider. Domain registrars don’t typically manage PTR records because reverse DNS authority follows the IP block, not the domain.

### How long do PTR record changes take to propagate?

Most PTR changes propagate within minutes to a few hours, depending on the TTL set by the IP owner. Worst case is 24 to 48 hours. If you’ve requested a change through your provider and the old PTR is still showing after that, contact support.

### Can I have multiple PTR records for one IP?

Technically yes, but it’s a bad idea. Most mail filters only use the first response and may flag IPs with multiple PTRs as inconsistent or suspicious. Stick to one PTR per IP that matches your primary sending domain.

### Do I need a PTR record for IPv6?

If you send mail over IPv6, yes — the requirement is the same as for IPv4. The record lives under `.ip6.arpa` instead of `.in-addr.arpa`, and the hex digits of the address are reversed and dot-separated.

### What’s a generic PTR record?

A default PTR assigned by a cloud provider that looks like `ec2-203-0-113-25.compute-1.amazonaws.com` or similar. It’s a valid record, but it signals to receiving mail servers that the IP is a generic cloud instance rather than a managed mail server. Generic PTRs significantly hurt deliverability and should be replaced with a custom PTR matching your sending domain.

### Does Cloudflare set PTR records?

For most Cloudflare users, no. Cloudflare proxies your web traffic but doesn’t own the IPs your mail sends from. PTR records remain managed by your mail server’s hosting provider. The exception is Cloudflare Magic Transit or BYOIP customers, who can manage PTRs through Cloudflare for IPs they bring to the platform.

### Will Gmail reject my email without a PTR record?

For higher-volume senders, yes — Gmail returns errors like `421-4.7.0` for connections from IPs without valid reverse DNS. Lower-volume senders may not see outright rejections, but their messages are far more likely to land in spam.

### Do PTR records affect SEO?

No. PTR records affect email deliverability, not search rankings. Confusion sometimes arises because Google’s web crawlers perform reverse lookups in some contexts, but those checks don’t influence search ranking signals.

### Can a PTR record point to multiple domains?

A single PTR record points to a single domain name. If your IP sends mail for multiple domains, the PTR should point to your primary sending or HELO domain. The other domains’ authentication is handled separately through SPF, DKIM, and DMARC alignment.

## Next: Check Your Other Deliverability Records

PTR is one piece of email deliverability. Once you’ve confirmed yours is set correctly, the next step is making sure SPF, DKIM, and DMARC are all in place too. Our [complete guide to SPF, DKIM, and DMARC](https://wpmailsmtp.com/dmarc-spf-dkim/) walks through setting up all three.

If you’d rather not handle DNS records yourself, WP Mail SMTP’s Elite plan includes full White Glove Setup — we install the plugin, connect it to your provider, and configure your authentication records for you. See the [WP Mail SMTP pricing page](https://wpmailsmtp.com/pricing/) for details.

[Fix Your WordPress Emails Now](https://wpmailsmtp.com/pricing/)

If this article helped you out, please follow us on [Facebook](https://facebook.com/wpmailsmtp) and [Twitter](https://twitter.com/wpmailsmtp) for more WordPress tips and tutorials.

**Categories:** Marketing

**Tags:** DNS, PTR record

---