Skip to content
SiteShiftCo

Nameservers

The DNS servers responsible for answering authoritative queries about a domain's records, controlling where the domain points for web, email, and other services.

Also known as: DNS nameservers, authoritative nameservers, name servers

Nameservers are the DNS servers responsible for answering authoritative queries about a domain’s records. When the world’s DNS resolvers want to know what IP address example.com points to, they ultimately ask the domain’s nameservers, which return the configured answer.

A domain’s nameservers control where the domain points for every service tied to it: web hosting, email, subdomains, third-party integrations, and more. Whoever controls the nameservers controls the domain’s effective destination.

How nameservers fit into DNS

A simplified DNS resolution path:

  1. Browser asks a recursive resolver: “What is the IP for example.com?”
  2. The resolver asks the root nameservers, which point to .com TLD nameservers
  3. The TLD nameservers point to example.com’s authoritative nameservers
  4. The authoritative nameservers return the requested record (e.g., the A record’s IP)
  5. The resolver returns the answer to the browser

The “authoritative nameservers” in step 4 are what people mean when they say “the domain’s nameservers.”

Where nameservers are set

Nameservers are configured at the domain registrar, the company where the domain is registered. The registrar tells the TLD registry which nameservers are authoritative for the domain.

Changing nameservers at the registrar moves DNS management to a different provider. After the change propagates, all DNS queries for the domain go to the new nameservers.

Common nameserver scenarios

Default registrar nameservers

When a domain is registered, it typically uses the registrar’s own nameservers by default. DNS records are managed in the registrar’s web interface.

Examples:

  • dns1.registrar-servers.com, dns2.registrar-servers.com (Namecheap)
  • ns1.dnsimple.com, ns2.dnsimple.com (DNSimple)
  • ns1.cloudflare.com, ns2.cloudflare.com (Cloudflare)

Third-party DNS provider

Many users move DNS management to a dedicated DNS provider for better performance, features, or integration:

  • Cloudflare, free DNS with fast global anycast network
  • AWS Route 53, tightly integrated with AWS services
  • Google Cloud DNS, integrated with Google Cloud
  • NS1, enterprise DNS with traffic management
  • Azure DNS, Microsoft’s DNS service
  • DNS Made Easy, paid DNS focused on performance

To use a third-party DNS provider, the user changes the nameservers at the registrar to point to the provider’s nameservers. DNS records are then managed at the provider, not the registrar.

Hosting provider nameservers

Some hosting providers offer their own nameservers, simplifying setup. The user changes the registrar’s nameservers to point at the host. Common with managed WordPress hosting and some platform hosting (e.g., HostGator, Bluehost).

Why use a third-party DNS provider

  • Performance. Some providers have faster, more globally distributed networks than typical registrar DNS
  • Features. Advanced records, traffic management, geo-routing, DNSSEC
  • Reliability. Enterprise DNS providers often have stronger SLAs
  • Integration. Aligns DNS with cloud services in the same ecosystem
  • Security. DDoS protection, DNSSEC, advanced filtering
  • Free CDN and security. Cloudflare bundles DNS with CDN and DDoS mitigation at no cost

Nameserver requirements

Most domains require at least two nameservers for redundancy:

  • ICANN policies typically require a minimum of two nameservers per domain
  • The two nameservers should be on different networks for true redundancy
  • Most DNS providers automatically supply multiple nameserver hostnames

A typical domain has 2–4 nameservers configured.

Changing nameservers

The process to change nameservers:

  1. Identify the new DNS provider’s nameserver hostnames (e.g., ns1.cloudflare.com, ns2.cloudflare.com)
  2. Replicate any existing DNS records at the new provider before switching (to avoid downtime)
  3. Log into the registrar’s account and update the nameserver fields for the domain
  4. Save the changes
  5. Wait for propagation, typically 24–48 hours, often faster

During propagation, some resolvers will use the old nameservers and others the new. If the records on both providers are identical, this causes no disruption.

DNS propagation timing

Nameserver changes take longer to propagate than individual record changes because TLD-level caches (which point to the nameservers themselves) typically have longer TTLs. Plan for up to 48 hours, though most users see the change within hours.

Common misconceptions

  • “Nameservers and DNS records are the same.” Nameservers are servers; DNS records are individual entries (A, MX, CNAME, etc.) hosted on those nameservers.
  • “Changing nameservers loses your DNS records.” The records do not transfer automatically; they need to be added at the new provider before switching to avoid downtime.
  • “You need to change nameservers to change a single DNS record.” Individual records can be changed at the existing provider without touching nameservers.
  • “More nameservers always mean better reliability.” After 2–4 nameservers, additional ones rarely improve reliability and can increase configuration complexity.