Nameservers vs DNS Records: What's the Difference?

When your domain stops resolving, you're often faced with two separate places to look: your domain registrar's nameserver settings, and your DNS provider's zone records. Knowing which one to check — and understanding why they're different things — saves significant diagnostic time.

Nameservers: The Authority Delegation Layer

A nameserver is a server that holds the authoritative DNS records for a domain. When someone looks up yourdomain.com, the global DNS system needs to know which server to ask for the answer. That's what nameservers define.

Your domain's nameservers are set at the registrar level. They tell the rest of the internet: "To get DNS records for this domain, ask this server."

# See what nameservers are set for a domain
dig yourdomain.com NS +short
# Returns something like:
# ns1.cloudflare.com.
# ns2.cloudflare.com.

When you switch hosting providers or move to Cloudflare, you're usually changing nameservers — telling the internet to start asking a different authority for your domain's records.

Nameserver changes are managed at your domain registrar (GoDaddy, Namecheap, Google Domains, etc.) — not at your hosting provider. The IANA root zone database is the ultimate source of truth for which registrars manage which TLDs.

DNS Records: The Actual Answers

DNS records live inside a nameserver. They're the actual answers to DNS queries — what IP address does this domain resolve to, where does email go, what's the SPF record.

Common DNS record types:

• A record — maps a domain to an IPv4 address
• AAAA record — maps a domain to an IPv6 address
• CNAME — aliases one domain to another
• MX — specifies mail servers for a domain
• TXT — stores arbitrary text (SPF, DKIM, verification tokens)
• NS — delegates a subdomain to different nameservers

# See all DNS records at the authoritative nameserver
dig yourdomain.com ANY @ns1.cloudflare.com

# Check a specific record type
dig yourdomain.com A @ns1.cloudflare.com
dig yourdomain.com MX @ns1.cloudflare.com

DNS records are managed at your DNS provider — which is sometimes your registrar, sometimes your hosting provider, and sometimes a dedicated DNS service like Cloudflare or Route 53.

The Relationship Between the Two

The nameserver setting at the registrar points to the DNS provider. The DNS provider holds the actual records.

Your Registrar → "For yourdomain.com, ask ns1.cloudflare.com"
                    ↓
Cloudflare (ns1.cloudflare.com) → "yourdomain.com A record = 203.0.113.42"

This is why changing nameservers affects everything. When you switch nameservers from your old host to Cloudflare, all your DNS records need to exist at the new nameserver — the old host's records stop being authoritative.

Why This Matters for Troubleshooting

Symptom: "I changed my A record but the site still points to the old server"

Check nameservers first:

dig yourdomain.com NS +short

If the nameservers point to your old host, your A record change at the new host isn't the authoritative answer. The world is still asking your old host.

Symptom: "I updated the nameservers but nothing is resolving"

The new nameserver may not have all your DNS records. When you switch nameservers, you need to recreate all existing records (A, MX, TXT, CNAME) at the new DNS provider before the switch completes.

Symptom: "My domain resolves but email is broken after migration"

MX records weren't transferred when nameservers changed. Check:

dig yourdomain.com MX @new-ns1.yourdnsprovider.com

Who Manages What

If your registrar and DNS provider are the same (e.g. you're using GoDaddy for both registration and DNS), this distinction is less visible — but it still exists internally.

Monitoring Both Layers

Nameserver changes and DNS record changes are separate events that warrant separate monitoring. An unexpected nameserver change is a serious security event — it means someone redirected your entire domain to a different DNS authority. An unexpected A record change means traffic is being sent to a different server.

Domain Monitor monitors your DNS records continuously and alerts when any record changes — including nameserver changes. Create a free account to add DNS monitoring for your domain.

See A record vs CNAME vs ALIAS: which should you use? for more on individual record types, and what is DNS propagation for how changes at the nameserver level spread to the rest of the internet.

Also in This Series

• How to Change Nameservers Without Downtime
• DNSSEC Explained for Website Owners
• CAA Records Explained and Why They Matter for SSL
• How to Monitor Nameserver Changes Across Client Domains
• Registrar Lock vs Transfer Lock: What's the Difference?
• How to Prevent Domain Hijacking With Registrar Security
• Why DNS Works in One Location but Fails in Another