DNS Lookup

🔎

dns

Input

Target: a domain name or an IPv4 / IPv6 address.
A hostname like example.com runs a forward lookup (A + AAAA).
An IP like 1.1.1.1 or 2606:4700::1 automatically runs a reverse (PTR) lookup.

Options

Custom DNS Server (optional): DNS IP, hostname, or DoH URL. If empty, the system resolver is used. The same resolver is used whether the lookup is forward or reverse.

Output

For a hostname: resolved A and AAAA addresses.
For an IP: the PTR record (typically a hostname like one.one.one.one).
The header line tells you which mode ran (“DNS lookup for …” vs. “Reverse DNS lookup for …”).
Resolver source (system or custom).

Tips

Use a custom resolver to compare public DNS providers.
If results differ, it can indicate caching or resolver policy differences.
Reverse lookups query the special in-addr.arpa (IPv4) or ip6.arpa (IPv6) zones — many IPs simply have no PTR record set, which is reported as “No DNS records resolved”.

Deeplink

# Forward lookup
netdebug://dns?target=example.com&server=1.1.1.1

# Reverse lookup (PTR) — same slug, IP as the target
netdebug://dns?target=1.1.1.1

Tip: in the app, open the Export menu (the share icon) on this screen and choose Copy Deeplink to copy this link as a Universal Link with your current target and options already filled in.