What Are Nameservers? Complete Guide for MSPs

Q: What's the difference between changing nameservers and changing DNS records?

- Changing nameservers: Moves DNS control to a different provider - Changing DNS records: Modifies individual records at your current provider Nameserver changes propagate slower because NS records are cached at the TLD level.

What Are Nameservers?

Nameservers are specialized DNS servers that store DNS records for domains and respond to DNS queries. When you type a domain name into your browser, nameservers are what tell the internet where to find that website’s IP address.

The Basics

Nameservers are servers that host DNS records for a domain
They answer DNS queries from recursive resolvers
Every domain must have at least two nameservers (for redundancy)
Nameservers are configured at the domain registrar
They define which DNS provider controls your DNS records

Example Nameservers

; Cloudflare nameservers
example.com.    NS    ada.ns.cloudflare.com.
example.com.    NS    bob.ns.cloudflare.com.

; AWS Route 53 nameservers
example.com.    NS    ns-123.awsdns-45.com.
example.com.    NS    ns-456.awsdns-78.net.
example.com.    NS    ns-789.awsdns-01.org.
example.com.    NS    ns-012.awsdns-23.co.uk.

; GoDaddy nameservers
example.com.    NS    ns1.domaincontrol.com.
example.com.    NS    ns2.domaincontrol.com.

Why Nameservers Matter

Your nameservers determine:

Where your DNS records are stored — Which DNS provider has your records
Where DNS queries go — Who answers questions about your domain
Your DNS management interface — Where you make DNS changes
DNS performance and reliability — Your nameserver provider’s infrastructure

How Nameservers Work

The DNS Resolution Chain

When someone visits your website:

User types example.com in browser
Browser asks recursive resolver: “What’s the IP for example.com?”
Resolver asks root servers: “Who handles .com?”
Root says: “Ask the .com TLD servers”
Resolver asks .com TLD: “Who handles example.com?”
TLD says: “Ask ada.ns.cloudflare.com” (your nameservers)
Resolver asks YOUR NAMESERVER: “What’s the A record for example.com?”
Your nameserver responds: “192.0.2.1”
Browser connects to 192.0.2.1

The Delegation Hierarchy

DNS is hierarchical, with nameservers at each level:

Level	Operated By	Purpose
Root Nameservers (.)	ICANN and partners	Direct queries to TLD servers
TLD Nameservers (.com, .net, .org)	Registry operators (Verisign, etc.)	Direct queries to domain nameservers
Domain Nameservers (example.com)	Your DNS provider	Answer queries for your specific domain
Your DNS Records	You	A, CNAME, MX, TXT, etc.

NS Records in the Zone

Your domain’s nameservers are stored as NS records in the parent zone:

; In the .com zone (at Verisign)
example.com.    172800    IN    NS    ada.ns.cloudflare.com.
example.com.    172800    IN    NS    bob.ns.cloudflare.com.

; Glue records (if nameservers are under the same domain)
ada.ns.cloudflare.com.    172800    IN    A    173.245.59.102
bob.ns.cloudflare.com.    172800    IN    A    173.245.58.102

Types of Nameservers

Authoritative Nameservers

The “official” source of DNS records for a domain:

Store your actual DNS records (A, CNAME, MX, TXT, etc.)
Respond to queries from recursive resolvers
You configure these at your registrar
Examples: Cloudflare, Route 53, GoDaddy DNS

Recursive Resolvers

Servers that find answers by querying authoritative servers:

Used by end users (configured in OS or router)
Cache responses to speed up future queries
Query authoritative servers on behalf of users
Examples: 8.8.8.8 (Google), 1.1.1.1 (Cloudflare), ISP resolvers

Root Nameservers

The top of the DNS hierarchy:

13 root server addresses (a.root-servers.net through m.root-servers.net)
Actually hundreds of servers (anycast)
Direct queries to TLD servers (.com, .net, .org)
Operated by various organizations (ICANN, Verisign, NASA, etc.)

TLD Nameservers

Handle specific top-level domains:

.com, .net — Operated by Verisign
.org — Operated by PIR (Public Interest Registry)
Country codes (.uk, .de, .au) — Various national registries
Direct queries to your domain’s nameservers

