About this tool
Reverse DNS Lookup (rDNS, governed by RFC 1035 and RFC 3596) resolves known IPv4 or IPv6 network addresses back into their associated authoritative domain hostnames via PTR (Pointer) records. Whereas forward DNS maps hostnames to IP addresses, rDNS operates in the opposite direction. rDNS serves as a mandatory security filter for anti-spam mail server authentication, cyber incident attribution, and CDN trace analysis. This tool delivers client-side DoH reverse DNS querying and in-addr.arpa lookup locally.
How to Use This Tool (Step-by-Step)
Enter Target IP Address
Type your target IPv4 address (e.g., `8.8.8.8`) or IPv6 address into the lookup field.
Construct .arpa Inversion Domain
The engine reverses address octets and appends the root zone (`8.8.8.8.in-addr.arpa`) to dispatch a standardized PTR query.
Inspect PTR Hostname & Verification
Review the resolved PTR hostname (`dns.google`), remaining TTL cache duration, and Forward-Confirmed rDNS status.
Full IPv4 & IPv6 Dual-Stack Support
Supports traditional IPv4 byte reversals alongside complex 128-bit IPv6 nibble-by-nibble `ip6.arpa` pointer expansions.
Forward-Confirmed rDNS (FCrDNS)
Automatically verifies Forward-Confirmed rDNS by cross-checking forward A-records against original IPs to detect spoofing.
Encrypted DoH Security
Queries execute over encrypted DNS-over-HTTPS (DoH) upstream connections, eliminating local ISP cache pollution.
rDNS Email Deliverability & Server Admin Tips
- •Mandatory for SMTP email servers: Gmail and Outlook reject incoming mail lacking valid PTR records. File hosting tickets to configure rDNS.
- •Private IPs cannot be resolved on public DNS: RFC 1918 private ranges (`192.168.x.x`) yield NXDOMAIN on public nameservers.
- •PTR records are controlled by IP providers, not domain registrars: You configure PTR at your VPS hosting dashboard, not GoDaddy.
Code & Transformation Examples
IPv4 to in-addr.arpa Domain Construction Benchmark
8.8.8.8 (Google 著名公共 DNS)• 逆序查询域名 : 8.8.8.8.in-addr.arpa
• 权威解析主机名 : dns.google
• 正向校验核对 : dns.google 解析为 8.8.8.8 (双向确认 FCrDNS 完美闭环通过!)* IP octets invert from right to left (`1.2.3.4` becomes `4.3.2.1.in-addr.arpa`) to mirror DNS tree hierarchies.
Terminal Reverse DNS Commands Cheat Sheet
# 使用 -x 参数直接进行反向解析
dig -x 8.8.8.8 +short
# 输出: dns.google.nslookup -type=ptr 8.8.8.8
# 输出: Name: dns.google* Trailing periods on hostnames denote the definitive absolute DNS root zone in BIND outputs.
Frequently Asked Questions
Q: Why must IP octets be reversed in in-addr.arpa?
A: DNS hierarchy progresses from specific to generic (right to left). IP addresses are generic to specific (left to right). Inverting aligns the hierarchies.
Q: What is Forward-Confirmed rDNS (FCrDNS)?
A: FCrDNS proves identity: Resolving an IP yields hostname H; resolving H must yield the original IP. Prevents attackers from forging arbitrary PTR strings.
Q: How long does it take for PTR changes to propagate globally?
A: Upstream regional internet registries (ARIN, APNIC) assign conservative TTLs. PTR propagation typically requires 12–24 hours worldwide.