Skip to content
AdminKit

Authoritative nameserver

What is Authoritative nameserver?

An authoritative nameserver holds a DNS zone's actual source-of-truth records and is the server a recursive resolver ultimately queries for an answer it doesn't already have cached. AdminKit's whois tool looks up which nameservers a domain's registrar has on file, so you can confirm they match what you intentionally configured.

By AdminKit team, Netbase JSC · Updated

An authoritative nameserver is the server that holds the actual source-of-truth records for a DNS zone and is designated, via NS records at both the registrar and the zone itself, to answer queries about that domain directly — as opposed to a recursive resolver, which only caches and forwards answers it looked up elsewhere. When a recursive resolver doesn’t have a cached answer, it eventually queries one of the domain’s authoritative nameservers to get the current, canonical record. Changing DNS providers means updating which servers are authoritative for a domain at the registrar, and until every resolver’s cached copy of the old NS records expires, some queries may still reach the old servers. Confirming which nameservers are actually authoritative for a domain, and that they match what was intentionally configured, is a basic check against DNS hijacking or an unnoticed registrar change. Microsoft’s Azure DNS tutorial on hosting a domain walks through that delegation step: the registrar stores the domain’s NS records in the parent zone (.com, for a .com domain), which is what directs resolvers to the servers hosting the zone. The delegation chain that leads a resolver to the right authoritative server is defined in RFC 1035; at the top of that chain sit the root servers, as listed in IANA’s root server registry.

When a zone’s own authoritative nameserver has a name inside that same zone (ns1.example.com for example.com), the parent also has to publish a glue record so resolvers can find it without a circular lookup.

Authoritative nameserver is part of AdminKit’s DNS cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

What's the difference between an authoritative nameserver and a recursive resolver?

An authoritative nameserver holds a DNS zone's actual source-of-truth records and is designated to answer queries about that domain directly, while a recursive resolver only caches and forwards answers it looked up elsewhere.

When does a recursive resolver actually contact an authoritative nameserver?

Only when it doesn't already have a cached answer -- at that point it eventually queries one of the domain's authoritative nameservers to get the current, canonical record.

What happens when I change DNS providers?

You update which servers are authoritative for the domain at the registrar, and until every resolver's cached copy of the old NS records expires, some queries may still reach the old servers.

Why does it matter to confirm which nameservers are authoritative for my domain?

Confirming they match what was intentionally configured is a basic check against DNS hijacking or an unnoticed registrar change.