What Are Nameservers? How They Work

A nameserver is a server that answers DNS queries — it holds the actual records (A, MX, TXT...) for a domain and hands them out when asked. Every domain points to a set of nameservers at the registrar, and those servers are the domain's source of truth.

The DNS hierarchy.root.com.org.plexample.comNSexample.orgNS
The root delegates every top-level domain, and each top-level domain delegates the nameservers for a domain.

Two Different Meanings of "Nameserver"

The word gets used for two different roles, which confuses people:

  • Authoritative nameserver — holds the actual zone data for a domain (usually run by your DNS provider — Cloudflare, Route 53, your registrar). It's the final answer for that domain.
  • Recursive resolver — the server your device or ISP queries (e.g. 8.8.8.8, 1.1.1.1). It doesn't hold your records — it looks them up by asking authoritative nameservers on your behalf and caches the result.

How Delegation Works

When you register a domain, the registrar tells the TLD's nameservers (e.g. the .com zone) which nameservers are authoritative for your domain. This is the NS record — it points from the parent zone down to your provider:

example.com.   NS   ns1.provider.com.
example.com.   NS   ns2.provider.com.

Why Every Domain Has Multiple Nameservers

DNS requires at least two nameservers for redundancy (RFC 1035). If one is unreachable, resolvers try the next. Most providers give you 2–4:

  • Redundancy — one server going down does not take your domain offline
  • Geographic distribution — servers in different regions reduce latency
  • Load distribution — query volume is spread across servers

Changing Nameservers

Changing your domain's nameservers moves DNS management to a different provider entirely — a bigger operation than editing a single record:

  1. Set up all your DNS records (A, MX, TXT, etc.) at the new provider first
  2. Verify the records resolve correctly by querying the new nameservers directly
  3. Update the nameservers at your domain registrar's control panel
  4. Wait for propagation — this can take up to 48 hours since NS records typically have long TTLs
  5. Once propagated, retire the old provider

Common Nameserver Setups

ProviderExample Nameservers
Cloudflareada.ns.cloudflare.com, bob.ns.cloudflare.com
AWS Route 53ns-1.awsdns-00.com, ns-2.awsdns-00.co.uk
GoDaddyns1.domaincontrol.com, ns2.domaincontrol.com

Verify Your Nameservers

Check which nameservers a domain is actually using and confirm they are answering correctly:

Try it on your domain

See the theory in practice — run a NS Lookup for your own domain.