Why Reverse DNS is Important for VPS Mail Servers

Introduction

Reverse DNS, also called rDNS, maps an IP address back to a hostname. For normal website hosting, reverse DNS is not usually critical. For mail servers, it matters much more because receiving mail systems often check whether the sending IP has a valid and reasonable reverse DNS record.

If a VPS sends email without proper reverse DNS, messages may be delayed, rejected or placed in spam. Reverse DNS does not guarantee inbox delivery, but it is one of the basic identity checks expected for serious mail servers.

Quick answer

Reverse DNS

Reverse DNS is the opposite of normal DNS.

For email, the reverse DNS record is usually called a PTR record. The PTR record is managed by the IP address owner or hosting provider, not usually by the domain DNS zone.

Why mail servers check reverse DNS

Receiving mail servers use reverse DNS as part of sender identity and reputation checks.

They may check:

• whether the sending IP has a PTR record
• whether the PTR hostname looks valid
• whether the hostname resolves back to the same IP
• whether the hostname matches the mail server identity
• whether the IP is listed on blacklists
• whether SPF, DKIM and DMARC pass
• whether the sending pattern looks trustworthy

PTR record explained

A PTR record is the DNS record used for reverse DNS.

IP address:
192.0.2.10

PTR record:
mail.example.com

Forward DNS:
mail.example.com A 192.0.2.10

Good reverse DNS examples

Sending IP:
192.0.2.10

PTR:
192.0.2.10 → mail.example.com

Forward DNS:
mail.example.com → 192.0.2.10

Mail server hostname:
mail.example.com

HELO/EHLO:
mail.example.com

Result:
The sending IP has a clear and consistent mail server identity.

PTR:
192.0.2.10 → server1.hostingprovider.com

Forward DNS:
server1.hostingprovider.com → 192.0.2.10

Result:
May be acceptable if mail authentication and reputation are also good.

Bad reverse DNS examples

Missing PTR:

Sending IP:
192.0.2.10

PTR:
No reverse DNS record

Problem:
Some receivers may reject or distrust the mail.

Generic PTR:

PTR:
192-0-2-10.provider.local

Problem:
Looks like a generic or internal hostname.

Mismatch:

PTR:
192.0.2.10 → mail.example.com

Forward DNS:
mail.example.com → 198.51.100.20

Problem:
PTR hostname does not resolve back to the sending IP.

Wrong identity:

PTR:
192.0.2.10 → web.example.com

HELO:
mail.otherdomain.com

Problem:
Mail identity is inconsistent.

Reverse DNS vs SPF, DKIM and DMARC

Reverse DNS is only one part of email deliverability.

HELO/EHLO hostname

When a mail server connects to another mail server, it announces itself using HELO or EHLO.

A clean mail setup usually has:

• mail server hostname
• PTR record
• forward A record
• HELO/EHLO name

Hostname: mail.example.com
PTR: IP → mail.example.com
A record: mail.example.com → IP
HELO/EHLO: mail.example.com

Who controls reverse DNS?

Reverse DNS is controlled by the owner of the IP address block.

This is usually:

• VPS provider
• hosting provider
• data center
• cloud provider
• ISP
• IP transit/provider
• dedicated server provider

Why this matters

Reverse DNS is not a magic inbox guarantee. It is a baseline technical requirement that should be combined with authentication, clean sending practices and good IP reputation.

How to check reverse DNS for a VPS mail server

Use Reverse DNS Checker and DNS Lookup to verify both reverse and forward DNS.

1. Sending IP — Identify the exact IP used for outbound mail.
2. PTR record — Check whether the IP has reverse DNS.
3. PTR hostname — Confirm the hostname is valid and professional.
4. Forward DNS — Check whether the PTR hostname resolves back to the same IP.
5. Mail hostname — Confirm the server hostname matches your intended mail identity.
6. HELO/EHLO — Check mail server greeting if you manage the mail server.
7. SPF/DKIM/DMARC — Verify mail authentication records.
8. Blacklists — Check whether the sending IP is listed.

Common problems

How to set reverse DNS correctly

1. Step 1: Identify the sending IP

   Find the IP address your mail server uses for outbound email.

2. Step 2: Choose a mail hostname

   Use a real hostname such as mail.example.com or server1.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 update

   Set reverse DNS in the VPS provider panel or ask support to update the PTR record.

5. Step 5: Align mail hostname

   Configure the mail server hostname and HELO/EHLO to use the chosen name where possible.

6. Step 6: Check SPF, DKIM and DMARC

   Publish authentication records for the sending domain.

7. Step 7: Verify with tools

   Use Reverse DNS Checker, DNS Lookup and mail tests.

8. Step 8: Monitor delivery

   Watch bounces, spam placement, blacklists and mail logs.

Example request to hosting provider

Hello,

Please set reverse DNS / PTR for the following IP:

IP address:
192.0.2.10

Requested PTR:
mail.example.com

Forward DNS is already configured:
mail.example.com → 192.0.2.10

This IP is used for outbound mail, and we need the PTR record to match the mail server hostname.

Thank you.

Self-hosted mail warning

Running email on a VPS is more complex than hosting a website.

You need:

• clean IP reputation
• reverse DNS
• SPF
• DKIM
• DMARC
• TLS
• spam filtering
• abuse protection
• bounce handling
• queue monitoring
• secure authentication
• proper rate limits

Useful reverse DNS checks

Check reverse DNS:
dig -x 192.0.2.10

Check forward DNS:
dig mail.example.com A

Check MX:
dig example.com MX

Check SPF:
dig example.com TXT

Check DMARC:
dig _dmarc.example.com TXT

Check server hostname:
hostname -f

Check mail banner manually:
openssl s_client -connect mail.example.com:25 -starttls smtp

Frequently asked questions