Nameserver

Why It Matters

The single most confusing DNS failure is editing records in a perfectly good control panel that nothing is delegated to. The records save, the interface confirms, and no resolver on earth ever reads them, because the delegation points somewhere else entirely. Nameserver changes are also the one DNS operation where the folk wisdom about long waits holds up: the delegation records at the top-level domain often carry TTLs of a day or two, so resolvers that already knew the old set will keep asking it for that long. Anyone planning a move should treat it as a scheduled change, not an afternoon experiment.

How It Works

Registrar, registry, resolver, zone — in that order. You set the nameservers at the registrar, the registry publishes them as the delegation for your name, and any resolver working down from the root is referred to them. If the nameservers are themselves inside the domain they serve, the registry also publishes glue records holding their addresses, otherwise the lookup would be circular. Each server in the set should carry an identical copy of the zone, usually with one primary and the rest transferring from it and comparing the zone serial number. Because resolvers cache the referral as well as the answers, a change of operator is the slowest thing in DNS to take effect.

Real-World Example

Common Mistakes

• ✕Switching nameservers before copying the existing zone across — MX and TXT records stay behind with the old operator and mail stops within the hour
• ✕Editing the zone at the registrar while a third-party provider holds the delegation — nothing you save is ever served
• ✕Listing a single nameserver — one maintenance window at the operator becomes a total outage for your name

Related Terms