Infrastructure & ZoneRFC 1035
PTR Record — PTR Record (Pointer / Reverse DNS)
Resolves an IP address back to its canonical domain name (Reverse DNS / rDNS lookup).
RECORD TYPE
PTR
STANDARD RFC
RFC 1035
DEFAULT TTL
3600 seconds (1 hour)
CATEGORY
Infrastructure & Zone
BIND Zone File Syntax Example
4.3.2.1.in-addr.arpa. 3600 IN PTR mail.example.com.How to Query & Check PTR Records
Linux / Mac (dig)
dig +short -x 192.0.2.1Windows / Generic (nslookup)
nslookup 192.0.2.1PowerShell (Resolve-DnsName)
Resolve-DnsName -Name 192.0.2.1 -Type PTRRecommended Best Practices
PTR records must be requested through your IP provider or hosting company (AWS, DigitalOcean, Hetzner, Linode), not your domain registrar.
Primary Use Cases:
- •Configuring Forward-Confirmed Reverse DNS (FCrDNS) for outbound SMTP mail servers
- •Network diagnostics, traceroute hostname resolution, and server authentication
Common Configuration Mistake
Attempting to create a PTR record in Cloudflare or GoDaddy for a domain; PTR records belong to the owner of the IP block.
Always verify records using authoritative queries (`dig @1.1.1.1 $PTR example.com`) to bypass local ISP caching when debugging propagation delays.
Frequently Asked Questions
DNS PTR Record Questions & Answers
Common questions regarding DNS propagation, TTL settings, and zone file syntax.
PTR (Pointer) records perform the exact inverse of an A record. PTR records are configured within special reverse lookup zones (`in-addr.arpa` for IPv4 and `ip6.arpa` for IPv6). Mail servers strictly verify PTR records (FCrDNS) to combat spam.