Every domain name is registered somewhere, at a domain registrar, and that registration record includes a setting called nameservers. Nameservers are the addresses that tell the wider internet which company actually manages the domain’s day-to-day DNS records, the ones that decide where your website and email actually point.

Think of the registrar as the deed office and the nameservers as the property manager. The registrar confirms you own the domain. The nameservers are wherever you have handed the keys to run it.

Changing nameservers is usually a single settings change inside your registrar’s dashboard, but it has a large effect. It moves control of every DNS record for that domain to a new provider in one step. For a business with an active website and working email, that single setting is worth understanding before anyone touches it.

Why it matters to you

Whoever’s nameservers your domain points at effectively controls your website and email, because they control the records underneath. If your nameservers still point at an old web host or a provider you no longer work with, that provider can still change where your domain sends traffic, even if you have not spoken to them in years.

This is also the step where things most often go wrong during a switch of providers. Point the nameservers at the wrong place, or make the change without the records ready on the other end, and a business can lose email and its website at the same time, sometimes for hours.

How I set it up

When I move a client onto Cloudflare, pointing the nameservers is one of the last steps, done only after every DNS record has been copied over and checked on the new side first. That order matters. I want the new setup fully built and verified before the switch happens, so the change itself is close to instant and invisible to visitors.

For a domain with an active redirect map or working mail, I walk the client or their registrar contact through the change live, on a short call, rather than sending instructions and hoping they get followed correctly. It typically takes about ten minutes.

What it looks like in practice

Once the nameservers are changed, the update spreads across the internet over a period of minutes to about a day, depending on how the domain was configured before. Most visitors never notice a gap, because the old and new records are set up to match before the switch happens. Afterward, every DNS change for that domain happens in the new account, and the old provider has no further say in where your domain points.

Questions I get about this

Do I need to change nameservers often?
Almost never. You change them once, when you decide who should manage your domain's DNS, and then you leave them alone. Repeated changes are usually a sign something is being moved around behind the scenes without a clear reason.
Who is allowed to change my nameservers?
Whoever has access to your domain registrar account. That is exactly why it matters who holds that login, and why a ten-minute nameserver change is worth doing on a call with someone you trust rather than handing the task off blind.

Want this set up properly for your business?

This is the kind of thing I build every week. Grab a time and we will talk through what fits.