What are nameservers?

Nameservers are the servers that hold the authoritative DNS records for your domain. When someone looks up your domain, the chain ends at whichever nameservers your registrar says are in charge, and whatever they answer is the truth.

They usually look like a pair:

ns1.examplehost.com
ns2.examplehost.com

Two or more, for redundancy.

The distinction that matters

There are three separate things people conflate, and untangling them prevents most domain confusion:

• Registrar — where you bought the domain and pay to renew it
• DNS host — whose nameservers answer queries for it
• Web host — where the website's files actually live

These are frequently three different companies, and that is completely normal. Your domain can be registered at one company, use another's nameservers, and point at a third's web server.

Confusing the three is why people log into their registrar, change a record, and see nothing happen — because the domain's nameservers point at a different provider entirely, and that is where the live records are.

What changing nameservers actually does

It moves every record at once: web, email, verification records, subdomains, all of it.

This is the crucial difference from editing a single A record. If you switch nameservers to a new provider that does not yet have your MX records, your email stops. Not degrades — stops.

Always recreate every existing record at the new provider before you switch. Export or screenshot the current zone first.

When you should change them

• Moving DNS to your web host so records live alongside the site
• Moving to Cloudflare or a similar performance/security layer, which requires using their nameservers
• Consolidating several domains under one DNS provider
• Your current DNS provider is slow or unreliable — DNS lookup time is part of page load

When you should not

• Just to move the website. If your DNS is already somewhere you are happy with, changing the A record is enough, and far lower risk.
• Because a host's setup guide says to. It is the easiest instruction for them to write; it is not always the best option for you. Pointing an A record achieves the same thing with a fraction of the blast radius.
• Mid-campaign, or on a Friday. Give yourself room to fix it.

Doing it safely

1. Export the current zone. Every A, AAAA, CNAME, MX, TXT and SRV record. Miss one and you will find out which when something breaks.
2. Create all of them at the new provider first. The zone should be complete and correct before it is live.
3. Check MX and TXT especially. Email and domain verification are what people forget.
4. Change the nameservers at the registrar.
5. Verify from outside. Use the DNS lookup tool to confirm each record type resolves correctly.
6. Keep the old DNS zone in place for a week. Do not delete it the same day — it is your rollback.

Glue records and vanity nameservers

If you run ns1.yourdomain.com pointing at your own server, you need glue records at the registrar: the IP addresses of those nameservers, registered alongside the domain. Without them there is a chicken-and-egg problem — resolving your nameserver requires querying your nameserver.

Most people never need this. It matters for hosting resellers who want branded nameservers.

How to see what is live right now

Nameservers are public. The Who Hosts This Site? tool shows the current nameservers for any domain, along with the mail provider and hosting, which is the quickest way to work out who is actually in charge of a domain you have inherited.

If the nameservers do not match the control panel you have been editing, you have found your problem.