What a nameserver is
Every domain name has a set of authoritative nameservers, usually two or more, listed at the domain registrar. When someone types your domain into a browser, their device asks a recursive resolver (their ISP's, or a public one like Cloudflare's 1.1.1.1 or Google's 8.8.8.8) for the address. The resolver works down from the root servers to the .uk or .com servers, which say "ask these nameservers", and the authoritative nameservers give the final answer from the domain's DNS zone. The resolver caches that answer for the record's TTL so the next lookup is instant.
A nameserver looks like ns1.example.com, and a domain's nameservers are usually a matching pair or trio: ns1, ns2, ns3. You can see any domain's nameservers with a WHOIS lookup or the command dig NS example.com.
The difference between DNS and nameservers
DNS is the whole system: the naming, the hierarchy, the resolvers and the records. Nameservers are the specific servers that hold and publish a domain's records. Changing nameservers moves the entire zone to a different provider. Changing a DNS record changes one answer inside the zone and leaves the nameservers where they are. Most day-to-day changes (pointing the website at a new host, adding a mail record) are record changes, not nameserver changes.
Who provides your nameservers
Usually one of three: the domain registrar, the web host, or a dedicated DNS provider such as Cloudflare. Registrar nameservers are the default and fine for simple sites. Hosting nameservers make sense when the host manages the site and the DNS together, as ours do for domains registered with us. Cloudflare's nameservers add a CDN and proxy in front of the site. Resellers and agencies often run private nameservers (ns1.theirbrand.co.uk) that point at the host's DNS, so clients never see the hosting company's name; that's included on our reseller hosting plans.
Nameservers publish DNS information for a domain. When you set authoritative nameservers at your registrar, you identify the service responsible for answering DNS questions about that domain. The individual records then tell clients where to find services such as the website and email.
Nameservers and records are different
An NS record identifies a nameserver. An A or AAAA record points a hostname to an IP address, while an MX record identifies mail delivery destinations. TXT records can carry verification and email policy information. Cloudflare's explanation of NS records describes the role of authoritative nameservers.
Changing the website's destination does not always require changing nameservers. If you keep the DNS provider, updating the relevant web records may be enough. Moving nameservers usually means preparing the whole zone at the new DNS provider first.
Before changing nameservers
Save the current DNS zone and list every service using it. Check website records, mail records, verification entries and subdomains. Recreate the required records at the new provider and verify them before switching the delegation at the registrar. If DNSSEC is enabled, coordinate the signing and registrar DS records with the DNS providers so old validation settings do not break the move.
Why changes take time to appear
Resolvers cache answers for their TTL. Different visitors may therefore use different cached answers during a change. Reducing a TTL helps only after the old cached value has expired. Keep the old service available for the agreed transition and check both the authoritative answer and what public resolvers return.
Keep email in the plan
A website may be hosted with one company and email with another. Do not replace working MX and related TXT records with a hosting provider's defaults unless email is deliberately moving too. Test incoming and outgoing mail separately from loading the homepage.
Our migration checklist includes DNS and mail checks. Agencies using reseller hosting can also use private nameservers under their own brand; ask the team which delegation and glue records your setup needs before changing them.
Nameserver FAQs
What is a nameserver used for?
Answering DNS queries for a domain: which IP address serves the website, which servers receive its email, and the TXT records used for verification and email security. Without working nameservers a domain resolves to nothing.
What is an example of a name server?
Registrar and hosting nameservers follow the pattern ns1.provider.tld and ns2.provider.tld. Cloudflare assigns pairs with names like ada.ns.cloudflare.com. A reseller's private nameservers might be ns1.agencyname.co.uk.
How do I find the nameservers of a domain?
Run a WHOIS lookup on the domain, or use dig NS yourdomain.co.uk from a terminal. Both show the authoritative nameservers currently set at the registrar. Our guide to WHOIS privacy explains what else a WHOIS record shows.
How long does a nameserver change take?
Registries usually publish the change within minutes to a few hours, but resolvers keep cached answers until the old TTL expires, so different visitors can see different results for up to a day or two. Lower the TTLs a day before a planned move, and keep the old service running until the new answers are everywhere.
Hosting that keeps up
Your domain and your hosting on one bill.
Search, register and transfer domains in the same panel as your hosting, with a UK team to call when DNS gets fiddly.
