Why is a PTR record required for mail servers?

Major email providers (Gmail, Outlook, Yahoo) reject incoming emails if the sending server's IP address lacks a matching reverse DNS PTR record (FCrDNS).

Where do I configure a PTR record?

PTR records are configured in your server hosting provider's management console (DigitalOcean, AWS, Linode, Hetzner), not in your domain registrar's DNS panel.

How do I perform a reverse DNS lookup?

Use our online Reverse IP Lookup tool or run 'dig -x 192.0.2.1' from your terminal.

Home/DNS Lookup/PTR Record

SOA CAA

DNS Resource Record Type

PTR Record: Pointer Record (Reverse DNS)

Resolves an IP address in reverse to a canonical domain hostname (rDNS).

Record Type

PTR

Query Protocol

DNS Port 53

Standard / RFC

RFC 1035, Section 3.5

Recommended TTL

3600 seconds

Query Live PTR Records

Query any domain name to inspect authoritative PTR records, response latency, and TTL values.

Loading DNS lookup tool...

BIND Zone File Syntax

Standard BIND representation of this record in authoritative master zone files:

1.2.0.192.in-addr.arpa. 3600 IN PTR mail.example.com.

Recommended TTL: 3600 seconds (1 hour) to 86400 seconds (24 hours).

Common Configuration Pitfalls

Attempting to configure PTR records in domain DNS zone managers instead of through the VPS or IP provider's control panel.
Mismatched forward (A record) and reverse (PTR record) names, causing email delivery to fail Forward-Confirmed Reverse DNS (FCrDNS) checks.

How the PTR Record Operates in DNS Resolution

The PTR (Pointer) record maps an IP address back to its associated fully qualified domain name (FQDN). Unlike standard forward DNS (domain -> IP), PTR records are managed under the .in-addr.arpa (IPv4) or .ip6.arpa (IPv6) zones by the hosting ISP or cloud infrastructure provider. Valid rDNS is mandatory for sending email.