Query a specific nameserver

Ask one nameserver directly — an authoritative server for the zone, or a public resolver like 8.8.8.8 — and see exactly what it returns, bypassing every cache in between. This is the dig @server a sysadmin reaches for, run from our server.

Verbose outputiAsks that one server directly — bypassing caches — like dig @server.

When you'd use this

The propagation checker shows what public resolvers around the world are handing out. This is the opposite view: it goes straight to a server you name and asks it. That's how you confirm an authoritative nameserver already serves a change (before waiting for propagation), compare what two nameservers in a set return, or check whether a specific resolver still has a stale record cached.

Authoritative vs non-authoritative

If the server you query is authoritative for the zone, the answer is marked authoritative (dig's aa flag) — it's the source of truth, not a cached copy. A public resolver like 8.8.8.8 answers non-authoritatively from its cache. To watch a change roll out across many resolvers instead, use propagation on the homepage, or trace the delegation on propagation.studio.