A domain name such as `yourbusiness.co.uk` is easy for customers to remember. Behind it, however, your website, email and other online services need precise instructions to know where they live. If you have asked, what is a domain nameserver, the simple answer is that it is part of the system that directs people and services to the right place when they use your domain.
Nameservers work quietly in the background, but they matter whenever you launch a website, move hosting, set up professional email or troubleshoot why a domain is not showing the expected site. Understanding the basics can make these jobs far less confusing.
What is a domain nameserver?
A nameserver is a server that holds DNS information for your domain. DNS stands for Domain Name System. Think of it as the internet’s directory service: it translates a familiar domain name into the technical information needed to find a website, email service or other online tool.
When someone types your domain into their browser, their device needs to find the web server hosting your site. It asks the DNS system where to look. Your domain’s nameservers provide the answer by pointing the request towards the DNS records associated with that domain.
For example, your domain might use nameservers supplied by your web hosting provider. Those nameservers can then tell browsers which IP address holds your website. They can also tell email providers where messages for `[email protected]` should be delivered.
Most domains have at least two nameservers. This provides resilience. If one server is temporarily unavailable, another can respond, helping to keep your online services reachable.
Nameservers, DNS records and hosting: the difference
These terms are often used together, which is why they can seem interchangeable. They each have a separate role.
Your domain name is the address people use, such as `yourbusiness.co.uk`. A domain registrar is the company through which that domain is registered and renewed. Your web host stores the website files, databases and email services that make up your online presence.
Nameservers sit between the domain and the services it uses. They establish where the DNS settings for the domain are managed. Within those DNS settings are individual DNS records. Each record gives a specific instruction.
An A record, for instance, points a domain or subdomain to an IPv4 address. A CNAME record directs one name to another name, often used for `www`. MX records control where email is received. TXT records are commonly used to verify domain ownership and support email security measures such as SPF, DKIM and DMARC.
A useful way to picture the relationship is this: the registrar records who controls the domain, the nameservers identify the DNS directory responsible for it, and the DNS records contain the individual directions to the website and email services.
Why nameservers matter to a business website
For a small business, nameservers are not just a technical detail. Incorrect settings can mean customers see an old website, a holding page or an error instead of your business. They can also disrupt email, which is often more damaging than a website issue when enquiries, bookings and invoices depend on it.
The right nameserver arrangement makes it possible to manage your website and email in a clear, consistent place. If your domain, hosting and email are supplied by one provider, using that provider’s nameservers is often the simplest option. The provider can manage the relevant DNS records as part of the hosting setup, reducing the chance of conflicting settings.
That said, keeping the domain and hosting with different providers can work perfectly well. Some businesses do this because they have an established registrar, use a specialist email platform or need a particular DNS service. It simply requires more care: the DNS records must point accurately to every service you use, and you need to know which provider is responsible for making changes.
When would you need to change nameservers?
You do not normally need to change nameservers once a domain is working properly. A change is usually needed when you are moving where DNS is managed, rather than merely changing one setting within existing DNS.
Common situations include moving your website to a new host, transferring domain management to a provider that will manage both hosting and DNS, or using a specialist DNS platform for a more complex setup. Your new provider should give you the nameserver addresses to enter at the domain registrar. They often look similar to `ns1.examplehost.co.uk` and `ns2.examplehost.co.uk`.
Changing nameservers is different from updating a DNS record. If you only need to connect a new website platform, add a verification record or change email delivery settings, you may only need to amend an A, CNAME, MX or TXT record. Changing the nameservers unnecessarily can replace the whole DNS zone and remove records that existing services rely on.
Before making any change, check where your DNS is currently managed and take a copy of every existing record. This is particularly important if you use business email, Microsoft 365, a third-party payment service, subdomains or email security records.
What happens after a nameserver change?
After you save new nameservers with your registrar, the change has to be recognised across DNS systems worldwide. This process is commonly called DNS propagation. It can take up to 24 to 48 hours, although many changes are seen sooner.
During that period, some people may reach the new website while others still see the old one. This is normal, as different internet providers refresh their stored DNS information at different times. Email can also be affected if the new DNS zone does not contain the correct MX and related records from the outset.
For this reason, plan a nameserver change rather than treating it as a quick switch. Avoid making several unrelated DNS changes at the same time. Keep the old hosting active until you have confirmed that the new website, contact forms and email are all working as expected.
How to change domain nameservers safely
The exact screens vary by registrar, but the process follows the same general pattern. First, obtain the correct nameserver details from the provider that will manage your DNS. Next, log in to the account where your domain is registered, find the domain management area and replace the existing nameservers with the new ones.
Before confirming, make sure the new DNS service already contains the records your business needs. At minimum, that usually means the website record and the correct MX records for email. It may also include `www`, autodiscover settings, SPF, DKIM, DMARC, verification records and any subdomains used for booking systems or client portals.
Once the change is submitted, test your main services from more than one connection where possible. Check the website on a browser, send and receive a test email, and submit a contact form. If something is missing, do not assume it is only propagation. Compare the records in the new DNS zone with the previous configuration.
If you are transferring a website and email at the same time, support from a hosting provider can be valuable. A managed migration and a reviewed DNS setup reduce the risk of a disruption during a busy working day.
Common nameserver problems
A website displaying the wrong content after a move is often caused by an old DNS record, cached information or nameservers that still point to the previous provider. If email stops arriving after a change, missing or incorrect MX records are a likely cause.
Another common issue is having DNS records split across two providers. For example, a domain may use one provider’s nameservers while records are updated in another provider’s control panel. In that situation, the changes will have no effect because only the DNS zone attached to the active nameservers is being used.
It is also possible to create a mismatch between website and email services. A new host may set up the website correctly but not know that your email remains with Microsoft 365 or another provider. The website can appear to work while email records have been replaced. This is why a full list of services connected to the domain is worthwhile before any move.
Frequently asked questions about domain nameservers
Do I need nameservers for my domain?
Yes. A registered domain needs active DNS delegation to connect it to a website, email or other service. Even a domain that is not yet being used will normally have default nameservers set by its registrar.
Can I use different nameservers for my website and email?
A domain normally has one authoritative set of nameservers. Within the DNS zone they manage, however, you can direct website traffic and email to different providers using the appropriate records.
Are nameservers the same as an IP address?
No. Nameservers direct DNS queries to the place where your DNS records are held. An IP address is one of the technical addresses a DNS record may return for your website server.
Will changing nameservers affect email?
It can. Email will continue to work only if the new DNS zone contains the correct MX, TXT and any other required email records. Check these carefully before making the switch.
A nameserver change is often a one-off task, but it affects the foundations of your online presence. If you are unsure which records your website or email depend on, pause before changing anything and get the setup checked. A little care at this stage helps keep your site available, your email flowing and your business easy to find.
