A nameserver is a server that holds the DNS records for your domain and answers questions about it. When a browser or mail server wants to know where yourbusiness.co.uk lives, it is directed to your domain’s nameservers, and they reply with the address of your website, your email servers and anything else you have set up.
How nameservers work
Every domain has a pair or more of authoritative nameservers, set at your domain registrar. They usually look like ns1.yourhost.com and ns2.yourhost.com, or a pair of names assigned by a service such as Cloudflare. The registry for your domain ending, Nominet for .uk domains, keeps a note of which nameservers are in charge.
The nameservers hold the zone file: the list of DNS records such as A records for the website, MX records for email and TXT records for verification and email security. Changing a single record means editing it wherever the nameservers point. Changing the nameservers themselves means handing the entire zone to a different provider, which reads only its own copy.
Nameserver changes take time to spread. Resolvers around the world cache the old answer, and changes at the registry level can take up to 24 to 48 hours to be seen everywhere, though often far less.
Why it matters
Nameservers are where control of your domain really sits. Whoever runs the DNS provider your nameservers point to controls where your website, email and verifications go. For many UK small businesses, that is the original web designer’s hosting account, which becomes a problem when the relationship ends.
They are also the most common cause of self-inflicted outages during a website project. A new host asks you to switch nameservers to them, the new zone holds only the website records, and email, Google Search Console verification and Microsoft 365 records vanish at once. The site looks fine, so nobody connects the silent inbox to the change.
Nameservers also decide where new services plug in. Pointing them at Cloudflare puts its content delivery network and firewall in front of your site. Connecting a domain to a website builder such as Wix or Squarespace by nameserver often hands that builder your whole DNS, so email and verification records then have to be added there. When a new tool asks you to add a TXT or CNAME record to prove you own the domain, knowing which provider is in charge saves a lot of trial and error.
Common mistakes
- Switching nameservers before recreating every existing record, especially MX records and TXT records for SPF, DKIM and verification.
- Editing records at the old host after the domain has moved, and wondering why nothing happens.
- Leaving DNSSEC switched on at the registrar with the old provider’s keys, so the domain stops resolving entirely after the change.
- Mixing nameservers from two providers, so visitors get different answers depending on which one replies.
- Not knowing who has the registrar login, so the nameservers cannot be changed when a host closes or an account lapses.
How to act on it
Find out where your nameservers point with a WHOIS lookup or a DNS checker, then confirm you can log in to both the registrar and the DNS provider. Export or screenshot the full DNS zone and keep it somewhere safe.
If you need to change nameservers, recreate every record at the new provider first, lower TTL values a day ahead, deal with DNSSEC, then switch early in the week. Test the website, send and receive email, and check Search Console verification afterwards. This is one of the checks in any website migration I run.