DNS tool

PTR Record Lookup - Reverse DNS Checker

Run a PTR record lookup for an IPv4 address, IPv6 address or reverse DNS name and compare answers across global resolvers.

Record type

What this check shows

A PTR record maps an IP address back to a hostname through the reverse DNS hierarchy. It is commonly checked for mail servers, logging and infrastructure diagnostics.

Enter an IP address such as 8.8.8.8, an IPv6 address or a reverse lookup name such as an in-addr.arpa or ip6.arpa FQDN to compare the hostname returned by different resolvers.

When to use it

  • Mail server reverse DNS checks
  • Validating server identity
  • Investigating log attribution
  • Confirming provider-managed PTR changes

How to read the result

  • PTR records are normally controlled by the owner of the IP address, not by the domain's regular DNS provider.
  • Forward-confirmed reverse DNS requires the PTR hostname to resolve back to the original IP address.
  • Missing PTR records can affect mail reputation but do not normally prevent basic IP connectivity.

Command examples

Use these dig commands when you need to compare DNSRadar with a terminal check or collect evidence for a DNS provider.

Terminal
dig -x 8.8.8.8 +short
dig @1.1.1.1 -x 8.8.8.8
dig 8.8.8.8.in-addr.arpa PTR +short

Troubleshooting focus

Use this page to check reverse DNS for a server IP, mail server, log source or abuse investigation. PTR lookups are different from A and AAAA checks because the reverse zone is usually controlled by the owner of the IP range, not by the domain's ordinary DNS provider.

Practical examples

  • Check a mail server IP before sending production mail from a new provider.
  • Compare PTR responses after asking a hosting provider to update reverse DNS.
  • Verify forward-confirmed reverse DNS by checking whether the PTR hostname resolves back to the same IP.
  • Use the resolver IP and location columns to see whether one cache still has an old PTR answer.

Common mistakes

Editing PTR in the normal DNS zone

PTR records live under in-addr.arpa or ip6.arpa and are normally managed by the IP owner.

Assuming a PTR fixes email alone

PTR helps reputation, but SPF, DKIM, DMARC, rDNS consistency and sending behavior also matter.

Using a generic provider hostname

A clear hostname such as mail.example.com is easier to understand in logs and mail checks.

Checking only IPv4

IPv6 sending addresses need their own reverse DNS.

Questions

Can I configure PTR in my normal DNS zone?

Usually not. The hosting or network provider that owns the IP range must configure reverse DNS.

What should I enter for IPv4?

You can enter the IP address directly. DNSRadar converts 1.2.3.4 to 4.3.2.1.in-addr.arpa before running the PTR lookup.

Related DNS tools