Nameservers, explained
If a domain name is an address, nameservers are the directory that says which book to look the address up in. They're one of the least visible parts of owning a domain, and one of the most powerful — changing them is the single biggest thing you can do to a domain, for better or worse.
What a nameserver actually does
Every domain's registration record includes a short list of nameservers — usually two to four. When any device anywhere in the world wants to reach your domain, it first asks: "who's authoritative for this name?" The answer is your nameservers. Whatever they say next — where your website lives, where your email goes, any other rule in your DNS zone — is treated as the truth.
That's the key distinction worth holding onto: your domain registration says which nameservers to trust; the nameservers themselves hold the actual instructions, in the form of DNS records (the A, MX, CNAME and TXT entries we cover in our guide to DNS records). Registration and DNS are two different systems that happen to be connected by this one pointer.
Why changing them is the biggest lever you have
Most changes to a domain are small and specific — add one DNS record, update one setting. Changing nameservers is different: it swaps out the entire source of truth for the domain in one move. Point them at a new provider, and every record that provider hasn't already been told about — your website, your email, anything else — effectively goes dark until it's set up again on the new side.
This is exactly why it's usually the last step in moving a website or email to a new host, not the first: get everything working under the new nameservers' records before the switch, and the changeover is invisible. Do it the other way around, and visitors hit a blank zone until you catch up.
Using your own nameservers vs. a provider's
Most people never touch this setting — a registrar or hosting provider sets sensible defaults, and that's the right call for a straightforward website and inbox. There are still real reasons to point a domain at your own nameservers instead: running your own DNS infrastructure, using a specialized DNS provider for advanced routing, or consolidating several domains under one system you already manage elsewhere.
The trade-off is straightforward: your own nameservers mean full control and full responsibility. A misconfigured record on infrastructure nobody's watching is a website that quietly stops resolving, sometimes for days before anyone notices. If you don't have a specific reason to manage it yourself, there usually isn't one waiting to be discovered.
Changes aren't instant. Nameserver updates propagate across the internet's resolvers gradually rather than all at once — often within a couple of hours, but sometimes up to 24–48 hours depending on how long previous answers were cached. This isn't a bug in any one system; it's a deliberate trade-off DNS makes everywhere, favoring speed for the other 99.99% of lookups over instant updates for the rare change.
The practical takeaway
You'll rarely need to think about nameservers day to day — until the moment you do, at which point it's worth knowing exactly what's about to move. Before changing them: make sure whatever you're pointing at already has the records it needs, ready to answer the moment the switch takes effect. After changing them: give it time before assuming something's broken — a domain that "isn't working" an hour after a nameserver change is very often just still propagating.
If you're weighing whether to manage your own DNS or keep things simple, our website builder and hosting handle nameservers and DNS together, so a new site is reachable the moment it's published rather than a separate step to remember.