Add Website Hosts UK to your device
Install for quick access to hosting, tools, billing and support.
Learn what nameservers are, how they connect your domain to DNS records and hosting, and what happens when you change nameservers.
Nameservers are one of the most important parts of how domains work. They tell the internet where your domain’s DNS records are managed. If your domain is the name people type, nameservers tell the internet where to find the instructions for that name.
You will usually deal with nameservers when setting up a new domain, connecting a domain to web hosting, moving a website to a new host, changing DNS provider, or setting up services such as business email.
This guide explains what nameservers are, how they work, how they relate to DNS records, when you should change them, and what to check before making nameserver changes.
The name people type, such as yourbusiness.co.uk.
Tell the internet where DNS is managed.
Tell the domain where website, email and services go.
Nameservers are the servers that tell the internet where your domain’s DNS records are stored. When someone visits your domain, nameservers help locate the DNS records that point the domain to your website, email hosting and other services. Changing nameservers can move DNS control from one provider to another.
Nameservers do not usually host your website. They tell the internet where to find the records that point to your website.
A nameserver is a server that stores or points to DNS information for a domain. When someone types your domain into a browser, the internet needs to know where that domain should go. Nameservers help answer that question by directing lookups to the correct DNS zone.
Every domain uses nameservers. They are usually set at the domain registrar, which is the company where the domain is registered. The nameservers may belong to your registrar, your hosting provider, a DNS provider or another service.
For example, if your domain is registered in one place but your website hosting is somewhere else, you may be asked to update your nameservers so the hosting provider can manage your DNS records.
Your domain is registered, such as yourbusiness.co.uk.
They tell the internet where your DNS records are managed.
Records such as A, CNAME, MX and TXT control website and email routing.
Nameservers and DNS records are closely connected, but they are not the same thing. Nameservers tell the internet where to look for the DNS records. DNS records are the actual instructions that control what happens to your domain.
A helpful way to think about it is this: nameservers are like the address of the office where your domain instructions are stored. DNS records are the instructions inside that office.
If you change a DNS record, you are changing one instruction. If you change nameservers, you may be changing where all the instructions are managed.
| Item | What it does | Example |
|---|---|---|
| Nameservers | Tell the internet where your domain’s DNS records are managed. | ns1.examplehost.co.uk |
| A record | Points a domain to an IPv4 address. | Your website points to a hosting server IP. |
| CNAME record | Points one hostname to another hostname. | www points to your main domain. |
| MX record | Controls where email is delivered. | Email goes to your email hosting provider. |
| TXT record | Stores verification or authentication information. | SPF, DKIM, DMARC or domain verification. |
When someone visits your website, their browser needs to find the correct server. The process happens quickly in the background. Nameservers play a key role in helping the lookup reach the correct DNS records.
The visitor types your domain into a browser. A DNS resolver checks which nameservers are responsible for the domain. Those nameservers provide the DNS records needed to find the website, email service or other connected service.
Most visitors never see this process. They simply type your domain and the website loads. But if the nameservers are wrong, the internet may not know where to find the correct records.
Someone types yourbusiness.co.uk.
It looks for the domain’s authoritative nameservers.
It provides the DNS record for the requested service.
The browser connects to the correct hosting server.
Nameservers matter because they decide where DNS control lives. If the nameservers point to the wrong provider, changes made somewhere else may have no effect. This is one of the most common causes of confusion when setting up domains, hosting and email.
For example, you might update an A record inside your hosting control panel, but if your domain is still using your registrar’s nameservers, that hosting control panel change may not be live. You need to update DNS wherever the active nameservers are pointing.
This is why checking nameservers is one of the first steps when troubleshooting domain, website or email problems.
You may need to change nameservers when moving DNS management from one provider to another. This often happens when connecting a domain to a new hosting provider, moving a website, using a specialist DNS provider, or setting up a platform that wants to manage DNS for you.
Changing nameservers is a bigger change than updating one DNS record. It can affect your website, email, subdomains, verification records and other services connected to the domain.
Before changing nameservers, always check which DNS records currently exist. If important records are not copied to the new DNS provider, services may stop working.
Do not change nameservers without copying existing DNS records first. If your domain uses business email, website verification, payment services, booking systems or third-party tools, missing records can break those services.
Many domain changes can be done without changing nameservers. If you only need to point your website to a new hosting server, you may only need to update the A record. This keeps DNS management in the same place and changes only the website destination.
Changing nameservers moves DNS control to a different provider. This can be useful, but it is more disruptive if not planned properly. If the new DNS provider does not have the same MX, TXT, CNAME and verification records, services may fail.
A simple rule is this: change a DNS record when you only need to change one instruction. Change nameservers when you want to move DNS management to a different provider.
| Change type | What changes | Common use |
|---|---|---|
| Change A record | Only the website IP instruction changes. | Pointing a domain to new web hosting while keeping DNS where it is. |
| Change CNAME record | One hostname points to another hostname. | Connecting www, platforms or third-party services. |
| Change MX records | Email delivery destination changes. | Moving email to a new provider. |
| Change nameservers | The whole DNS management location changes. | Moving DNS control to a hosting provider, registrar or DNS platform. |
Web hosting is where your website files and databases live. Nameservers tell the internet where to find the DNS records that point your domain to that hosting.
Some hosting providers ask you to change nameservers to theirs. This means they will manage DNS for your domain. Other providers give you an IP address and ask you to update an A record instead.
Both methods can work. If you want a simple setup, using your hosting provider’s nameservers can be convenient. If you want to keep DNS with your registrar or DNS provider, updating individual records may be better.
If you are setting up a new website, compare our UK Web Hosting, WordPress Hosting and Small Business Hosting options.
Email is one of the biggest reasons to be careful with nameserver changes. Your domain’s MX records control where email is delivered. TXT records such as SPF, DKIM and DMARC help with email authentication.
If you change nameservers and forget to copy email records, your website might work but email could stop. This is especially risky for businesses that rely on customer enquiries, quotes, invoices, bookings or support messages.
If you use professional domain-based email, make sure all mail records are copied before changing nameservers. If you need business email using your own domain, visit our Business Email Hosting page.
Usually controlled by A or CNAME records.
Usually controlled by MX and TXT records.
Often controlled by TXT or CNAME records.
Nameserver changes can take time to appear everywhere. This delay is often called DNS propagation. Some networks may see the new nameservers quickly, while others may continue using cached information for longer.
During propagation, different people may see different results. One visitor might reach the new website while another still reaches the old setup. This can be normal for a while after a DNS or nameserver change.
You can use our DNS Propagation Checker to monitor DNS changes. You can also use DNS Lookup to inspect records for a domain.
If a nameserver change has only just been made, avoid repeatedly changing records in panic. Check the active nameservers, confirm records are correct, then allow time for DNS caches to refresh.
You can check nameservers using a DNS lookup tool or through your domain registrar account. The registrar will usually show which nameservers are currently assigned to the domain.
Checking nameservers is useful before making changes, during a website move, or when troubleshooting why DNS records do not appear to be working.
If you update a DNS record in one control panel but nothing changes, check the nameservers. You may be editing DNS in the wrong place.
If nameservers are wrong, your domain may not find the correct DNS records. This can cause the website to stop loading, email to fail, subdomains to break, or connected services to stop verifying.
Sometimes the issue is not that the nameservers are wrong, but that the DNS records at the new nameservers are incomplete. For example, the website record may have been added but the email records were missed.
If something breaks after a nameserver change, check the DNS records at the active nameservers first. The missing record is often the cause.
www works but the main domain does not.SSL certificates help websites load securely over HTTPS. Nameservers do not directly create SSL certificates, but DNS records can affect whether SSL can be issued or verified.
If a domain points to the wrong hosting server after a nameserver change, SSL may fail to issue. If DNS verification records are missing, some certificate providers may not be able to validate the domain.
After changing nameservers or moving hosting, use our SSL Checker to confirm your certificate is active and correct.
Nameserver changes should be planned. Before making the change, record all existing DNS records. This includes website records, email records, subdomains, verification records and third-party service records.
Then recreate those records at the new DNS provider before or immediately after switching nameservers. Once the change is made, monitor propagation and test key services.
For business websites, always test the website, email, contact forms, SSL, checkout, booking systems and any connected tools after the change.
www version.A local business moves its website to a new host. The new host asks the business to change nameservers. The business changes them, and the new website starts loading. However, email stops working because the old MX records were not copied.
The safer approach would have been to copy all DNS records first, especially email records. Then, after changing nameservers, the business should test website loading, email delivery, SSL and contact forms.
A business uses one provider for website hosting and another for email hosting. This is common and can work well. The important point is that the DNS records must send website traffic to the web host and email traffic to the email provider.
If the business changes nameservers to the web host but forgets to add the email provider’s MX records, email may break. Nameservers do not decide email by themselves; the active DNS records do.
A business owner updates an A record at their domain registrar, but the website does not change. After checking, they find the domain is actually using nameservers from the hosting provider, so the registrar’s DNS editor is not active.
The fix is to edit DNS wherever the active nameservers point. This is why checking nameservers first can save a lot of time.
The biggest mistake is changing nameservers without copying existing DNS records. This can break email, subdomains, website verification, payment tools, booking systems and other services.
Another common mistake is editing DNS records in the wrong place. If the domain is using one provider’s nameservers, changes made in another provider’s DNS panel may not affect the live domain.
It is also a mistake to assume DNS changes are instant everywhere. Propagation can take time, and different networks may see different results during the transition.
Once you register a domain, nameservers help connect it to hosting, email and DNS services.
Nameservers tell the internet where your domain’s DNS records are managed. Those DNS records then point your domain to your website, email and other services.
No. Nameservers tell the internet where DNS records are stored. DNS records are the actual instructions for website, email and service routing.
Not always. Sometimes you can simply update the A record to point to the new hosting server. Changing nameservers moves DNS management to another provider.
Yes. If MX and email-related TXT records are not copied to the new DNS provider, email delivery or authentication may stop working.
Some changes appear quickly, while others take longer because of DNS caching and propagation. Use a DNS propagation checker to monitor updates.
Nameservers are usually changed at your domain registrar, which is the company where your domain is registered.
If you need a domain name, visit our Domain Services. If you are connecting a domain to a website, compare our UK Web Hosting, WordPress Hosting and Small Business Hosting options.
If you need professional email on your domain, explore Business Email Hosting. Always check MX, SPF, DKIM and DMARC records before changing nameservers.
Not sure where to begin? Visit Start Here and choose the right setup for your domain, website and email.
Check current nameservers.
Copy existing DNS records.
Test website, email and SSL after changes.
Nameservers tell the internet where your domain’s DNS records are managed. They are a key part of connecting domains to websites, email hosting and online services.
The most important thing to remember is that changing nameservers can move DNS control from one provider to another. That makes nameserver changes more powerful than simply editing one DNS record.
Before changing nameservers, copy your existing DNS records, pay special attention to email records, and test everything afterwards. A careful nameserver change can be smooth, but a rushed one can break websites, email and connected services.
Add Website Hosts UK to your device
Install for quick access to hosting, tools, billing and support.