Reverse DNS Misconfiguration: Fixing PTR Issues

Introduction

Reverse DNS misconfiguration is a common email deliverability problem for VPS, dedicated servers and self-hosted mail. The sending IP should have a PTR record that points to a proper mail hostname, and that hostname should resolve forward to the same IP.

When PTR is missing, generic or mismatched, receiving servers may treat the mail as less trustworthy. This rarely blocks every message by itself, but it can contribute to deferrals, spam folder placement or rejection — especially alongside weak SPF, DKIM or blacklist issues.

Quick answer

Reverse DNS misconfiguration explained

Normal DNS maps a hostname to an IP. Reverse DNS does the opposite: IP to hostname via a PTR record.

Forward DNS:
mail.example.com → 192.0.2.10

Reverse DNS (PTR):
192.0.2.10 → mail.example.com

Common PTR problems:

• No PTR record on the sending IP
• Generic provider hostname instead of your mail identity
• PTR hostname does not resolve forward to the same IP
• Website IP checked instead of actual mail IP
• HELO/EHLO hostname does not match mail identity
• Provider refuses custom PTR on shared hosting
• Old PTR left after server migration or IP change
• Multiple domains sending from one IP with no neutral hostname
• PTR changed but forward A record not updated
• Self-signed or misconfigured mail server using localhost HELO

Why this matters

PTR fixes are especially important for VPS mail, dedicated servers, transactional SMTP and any environment where you control or influence the sending IP.

How to check reverse DNS

Always check reverse DNS for the IP that actually sends mail, not just the website IP.

1. Sending IP — Find the outbound SMTP IP from headers, logs or provider dashboard.
2. PTR record — Confirm the IP has a reverse DNS hostname.
3. Forward DNS — Confirm the PTR hostname resolves back to the same IP.
4. HELO/EHLO — Check whether the mail server announces a consistent hostname.
5. SPF — Confirm the sending IP or provider is authorized.
6. Blacklist status — Check whether the IP is listed on reputation databases.
7. Shared vs dedicated IP — Confirm whether custom PTR is even possible on your plan.
8. Provider rDNS panel — Check whether the host lets you set PTR directly or by ticket.

Common problems

How to fix reverse DNS

1. Step 1: Find the sending IP

   Use email headers, SMTP logs, bounce messages or your provider dashboard.

2. Step 2: Choose a mail hostname

   Pick a hostname such as mail.example.com or smtp.example.com.

3. Step 3: Create forward DNS

   Add an A record so the hostname points to the sending IP.

4. Step 4: Request PTR from the provider

   Open a ticket or use the provider panel to set rDNS for the IP.

5. Step 5: Align HELO/EHLO settings

   Configure the mail server to announce the same or a consistent hostname.

6. Step 6: Verify forward-confirmed rDNS

   Confirm IP → hostname and hostname → IP both resolve correctly.

7. Step 7: Check SPF and blacklist status

   Ensure the sending IP is authorized and not listed.

8. Step 8: Send test mail and review headers

   Confirm improved delivery and check authentication results on test messages.

PTR request examples

Subject: Request custom reverse DNS (PTR) for mail server IP

Hello Support,

Please set reverse DNS (PTR) for the following IP address:

IP address:
192.0.2.10

Requested PTR hostname:
mail.example.com

Forward DNS already configured:
mail.example.com A 192.0.2.10

Purpose:
Outbound SMTP mail server for example.com

Please confirm once the PTR record is active.

Thank you.

---

Good forward-confirmed rDNS:

dig -x 192.0.2.10
→ mail.example.com

dig mail.example.com A
→ 192.0.2.10

Bad setup:

dig -x 192.0.2.10
→ ip-10-0-0-1.provider.net

mail.example.com → different IP or no record

Frequently asked questions