DNS Trace Debugger
Trace DNS resolution step-by-step from Root → TLD → Authoritative nameservers, similar to dig +trace.
About DNS Trace
DNS resolution is hierarchical. When you query a domain, the resolver starts from the root (.) zone, then delegates to the TLD nameservers, and finally reaches the authoritative nameservers for your domain.
- Root (.) 13 root nameserver clusters manage the top-level delegation
- Delegation Each zone hands off to the next level via NS records
- Answer Final records returned from the authoritative nameserver
About DNS Trace Debugger – dig +trace Tool Online
Trace DNS resolution step-by-step from Root → TLD → Authoritative nameservers, similar to dig +trace. Choose your DNS resolver: Cloudflare, Google, Quad9.
Follow DNS resolution from root servers through TLD and authoritative nameservers to reveal delegation and final-answer problems.
Key features
- Diagnostic scope Follow DNS resolution from root servers through TLD and authoritative nameservers to reveal delegation and final-answer problems.
- Target input Enter a fully qualified domain name and select the DNS record type and starting resolver options shown by the tool.
- Checks to review Inspect each root, parent, delegation, glue, authoritative, CNAME, and final-answer step rather than only the last record.
- Diagnostic result The trace provides a chronological resolution path that helps isolate lame delegation, missing glue, timeout, and inconsistent authoritative data.
How to use DNS Trace Debugger – dig +trace Tool Online
Follow this workflow to work with DNS delegation path safely and accurately.
- Enter the target Enter a fully qualified domain name and select the DNS record type and starting resolver options shown by the tool.
- Select the diagnostic scope Inspect each root, parent, delegation, glue, authoritative, CNAME, and final-answer step rather than only the last record.
- Run the network check Run the DNS delegation path diagnostic and retain status, timing, returned values, and the observation point needed to reproduce it.
- Correlate the result The trace provides a chronological resolution path that helps isolate lame delegation, missing glue, timeout, and inconsistent authoritative data.
Usage tips
- Start with NS or SOA when diagnosing delegation, then trace the affected application record.
- Compare all authoritative nameservers; one stale server can produce intermittent failures.
- Check UDP/TCP reachability and EDNS behavior when a step times out or returns a truncated response.