Reverse DNS Lookup
Look up the PTR record for any IP address. Verify reverse DNS configuration and check FCrDNS for email delivery.
PTR Records and Why Reverse DNS Still Matters
Reverse DNS answers the opposite question to a normal lookup: given an IP address, what hostname does its owner want it known by? The mechanism is a PTR record stored in a special part of the DNS tree — for IPv4 the octets are reversed and appended to in-addr.arpa, so 8.8.8.8 becomes 8.8.8.8.in-addr.arpa, and for IPv6 each hex nibble is reversed under ip6.arpa. Querying that name returns the PTR answer, which for 8.8.8.8 is dns.google.
The reason most people meet reverse DNS is email. Receiving mail servers apply Forward-Confirmed reverse DNS (FCrDNS): the sending IP must have a PTR record, and the hostname in that PTR must resolve back to the same IP. Gmail's sender guidelines require valid PTR records for sending IPs, and Outlook.com and countless corporate gateways reject or spam-folder mail that fails the check, because the ability to pass FCrDNS proves someone administratively controls both the address and the name — something botnets on residential connections cannot fake.
A frequent point of confusion is who can change a PTR. It is not your domain registrar: the in-addr.arpa and ip6.arpa zones are delegated along the IP allocation chain, so only the holder of the address block — your ISP, hosting provider, or cloud platform — can publish PTR records for it. Cloud providers expose this as self-service (a public PTR setting in GCP, an rDNS request in AWS, naming your droplet after its FQDN in DigitalOcean), while traditional ISPs often handle it through support tickets.
Key Reverse DNS Concepts
PTR recordThe DNS record type behind reverse DNS. 8.8.8.8 is looked up as 8.8.8.8.in-addr.arpa, and the PTR answer is the hostname dns.google.
FCrDNS matchThe PTR resolves to a hostname, and that hostname resolves back to the same IP. This round-trip check is what most mail providers apply to sending IPs.
Generic vs custom rDNSProvider defaults like 1-2-3-4.static.isp.example look automated and score poorly with spam filters; a custom mail.yourdomain.com signals a managed server.
Setting PTR in the cloudAWS: request rDNS for your Elastic IP. GCP: set a public PTR on the VM network interface. DigitalOcean: name the droplet the exact FQDN you want.
dig -xThe command-line shortcut for reverse lookups: dig -x 8.8.8.8 builds the in-addr.arpa name for you and returns the PTR record with its TTL.
Mismatch problemsA PTR pointing at a hostname that does not resolve back fails FCrDNS — mail rejections, SSH login delays, and noisy application logs are the usual symptoms.