Nameservers vs DNS Records: What Is the Difference and When to Change Each
One of the most confusing aspects of domain management is the difference between nameservers and DNS records. Both relate to DNS, both are configured at your domain registrar, and changing either one affects how your domain works. But they serve fundamentally different purposes, and changing the wrong one during a migration can cause serious problems. This guide explains the difference clearly.
What Are Nameservers?
Nameservers are the servers that hold your domain's DNS records. They are the authoritative source of truth for your domain's DNS configuration. When any computer on the internet needs to look up your domain, it ultimately queries your nameservers to get the answer.
Every domain has at least two nameservers (for redundancy). They are set at your domain registrar and look something like:
ns1.dnsprovider.comns2.dnsprovider.com
Your nameservers determine where your DNS records are managed. They are like the address of the filing cabinet that contains all your domain's information.
What Are DNS Records?
DNS records are the individual entries that define what your domain does. They are stored on your nameservers and queried whenever someone accesses your domain. The most common DNS records include:
- A record: Maps your domain to an IPv4 address (where your website is hosted)
- CNAME record: Creates an alias from one domain to another
- MX record: Specifies which servers handle email for your domain
- TXT record: Stores text data like SPF, DKIM, and verification codes
DNS records determine what happens when someone accesses your domain. They are the individual documents inside the filing cabinet.
The Key Difference
Nameservers = Where your DNS records are stored and managed
DNS records = The actual instructions that control where traffic goes
Changing nameservers is like moving your entire filing cabinet to a different office. All of your DNS records move with it (or more accurately, you need to recreate them at the new location). Changing a DNS record is like updating a single document in the filing cabinet — everything else stays the same.
When to Change Nameservers
You should change your nameservers when:
- Switching DNS providers: Moving from your registrar's default DNS to a specialised provider like Cloudflare, AWS Route 53, or Google Cloud DNS
- Setting up a CDN that acts as a DNS proxy: Cloudflare requires you to point your nameservers to their servers to enable their proxy features
- Moving to managed DNS: When your old DNS provider does not support records or features you need
Important: When you change nameservers, all DNS records must be configured at the new DNS provider. The old DNS records are no longer used. This means you need to recreate every A record, MX record, TXT record, and CNAME record at the new provider before making the switch. Failure to do this will cause your website, email, and other services to stop working.
When to Change DNS Records
You should change individual DNS records when:
- Migrating to a new web host: Update the A record to point to the new server's IP address
- Changing email providers: Update MX records to point to the new email service
- Adding a subdomain: Create a new A or CNAME record for the subdomain
- Setting up email authentication: Add TXT records for SPF, DKIM, and DMARC
- Verifying domain ownership: Add a TXT or CNAME record for Google Search Console, Microsoft 365, etc.
Changing individual DNS records is the most common operation. Most hosting migrations only require updating the A record — you do not need to change nameservers.
Common Mistakes
Changing nameservers when you only need to change an A record
This is the most common mistake. To move your website to a new host, you typically only need to update the A record. Changing nameservers is unnecessary and risky — you might lose email configuration, verification records, and other DNS settings in the process.
Changing nameservers without recreating all DNS records
If you change nameservers to a new DNS provider, all existing DNS records at the old provider become irrelevant. If you did not copy your MX records, SPF records, and other TXT records to the new provider, email and other services will break immediately.
Not testing before switching
Whether you are changing nameservers or DNS records, always test the new configuration before making the change. Use HostCheck to preview your website on the new server IP before updating the A record. For nameserver changes, verify that all records are correctly configured at the new DNS provider before switching.
How to Check Your Current Nameservers
You can check your domain's nameservers using the command line:
nslookup -type=ns example.com
Or use an online WHOIS lookup tool to see the nameserver information in your domain registration details.
Conclusion
Understanding the difference between nameservers and DNS records prevents costly mistakes during migrations. In most cases, a web hosting migration only requires changing the A record — not the nameservers. Reserve nameserver changes for when you are actually switching DNS providers. And regardless of what you are changing, always test first with tools like HostCheck and verify that all DNS records are correctly configured before making any switch.