Nameservers vs DNS Records:What's the Difference?

Nameservers decide who is in charge of your domain's DNS. DNS records are the individual answers that DNS service gives, such as the IP address of your website (A record) or your mail servers (MX records). You change nameservers at your registrar; you change DNS records at whichever DNS host those nameservers belong to.

Mixing these up is the most common cause of "I changed DNS and nothing happened". Here is how they relate and which to change when.

An analogy

Think of a large office building:

• Nameservers are the reception desk you choose for the building.
• DNS records are the entries in that reception's directory: "web team, room 5; mail, room 9".

If you hire a new reception desk (change nameservers), the old directory is no longer consulted, so every entry must exist at the new desk.

Where each one is set

	Nameservers	DNS records
Set at	The registrar where the domain is registered	The DNS host the nameservers point to
Example values	ns1.examplehost.com, ns2.examplehost.com	A @ 203.0.113.10, MX @ mail.example.com
Controls	Which service answers DNS for the whole domain	Where the website, email and other services are
How often changed	Rarely	Whenever services move or are added

Option 1: Change nameservers to your host

Point the domain's nameservers to your hosting provider. The host then manages all DNS records, usually creating sensible defaults for the website and email automatically.

Good when: the host is the centre of everything (website and email), and you want it to manage DNS.

Watch out for: records you had elsewhere (verification TXT records, a separate email service's MX records, subdomains) must be recreated at the new host, or they stop working.

Option 2: Keep nameservers, edit records

Keep DNS where it is (registrar, Cloudflare or another DNS service) and change only the records that matter, usually the A record for the root domain and www.

Good when: email or other services are hosted elsewhere, you use a DNS service like Cloudflare, or you only want to move the website.

Watch out for: you must update records yourself if the host changes IP address.

Which should you choose?

• Website and email both on one host, nothing else: change nameservers.
• Email on a separate service, or many custom records: keep your DNS and edit the A record.
• Using Cloudflare: nameservers point to Cloudflare; records at Cloudflare point to your host. See how to set up Cloudflare DNS.

Step-by-step instructions for both options are in how to point a domain to hosting.

What happens to email when you change nameservers

Email depends on MX, SPF, DKIM and DMARC records. If you change nameservers and the new DNS host does not have the same records, email can stop arriving or start going to spam. Before changing nameservers:

1. Export or note every record at the current DNS host.
2. Recreate them at the new DNS host (or let the host create email records if email is moving there too).
3. Then change nameservers.

See MX records explained and SPF, DKIM and DMARC explained.

Worked example: "I changed the A record but nothing happened"

A business edited the A record of example.com in its registrar's DNS panel to point to new hosting, waited a day, and the old site still appeared.

1. A WHOIS lookup showed the domain's nameservers were ns1.oldhost.example and ns2.oldhost.example, belonging to the old hosting company, not the registrar.
2. So the internet was asking the old host's DNS for answers; the registrar's DNS panel was not in use at all, and the edit there had no effect.
3. Two possible fixes: edit the A record in the old host's DNS (if the account still exists), or change the nameservers to the new host (after recreating all needed records there).
4. They chose to change nameservers to the new host, copied the MX and TXT records first, and the site switched within a few hours.

The lesson: before editing any record, check which nameservers the domain uses, so you edit the DNS zone that actually answers.

Checking which DNS host answers for your domain

dig NS example.com +short

The output lists the authoritative nameservers. Then confirm a specific record directly from them:

dig @ns1.yourdnshost.example example.com A +short

If this shows the new value but public resolvers still show the old one, you are only waiting for caches; see DNS propagation explained.

How long changes take

• Nameserver changes depend on the TTL of the NS records at the TLD level, often up to 24–48 hours to be seen everywhere.
• Record changes follow the record's own TTL, which you control.

See DNS propagation explained.

How to check what is currently set

• A WHOIS lookup shows the nameservers registered for the domain.
• A DNS lookup tool shows the records being served.
• If the records you edited do not appear, check that you edited them at the DNS host the nameservers point to.

Frequently Asked Questions

Can I use my registrar's nameservers and host the website elsewhere?

Yes. Keep the registrar's nameservers and set the A record (and www) to your host's IP address.

Do I need to change nameservers when I change hosting?

No. You can either change nameservers to the new host or keep your DNS and update the records.

Why are there two or more nameservers?

For redundancy: if one is unreachable, resolvers use another.

Related reading

For how DNS works overall, see what is DNS and domain names explained. Manage your domains through the ServerNeed domain search.

Sources

• Cloudflare Learning Center: What is a DNS NS record?