Reverse DNS
DNSReverse DNS is a DNS lookup method that maps an IP address back to a hostname using PTR records in special reverse-mapping zones. It is commonly used to verify the identity of mail servers, support logging and troubleshooting, and improve trust signals for network services. Reverse DNS does not control where a domain points; it provides a name associated with an IP.
How It Works
Reverse DNS (rDNS) performs the opposite of a typical A or AAAA record lookup. Instead of resolving a hostname to an IP address, it queries a PTR (pointer) record to find the hostname associated with a given IP. For IPv4, the IP is reversed and appended to the in-addr.arpa zone (for example, 203.0.113.10 becomes 10.113.0.203.in-addr.arpa). For IPv6, the address is expanded, reversed by nibble, and queried under ip6.arpa.
PTR records are typically managed by the organization that controls the IP address block, which is often your hosting provider or upstream network. Many hosts let you set rDNS for dedicated IPs in a control panel or by support request. A common best practice is forward-confirmed reverse DNS (FCrDNS): the PTR points to a hostname, and that hostname resolves back to the same IP via A/AAAA records, creating a consistent identity for services like SMTP.
Why It Matters for Web Hosting
Reverse DNS is most important when your hosting plan sends email or runs services that other networks validate. Mail receivers often check for a valid PTR record and may treat missing or mismatched rDNS as a spam signal, affecting deliverability. When comparing hosting plans, consider whether you get a dedicated IP, whether rDNS is configurable, and how quickly changes propagate, especially for transactional email, server monitoring, and incident troubleshooting.
Common Use Cases
- Improving SMTP reputation signals and email deliverability for outbound mail servers
- Supporting forward-confirmed reverse DNS checks used by some security and anti-abuse systems
- Making server logs and network diagnostics easier by showing hostnames instead of raw IPs
- Identifying services behind dedicated IP addresses (web, API, VPN, or monitoring endpoints)
- Assisting incident response by correlating IP activity with expected hostnames
Reverse DNS vs Forward DNS
Forward DNS uses A/AAAA records to map a hostname to an IP so browsers and clients can reach your site or service. Reverse DNS uses PTR records to map an IP back to a hostname and is mainly used for validation, reputation, and diagnostics. Forward DNS is controlled in your domain DNS zone, while reverse DNS is usually controlled by the IP owner (often the host), so changing rDNS may require provider access even if you manage your domain DNS.