Registrar vs DNS Provider

Key Distinction

Registrar	DNS Provider
Where you buy/renew your domain	Where your DNS records live
Manages domain ownership	Manages DNS configuration
Sets nameserver delegation	Hosts authoritative nameservers
Examples: GoDaddy, Namecheap, Porkbun	Examples: Cloudflare, Route 53, GoDaddy

Same Company vs Different

Same company (common for simple setups):


Registrar	GoDaddy
DNS Provider	GoDaddy
Nameservers	ns1.domaincontrol.com, ns2.domaincontrol.com

Different companies (common for MSPs):


Registrar	Namecheap (where you bought the domain)
DNS Provider	Cloudflare (where you manage DNS)
Nameservers	ada.ns.cloudflare.com, bob.ns.cloudflare.com

Why Separate Them?

MSPs often use different registrars and DNS providers:

Better DNS features — Cloudflare has better DNS than most registrars
Consolidation — Manage all DNS in one place regardless of registrar
Client diversity — Clients have domains at various registrars
Security — Separate DNS control from domain ownership
Cost — Best registrar price vs best DNS features

Changing Nameservers

When to Change Nameservers

Moving to a new DNS provider (e.g., from GoDaddy DNS to Cloudflare)
Consolidating DNS management (bringing all clients to one provider)
Setting up CDN/proxy services (Cloudflare requires using their nameservers)
Improving DNS reliability (moving to more robust infrastructure)

Pre-Change Checklist

Before changing nameservers:

Document current DNS records — Export or screenshot all records
Create records at new provider — Set up the same records
Verify records match — Compare old and new configurations
Test new nameservers — Query directly to confirm records work
Lower TTL — Reduce DNS propagation time (optional but recommended)

Step-by-Step Process

Step 1: Set up new DNS zone

# Create zone at new provider (e.g., Cloudflare)
# Import or manually create all DNS records

Step 2: Verify records at new provider

# Query new nameservers directly
dig @ada.ns.cloudflare.com example.com A
dig @ada.ns.cloudflare.com example.com MX
dig @ada.ns.cloudflare.com example.com TXT

Step 3: Change nameservers at registrar

Log into registrar (e.g., Namecheap)
Find “Nameservers” or “DNS” settings
Select “Custom DNS” or “Custom nameservers”
Enter new nameservers:
- ada.ns.cloudflare.com
- bob.ns.cloudflare.com
Save changes

Step 4: Wait for propagation

# Check propagation status
dig NS example.com +short

# May take 24-48 hours for full propagation

Step 5: Verify and cleanup

# Confirm new nameservers are responding
dig @8.8.8.8 example.com A

# Remove old zone after propagation complete (optional)

Common Nameserver Formats

Different providers use different naming schemes:

; Cloudflare (assigned per account)
ada.ns.cloudflare.com
bob.ns.cloudflare.com

; AWS Route 53 (assigned per hosted zone)
ns-123.awsdns-45.com
ns-456.awsdns-78.net
ns-789.awsdns-01.org
ns-012.awsdns-23.co.uk

; GoDaddy
ns1.domaincontrol.com
ns2.domaincontrol.com

; Namecheap
dns1.registrar-servers.com
dns2.registrar-servers.com

; Porkbun
maceio.ns.porkbun.com
salvador.ns.porkbun.com
fortaleza.ns.porkbun.com
curitiba.ns.porkbun.com

Common Configurations

Cloudflare (Full Setup)

; Nameservers assigned by Cloudflare
example.com.    NS    ada.ns.cloudflare.com.
example.com.    NS    bob.ns.cloudflare.com.

; Includes:
; - DDoS protection
; - CDN (proxied records)
; - SSL certificates
; - Web Application Firewall

AWS Route 53

; Four nameservers per hosted zone
example.com.    NS    ns-123.awsdns-45.com.
example.com.    NS    ns-456.awsdns-78.net.
example.com.    NS    ns-789.awsdns-01.org.
example.com.    NS    ns-012.awsdns-23.co.uk.

; Geographic diversity built-in

Registrar DNS (e.g., Namecheap)

