Nameservers vs DNS records
The difference between changing nameservers and editing individual DNS records — and when to use each approach to manage where your domain points.
When we need to update where your domain sends visitors or email, there are two different ways to do it. One is to change nameservers. The other is to edit individual DNS records. Knowing which is which saves a lot of confusion.
Quick summary
Nameservers control where your DNS is managed. DNS records are the individual settings (like A, CNAME, MX) that tell the internet what to do. Changing nameservers hands control of all DNS to a new provider. Editing DNS records makes smaller, targeted changes without moving control.
The simple analogy
Think of it this way:
- Nameservers are like choosing which company runs your filing cabinet (where all your records live).
- DNS records are the individual files inside that cabinet.
When you change nameservers, you're moving the filing cabinet to a new company. When you edit DNS records, you're updating a file inside the cabinet — without moving anything.
What are nameservers?
Every domain is assigned a set of nameservers — usually two or more. When someone looks up your domain, the internet asks your nameservers for the answer. Nameservers are set at your registrar.
Typical nameserver addresses look like:
ns1.cloudflare.com/ns2.cloudflare.comdns1.registrar-servers.com/dns2.registrar-servers.com
What are DNS records?
DNS records are the specific instructions stored at your nameservers. Each record type does a specific job:
- A record — maps your domain to your website's IP address
- CNAME record — creates an alias pointing to another domain name
- MX records — route email to your email provider
- TXT records — verify ownership and configure email security
See DNS records explained for a full breakdown.
When to change nameservers
Change nameservers when:
- A service like Cloudflare needs to manage all your DNS for performance or security
- Your new web host asks you to delegate DNS to them (some hosts prefer this)
- You're migrating to a platform like Squarespace that manages DNS centrally
Important: Changing nameservers means all your DNS records need to be recreated at the new nameserver provider. Your MX records (email), any existing CNAMEs, and other settings must be carried over — otherwise email and other services will break.
When to edit DNS records
Edit individual DNS records when:
- You're connecting a new website to an existing domain (update the A record)
- You're setting up email (add or update MX records)
- You need to verify domain ownership with Google, Microsoft, or another service (add a TXT record)
- You're adding a subdomain
- Your nameservers aren't changing — you're just making a targeted update
This is a smaller, less disruptive change.
Side-by-side comparison
Changing nameservers
- Moves all DNS control to a new provider
- All records must be recreated at the new provider
- Can affect website AND email
- Used for major migrations
- Takes effect within a few hours to 48 hours
Editing DNS records
- Makes targeted changes at your current DNS provider
- Only the updated record is affected
- Easy to undo
- Used for specific connections (new site, new email, verifications)
- Usually takes effect in minutes to a few hours
Always back up your DNS records before changing nameservers
Before switching nameservers, write down or screenshot all your current DNS records — especially MX records for email. You'll need to recreate them at the new provider. Forgetting this is the most common cause of email going down during a site migration.
Common questions
Related guides
- DNS records explained (A, CNAME, MX, TXT)
- Pointing your domain to a new site
- Cloudflare basics for clients
- Email DNS records (MX, SPF, DKIM, DMARC)
- DNS propagation: why changes take time
Need a hand?