A PTR record, or Pointer record, is a type of DNS record used for reverse DNS lookup. It maps an IP address back to a domain name, allowing receiving systems to verify the identity of a sending server. While standard DNS queries resolve a domain to an IP address, PTR records perform the opposite function by resolving an IP address to a hostname.
PTR records are primarily used in email delivery and server verification. When a mail server receives a message, it often performs a reverse DNS check on the sending IP. If the PTR record exists and aligns with the sending domain, the message is more likely to be trusted. If it is missing or misconfigured, the email may be flagged as suspicious, rejected, or routed to spam.
These records are typically controlled by the owner of the IP address block, such as a hosting provider or infrastructure operator. Proper PTR configuration is essential for maintaining sender reputation and ensuring consistent email deliverability.
Advanced
PTR records are configured within reverse DNS zones, which are structured differently from standard forward DNS zones. IPv4 reverse DNS uses the in-addr.arpa domain, where the IP address is reversed and appended to this namespace. For example, an IP like 192.0.2.1 would map to 1.2.0.192.in-addr.arpa.
A critical requirement in email systems is forward-confirmed reverse DNS, where the PTR record resolves to a hostname that also resolves back to the same IP via an A record. This bidirectional validation strengthens trust signals used by receiving mail servers and spam filters.
In large scale environments, PTR records must be aligned with outbound mail servers, relays, and dedicated IP pools. Mismatches between PTR hostnames and HELO or EHLO identifiers can negatively impact deliverability. Proper coordination between DNS, mail server configuration, and IP allocation is required to maintain consistency.
Relevance
- Validates the identity of sending mail servers
- Improves email deliverability and sender reputation
- Supports spam filtering and anti abuse systems
- Required by many receiving servers for trusted communication
Applications
- Configuring reverse DNS for outbound mail servers
- Aligning PTR records with SMTP HELO or EHLO hostnames
- Managing dedicated IP addresses for transactional or marketing email
- Supporting compliance with email authentication best practices
Metrics
- Reverse DNS pass rates in email logs
- Email deliverability and inbox placement rates
- Spam filtering outcomes related to rDNS checks
- Bounce or rejection rates due to missing PTR records
Issues
- Missing PTR records leading to rejected or filtered emails
- Mismatch between PTR hostname and sending domain
- Lack of forward-confirmed reverse DNS reducing trust
- Dependency on hosting providers for configuration changes
Example
A hosting provider assigns a dedicated IP address for outbound email. A PTR record is configured to map the IP to mail.example.com. The domain mail.example.com also resolves back to the same IP address. This alignment ensures receiving mail servers recognise the sender as legitimate, improving inbox placement and reducing spam filtering.