Nameservers vs DNS Records: What’s the Difference?

You’ve been told to “update your DNS.” But your registrar offers two options: change the nameservers, or edit the DNS records. Pick the wrong one and your site — or worse, your email — can go offline. The two are closely related but do very different jobs.

This guide explains nameservers vs DNS records in plain words, when to change each, and the mistakes that break sites.

The DNS chain in plain words

When someone visits yourdomain.com, a lookup happens in steps:

1. The visitor’s resolver asks the registry for your domain (for example, the .com registry): “Who is responsible for this domain?”
2. The registry answers with your nameservers, such as ns1.provider.com.
3. The resolver asks those nameservers: “What’s the IP address for this domain?”
4. The nameservers answer using your DNS records, such as an A record pointing to your server.

Think of nameservers as the phone book you’re sent to, and DNS records as the entries inside that phone book.

What nameservers do

Nameservers decide which company answers DNS questions for your domain. You set them at your registrar. Common choices:

• Your registrar’s own nameservers (the default when you buy a domain).
• Your hosting company’s nameservers, so the host manages DNS for you.
• A dedicated DNS provider such as Cloudflare.

Only one set of nameservers is active at a time. Whoever owns those nameservers is where your DNS records must live. For help choosing, see Cloudflare DNS vs Registrar DNS: Which Should You Use?.

What DNS records do

DNS records are the actual answers: where the website lives (A, AAAA), aliases (CNAME), where email goes (MX), and verification and email security (TXT). You edit them inside the DNS zone at whichever provider your nameservers point to.

Here’s the key point: editing records at a provider that isn’t your active nameserver does nothing. The world never asks that provider. A full breakdown of each type is in DNS Record Types Explained: A, AAAA, CNAME, MX and TXT.

When to change nameservers vs records

Change DNS records when:

• You’re moving your website to a new server but keeping the same DNS provider.
• You’re adding email, a subdomain, or a verification record.
• You want the change to be fast and low-risk.

Change nameservers when:

• You want a different company to manage all of your DNS (for example, moving to Cloudflare).
• Your host requires its nameservers for a managed setup.

Pointing a domain to hosting for the first time? Follow How to Point a Domain to Your Hosting.

Common mistakes that break sites

• Changing nameservers without copying records. The new provider starts with an empty or auto-generated zone. Missing MX records mean email stops arriving.
• Editing records at the wrong provider and wondering why nothing changes. Check your active nameservers first.
• Mixing providers: some records at the registrar, others at the host. Keep everything in the zone your nameservers point to.
• Expecting instant results. Nameserver changes can take up to 24–48 hours; record changes depend on TTL.
• Typos in nameserver names, which can take the whole domain offline.

Key takeaways

• Nameservers decide who answers for your domain.
• DNS records are the answers themselves.
• Changing nameservers switches you to a new zone — copy every record first.
• For most moves, editing records is faster and safer.