Skip to content
LookupOwl

DNS trace

Follow a lookup from the root servers down to the answer, one referral at a time, and see why a change is not live yet.

A domain or any name under it.

Record type to resolve (mode trace only).

IPv6 only shows whether the path works for people with no IPv4.

More options

Real resolvers often ask each server only for the part it needs.

Results for *.review-lab.github.com

Checked live lookup238 ms

JSONCheck again

DNS trace

review-lab.github.com has no A record.

The name exists, but not for this type. dns1.p08.nsone.net answered after 3 steps. Resolvers remember that for 3,600 seconds.

Type A · 3 steps · 57 ms · Times are from LookupOwl's server

From the root, 3 steps

  1. Step 1 · rootm.root-servers.netReferral to com14 ms

    202.12.27.33 · 13 name servers, kept for 2 days

    13 servers could answer this step. We asked 1.

    a.root-servers.net, b.root-servers.net, c.root-servers.net, d.root-servers.net, e.root-servers.net, f.root-servers.net, g.root-servers.net, h.root-servers.net, i.root-servers.net, j.root-servers.net, k.root-servers.net, l.root-servers.net, m.root-servers.net (asked)

    • DS present
    • Glue for 26 addresses
  2. Step 2 · comb.gtld-servers.netReferral to github.com38 ms

    192.33.14.30 · 8 name servers, kept for 2 days

    13 servers could answer this step. We asked 1.

    i.gtld-servers.net, d.gtld-servers.net, h.gtld-servers.net, l.gtld-servers.net, j.gtld-servers.net, c.gtld-servers.net, f.gtld-servers.net, e.gtld-servers.net, b.gtld-servers.net (asked), a.gtld-servers.net, m.gtld-servers.net, g.gtld-servers.net, k.gtld-servers.net

    • No DS
    • Glue for 2 addresses
  3. Step 3 · github.comdns1.p08.nsone.netNo record of this type5 ms

    198.51.44.8

    Answer
    No record of this type
    Remembered for
    3,600 s (the SOA's negative TTL)
  • Copy traceText in dig +trace layout, for a ticket.
  • See what resolvers say nowDNS propagation for review-lab.github.com, type A.Propagation
  • See every record for the nameDNS lookup of review-lab.github.com.DNS lookup
Structured result (JSON) · 3.8 KB
{
  "name": "review-lab.github.com",
  "mode": "trace",
  "type": "A",
  "family": "any",
  "qmin": false,
  "trace": {
    "hops": [
      {
        "n": 1,
        "zone": ".",
        "server": {
          "host": "m.root-servers.net",
          "ip": "202.12.27.33",
          "family": 4
        },
        "serversAvailable": 13,
        "ms": 14,
        "kind": "referral",
        "authoritative": false,
        "referral": {
          "zone": "com",
          "ns": [
            "i.gtld-servers.net",
            "d.gtld-servers.net",
            "h.gtld-servers.net",
            "l.gtld-servers.net",
            "j.gtld-servers.net",
            "c.gtld-servers.net",
            "f.gtld-servers.net",
            "e.gtld-servers.net",
            "b.gtld-servers.net",
            "a.gtld-servers.net",
            "m.gtld-servers.net",
            "g.gtld-servers.net",
            "k.gtld-servers.net"
          ],
          "ttl": 172800,
          "count": 13,
          "glue": 26,
          "ds": true
        }
      },
      {
        "n": 2,
        "zone": "com",
        "server": {
          "host": "b.gtld-servers.net",
          "ip": "192.33.14.30",
          "family": 4
        },
        "serversAvailable": 13,
        "ms": 38,
        "kind": "referral",
        "authoritative": false,
        "referral": {
          "zone": "github.com",
          "ns": [
            "ns-520.awsdns-01.net",
            "ns-421.awsdns-52.com",
            "ns-1707.awsdns-21.co.uk",
            "ns-1283.awsdns-32.org",
            "dns1.p08.nsone.net",
            "dns2.p08.nsone.net",
            "dns3.p08.nsone.net",
            "dns4.p08.nsone.net"
          ],
          "ttl": 172800,
          "count": 8,
          "glue": 2,
          "ds": false
        }
      },
      {
        "n": 3,
        "zone": "github.com",
        "server": {
          "host": "dns1.p08.nsone.net",
          "ip": "198.51.44.8",
          "family": 4
        },
        "serversAvailable": 3,
        "ms": 5,
        "kind": "nodata",
        "authoritative": true,
        "negativeTtl": 3600
      }
    ],
    "followed": [],
    "totalMs": 57,
    "steps": 3,
    "cachedHops": 0,
    "final": {
      "rcode": "NOERROR",
      "authoritative": true
    },
    "flags": [
      {
        "hop": null,
        "kind": "none"
      }
    ],
    "text": "; <<>> LookupOwl trace <<>> review-lab.github.com A\n; Times are from LookupOwl's server, not from you.\n\ncom.\t172800\tIN\tNS\ti.gtld-servers.net.\ncom.\t172800\tIN\tNS\td.gtld-servers.net.\ncom.\t172800\tIN\tNS\th.gtld-servers.net.\ncom.\t172800\tIN\tNS\tl.gtld-servers.net.\ncom.\t172800\tIN\tNS\tj.gtld-servers.net.\ncom.\t172800\tIN\tNS\tc.gtld-servers.net.\ncom.\t172800\tIN\tNS\tf.gtld-servers.net.\ncom.\t172800\tIN\tNS\te.gtld-servers.net.\ncom.\t172800\tIN\tNS\tb.gtld-servers.net.\ncom.\t172800\tIN\tNS\ta.gtld-servers.net.\ncom.\t172800\tIN\tNS\tm.gtld-servers.net.\ncom.\t172800\tIN\tNS\tg.gtld-servers.net.\ncom.\t172800\tIN\tNS\tk.gtld-servers.net.\n;; Received from 202.12.27.33#53(m.root-servers.net) in 14 ms\n\ngithub.com.\t172800\tIN\tNS\tns-520.awsdns-01.net.\ngithub.com.\t172800\tIN\tNS\tns-421.awsdns-52.com.\ngithub.com.\t172800\tIN\tNS\tns-1707.awsdns-21.co.uk.\ngithub.com.\t172800\tIN\tNS\tns-1283.awsdns-32.org.\ngithub.com.\t172800\tIN\tNS\tdns1.p08.nsone.net.\ngithub.com.\t172800\tIN\tNS\tdns2.p08.nsone.net.\ngithub.com.\t172800\tIN\tNS\tdns3.p08.nsone.net.\ngithub.com.\t172800\tIN\tNS\tdns4.p08.nsone.net.\n;; Received from 192.33.14.30#53(b.gtld-servers.net) in 38 ms\n\n;; review-lab.github.com. has no A record (NODATA)\n;; Received from 198.51.44.8#53(dns1.p08.nsone.net) in 5 ms\n\n;; Total 57 ms",
    "varies": {
      "servers": 2,
      "differing": 0
    }
  },
  "summary": "review-lab.github.com has no A record according to dns1.p08.nsone.net, after 3 steps (57 ms)."
}

Next step

How a DNS trace works

No server knows every domain. Instead the system is a chain of pointers. A resolver with nothing in its memory asks one of the 13 root server addresses, which does not know your domain but knows who runs the top-level domain, such as com. That server does not know your domain either, but it knows which name servers your domain is delegated to. Those name servers finally give the answer. Each pointer is called a referral.

This page does the same walk, from our server, and shows every step: the server asked, its address, how long it took, what it sent back and for how long that may be kept. It is the same thing dig +trace prints, laid out so you can read it without knowing the output format.

  1. Enter a nameA domain or any name under it, such as www.example.com. Record type A is the default; open More options for MX, TXT, NS, CAA and others.
  2. Read the pathThe first steps are referrals. The last step is the answer, marked authoritative when it comes from a server that holds the zone.
  3. Check the timing and the TTLThe bars share one scale, so the slowest step is the longest. The time to live on the last step tells you how long other resolvers may keep the answer.

What each step tells you

  • Referral to a zone. The server does not hold the answer but names the servers that do. The line under it says how many name servers it listed, whether it sent glue (their addresses, so the trace can continue) and how long a resolver may keep the referral.
  • DS present or No DS. A referral carries a DS record when the child zone is signed with DNSSEC. This page does not validate anything. Use the DNSSEC check to see whether the chain of trust holds.
  • Answer, authoritative. The records you asked for, from a server that holds the zone itself, with the TTL of each.
  • Alias (CNAME). The name points to another name. The target is traced as its own block, up to four aliases deep.
  • No record of this type, or Name does not exist. The name is real but has no record of the type you asked for, or it does not exist at all. The SOA record sets how long a resolver remembers that no.

The first two steps are referrals for the root and the top-level domain. They change rarely, so they are kept for about two days. Your own resolver almost never repeats them, which is why the page says so under the path.

Why a change is not live yet

After you change a record, the servers that hold the zone have the new value at once. Everyone else is holding a copy that stays valid until its TTL runs out. The TTL of the answer on the last step is therefore the number that decides how long a change takes to reach people: at 300 seconds, within about five minutes. At 86400 seconds, up to a day.

What you seeWhat it usually meansWhat to do
The trace shows the new valueThe zone is updated. Other resolvers are waiting for their copy to expire.Wait for the TTL, or check DNS propagation to see who has caught up.
The trace shows the old valueThe change is not published at the servers that hold the zone.Check the DNS provider. Waiting will not help.
Two traces give different answersThe name is load balanced, or the servers of the zone disagree.The page notes it. The delegation check shows whether the servers are in sync.

When the trace shows a problem

A trace is also the quickest way to find where a lookup breaks. A server that refuses to answer for its zone, one that never answers, a slow step and a delegation that loops are each marked on the step where they happen, and the answer at the top says what that means.

  • A server refuses or is not authoritative. It is listed for the domain but does not hold it. The trace carries on with another server, and the delegation checker lists every server with its result.
  • No answer in time. We wait about two seconds for each server, then ask the next. One silent server is common. If every server of a zone is silent, the trace stops there and says so.
  • A loop. Two zones send the lookup back and forth. The trace stops and names the fix: correct the name server list at one of the registrars.
  • IPv6 only. Choose IPv6 only in More options to see whether the path works for someone with no IPv4 at all. If our own server cannot reach IPv6 at that moment, the page says it could not test, which is on our side.

Options and limits

QNAME minimisation hides the full name from the servers high up in the chain. With it on, the root server is asked only for com, the top-level server only for example.com, and only the last step sees the whole name. Many resolvers do this today, and each step of the trace shows the name that was really sent.

Only public names are traced, and only public server addresses are asked. A trace asks about ten servers and takes a few seconds. The same trace is available to AI assistants as the dns_trace tool through the LookupOwl MCP server, with the text version of the path in the result.

Questions people ask

Why trace instead of a normal lookup?

A normal lookup asks a resolver, which may answer from its memory. A trace asks the servers that hold the data, one referral at a time. It shows which servers answered, in what order, and where a lookup breaks, which a plain lookup cannot.

Is this the same as dig +trace?

It follows the same path from the root servers. The trace is run from our server, so times and the first answer you see may differ from running it at home. The result includes a text version in dig +trace layout that you can copy into a ticket.

What does QNAME minimisation do?

It sends each server only the part of the name it needs, as many real resolvers do. The root server hears about com, not about your full name. It is off by default; when it is on, each step shows the name that was sent.

Why do the first two steps say they are usually skipped?

The referrals from the root and from the top-level domain stay valid for about two days. A resolver that has seen any name in that top-level domain recently already has them, so it starts further down. We always ask from the top so that you can see the whole path.

Does the trace check DNSSEC?

No. It only shows whether each referral carries a DS record, which means the next zone is signed. To check that the signatures and keys hold up, use the DNSSEC check.

Why did two traces of the same name give different answers?

Some names are load balanced on purpose: the servers give a different set of addresses each time. The page notes it when it sees that. If the servers of a zone disagree about a record that should be the same everywhere, the delegation check shows it.

Use it from AI, the API or the command line

Every LookupOwl tool is also a free API and an MCP tool, with no key and no account. This one is dns_trace. Please be kind to the rate limits.

curl
curl "https://lookupowl.com/api/v1/tools/dns-trace?q=lookupowl.com"
MCP
claude mcp add --transport http lookupowl https://lookupowl.com/mcp