DNS Trace
Follow a name through the full resolution chain, from the root servers down to the authoritative nameserver, showing every delegation step and how long each took.
An ordinary lookup returns one answer from whichever cache replied first. A trace shows the whole journey — which is the only way to see where resolution is slow or breaking rather than simply that it is.
How resolution actually works
Nothing knows the answer up front. A resolver starts at the root servers, which do not know your domain but do know who is authoritative for its top-level domain. That server does not know your domain either, but knows which nameservers were delegated the zone. Those finally hold the record.
Each of those steps is a query to a different server, and each can be slow, misconfigured or unreachable independently. A trace makes the responsible step visible.
What the timings tell you
- A slow root or TLD step — rare, and almost never your problem. These are heavily anycast and normally answer in milliseconds.
- A slow authoritative step — the domain's own nameservers are overloaded, distant, or the operator is having trouble. This is the common case when one specific domain resolves slowly while everything else is fine.
- A step that times out and retries — usually a nameserver still listed in the delegation that no longer serves the zone. Very common after a DNS provider migration where the old records were never removed, and it adds seconds to every uncached lookup.
- Nameservers disagreeing — the zone was updated on some servers and not others. This produces "it works, just not always", and it stays invisible unless you query each nameserver individually rather than trusting whichever answered first.
Delegation problems a trace exposes
The most frequent is a mismatch between the NS records at the registrar and those in the zone itself. Both exist, both are authoritative-sounding, and when they disagree resolvers behave inconsistently depending on which they consulted.
The second is a nameserver that answers but is not authoritative for the zone — usually a leftover from a migration. Resolvers will try it, get an unhelpful answer, and fall back, which costs time on every lookup that misses cache.
When to reach for this instead of a plain lookup
Use the DNS lookup when you want to know what a name currently resolves to. Use a trace when the answer is right but arriving slowly, when a change has not taken effect and you need to know which layer is still stale, or when a domain resolves for some people and not others.