; Using registrar's included DNS
example.com.    NS    dns1.registrar-servers.com.
example.com.    NS    dns2.registrar-servers.com.

; Simple but limited features

Subdomain Delegation

; Main domain on Cloudflare
example.com.        NS    ada.ns.cloudflare.com.
example.com.        NS    bob.ns.cloudflare.com.

; Subdomain delegated to different nameservers
dev.example.com.    NS    ns-123.awsdns-45.com.
dev.example.com.    NS    ns-456.awsdns-78.net.

Best Practices for MSPs

1. Standardize on One DNS Provider

Benefits of consolidation:

Single management interface for all clients
Consistent features across domains
Easier training for team members
Better visibility across all DNS

2. Document Nameserver Changes

Track for each client:

Current nameservers
Current DNS provider
Registrar where nameservers are set
Date of last change
Reason for configuration

3. Always Keep Old Records During Transition

Never delete old DNS zone until:

New nameservers are confirmed active
Propagation is complete (24-48 hours)
All services verified working

4. Use Dedicated DNS Providers Over Registrar DNS

Why use Cloudflare, Route 53, etc.:

Better performance (anycast, global)
More features (API access, advanced records)
Better security (DDoS protection)
More reliable

5. Test Before Switching

# Always query new nameservers directly before changing
dig @new-ns1.provider.com example.com A
dig @new-ns1.provider.com example.com MX
dig @new-ns1.provider.com example.com TXT

# Verify all critical records exist and are correct

6. Have at Least Two Nameservers

This is required by DNS standards:

Provides redundancy
Most providers give you 2-4 nameservers
Geographically distributed is better

7. Use Unified DNS for Visibility

Managing nameservers and DNS across multiple clients is complex. Unified DNS provides:

Visibility into nameserver configuration across all clients
DNS record comparison between providers
Migration assistance and backup
Documentation sync to Hudu

Troubleshooting Nameservers

Nameservers Not Responding

# Check if nameservers are resolvable
dig ada.ns.cloudflare.com A

# Check if nameservers respond to queries
dig @ada.ns.cloudflare.com example.com A

# Check at registrar level
dig NS example.com @g.gtld-servers.net

Inconsistent Nameserver Responses

# Query each nameserver individually
dig @ns1.provider.com example.com A
dig @ns2.provider.com example.com A

# Results should match - if not, synchronization issue

Propagation Issues After Change

# Check if TLD has updated (may take 24-48 hours)
dig NS example.com @g.gtld-servers.net

# Compare to expected nameservers
# Old nameservers showing = propagation not complete

Lame Delegation

Problem: Nameservers set at registrar don’t have a zone for the domain.

# Test for lame delegation
dig @ns1.provider.com example.com SOA

# If SERVFAIL or no answer, nameserver doesn't have the zone
# Fix: Create zone at DNS provider before pointing nameservers

Frequently Asked Questions

How many nameservers should I have?

Minimum two (required by RFC). Most providers give you 2-4. More than 4 provides diminishing returns.

Can I use nameservers from different providers?

Technically yes, but it requires keeping DNS records synchronized between providers. This is complex and generally not recommended.

How long does it take to change nameservers?

24-48 hours for full propagation, though many resolvers update within a few hours. TLD servers cache NS records with high TTLs.

What’s the difference between changing nameservers and changing DNS records?

Changing nameservers: Moves DNS control to a different provider
Changing DNS records: Modifies individual records at your current provider

Nameserver changes propagate slower because NS records are cached at the TLD level.

Can I have different nameservers for subdomains?

Yes, this is called “subdomain delegation.” You add NS records for the subdomain in your main zone, pointing to different nameservers.

What happens if my nameservers go down?

Your domain becomes unreachable. Cached responses continue working until their TTL expires, then all services fail. This is why multiple nameservers and reliable providers are important.

Get Started with Unified DNS

Managing nameservers and DNS across multiple clients and registrars is challenging. Unified DNS lets you view, modify, audit, and backup all DNS records regardless of nameserver provider — with support for Cloudflare, Porkbun, NameSilo, and more in one dashboard.

Unified DNS is live — try it free for a month with code FREETRIAL2026 at billing setup. No commitment. Or request a demo for a walkthrough.