Skip to content
WebsiteHosting.com

concept Domains & DNS

Authoritative nameserver

Learn how authoritative nameservers answer for DNS zones and why registrar delegation must point to the zone you edit.

Sources checked · P0014

What it means

An authoritative nameserver holds or serves DNS data for one or more zones and responds for those zones from its authoritative data, rather than merely repeating an answer cached from another server. A zone is an administratively managed portion of the DNS name tree. Multiple authoritative servers can serve the same zone for availability. Authority is about the zone served, not whether the operator is the domain registrar, website host or another organization. Zones and authority DNS terms

A parent zone publishes a delegation, typically NS records pointing to the child's nameservers. The child zone also contains its own authoritative information, including SOA and NS records at its apex. Editing a DNS dashboard that is not actually delegated may save a record locally yet have no effect on the public lookup path. Delegation

Try it

Example — spot the important boundary. These are invented record displays, not live DNS or instructions to change a registrar.

; Parent delegation for example.com (schematic)
example.com.        IN NS    ns1.example.net.
example.com.        IN NS    ns2.example.net.

; Data served by the example.com zone (schematic)
example.com.        IN SOA   ns1.example.net. hostmaster.example.com. (...)
example.com.        IN NS    ns1.example.net.
www.example.com.    IN A     192.0.2.40

The parent delegation determines which authoritative servers recursive resolvers discover for the child. The www A record belongs to the zone data served there. 192.0.2.40 is a reserved documentation address, not a real website destination. NS hostnames are labels, not address records themselves; a resolver may need address lookups or glue to reach them. The text (...) is a placeholder for SOA fields, not executable zone-file syntax. NS/SOA formats DNS delegation

Zone versus domain versus provider

A domain name can contain many descendant labels and even delegated child zones. Changing www.example.com in the parent example.com zone is different from editing an independent shop.example.com child zone if shop has been delegated. The authoritative answer may originate from whichever zone actually covers the record's owner name.

ItemQuestion it answers
Domain registrationWho manages the registered name?
Parent NS delegationWhich servers are designated for this child zone?
Authoritative zoneWhich DNS records will its nameservers answer for?
Recursive cacheWhich answers might users still receive temporarily?

An NS record inside an unrelated DNS panel is not a substitute for correctly configuring the parent delegation. An NS target is meant to name a server with address records, not a CNAME alias. NS target rule

In practice

When verifying a proposed record change, identify the current delegated NS set and inspect each authoritative server for the exact owner name and RR type. Check that the authoritative servers agree on expected records and are reachable. A changed entry in a control panel alone is not a verification result. If parent and child NS data are inconsistent, investigate delegation separately from an ordinary A/AAAA edit; broad nameserver replacements can affect the whole domain, including email.

For the lookup path see DNS resolution; for a read-only decision tree when changes do not appear see DNS change not visible. Connecting a domain covers the wider hosting task.

Sources & model boundaries

Primary references used for this explanation. The example above is illustrative; it is not a live check.

  1. RFC 1034 — Domain Names: Concepts and Facilities

    Sections 2.4, 3.1, 4.3.2 and 5. DNS tree, zones, referrals, resolvers and caching.

    Checked .

  2. RFC 1035 — Domain Names: Implementation and Specification

    Sections 3.2, 3.3 and 4. RR formats, TTL, A, NS, SOA, CNAME and MX records.

    Checked .

  3. RFC 9499 — DNS Terminology

    Sections 2–7. Terminology for authoritative servers, recursion, caching, and delegation.

    Checked .

  4. RFC 2181 — Clarifications to the DNS Specification

    Sections 5 and 10. RRsets, CNAME coexistence, and MX/NS alias restrictions.

    Checked .