A domain can be registered in one place, hosted somewhere else and use email from a third provider. What are hosting nameservers in that setup? They are the settings that tell the internet where to look for the DNS records that direct visitors and services to the right destination.
For most website owners, nameservers only need attention when launching a site, changing hosting providers or moving DNS management. Yet one incorrect change can leave a website offline, stop email arriving or interrupt verification services. Understanding the basics gives you more control and makes domain changes far less stressful.
What are hosting nameservers?
Nameservers are specialised servers that store and provide DNS information for a domain name. DNS, or the Domain Name System, works rather like the internet’s address directory. It translates a memorable address such as `yourbusiness.co.uk` into the technical details browsers, email servers and other services need.
When someone enters your domain into a browser, their device needs to find out where the website lives. Your domain’s nameservers answer the first key question: which DNS provider holds the records for this domain? That DNS provider then supplies the relevant record, usually an IP address, so the browser can connect to the web server.
Nameservers are commonly shown as a pair, such as:
`ns1.examplehost.co.uk` `ns2.examplehost.co.uk`
Using at least two provides resilience. If one nameserver cannot respond, another can normally provide the same DNS information. This helps keep your domain reachable and avoids a single point of failure.
Nameservers, hosting and DNS records: the difference
These terms are often used interchangeably, but they do different jobs.
Your domain registrar is the company through which you register and renew your domain. The registrar holds the domain registration and lets you set the authoritative nameservers.
Your web host stores your website files, databases and application environment. It may also manage your DNS, but it does not have to. You can host a website with one provider while keeping DNS with your registrar or a dedicated DNS service.
Your nameservers point the domain towards the DNS provider that controls its records. Finally, the DNS records are the individual instructions within that provider’s DNS zone. These can include an A record for your website, MX records for email and CNAME records for services such as `www` or verification tools.
Think of nameservers as the signpost to the directory, while DNS records are the entries inside it. Changing nameservers hands control of the full DNS zone to a different provider. Editing an individual DNS record changes one instruction while leaving the existing DNS provider in charge.
This distinction matters. If your DNS already contains email, Microsoft 365, Google Workspace, SPF, DKIM or third-party service records, a full nameserver switch can remove them unless they are recreated at the new provider.
When should you change hosting nameservers?
You may need to update nameservers when a new hosting provider supplies its own nameservers and asks you to use them. This is common with shared hosting packages where DNS, website hosting, SSL and mailbox settings are managed in one control panel.
It can be a convenient option for a new website. Your host can create the standard records needed for the website, and ongoing management is kept in one place. For customers who want straightforward domain management, this reduces the number of systems to check.
However, changing nameservers is not always necessary when moving a website. If your DNS is managed at the registrar or through a separate DNS service, you can often leave the nameservers unchanged and amend only the A record or CNAME record to point to the new host. This approach is often safer for established businesses with complex email and third-party DNS settings.
The right choice depends on where your DNS is currently managed, what services rely on the domain and who will maintain the records in future. Convenience is useful, but retaining DNS with a dedicated provider can offer more control for agencies, developers and businesses with several connected services.
How to change nameservers safely
Nameserver changes are made at the domain registrar, not usually in your hosting account. The exact menu labels vary, but the process is broadly the same.
First, collect the nameserver addresses supplied by the new DNS or hosting provider. Next, make a complete note of the existing DNS zone before changing anything. Record A, AAAA, CNAME, MX, TXT and SRV records, paying particular attention to email and verification records.
Then sign in to the account where the domain is registered, locate the domain’s nameserver settings and replace the existing entries with the new pair or set. Save the change. At the new DNS provider, confirm that the necessary records are already in place.
Do not cancel the old hosting or DNS service immediately. Keep it available until the new DNS settings have propagated and you have tested the website, email and any essential integrations. This small overlap is often the difference between a controlled migration and a rushed recovery.
Check email before and after the switch
Email is the service most frequently affected by nameserver changes. Your website may appear to work while messages stop arriving because the MX records were not copied across.
Before switching, note every MX record and any TXT records used for SPF, DKIM and DMARC. If you use Microsoft 365, Google Workspace or another hosted email platform, its documentation will specify the records required. Recreate these precisely in the new DNS zone, then send and receive test messages after the change.
Also check subdomains. A business may use separate addresses for client portals, shop systems, staging sites, remote access or marketing platforms. Each can rely on its own DNS record.
How long do nameserver changes take?
Nameserver changes can begin appearing within a few hours, but allow up to 24 to 48 hours for worldwide propagation. During that period, different internet providers and devices may continue using cached information from the previous DNS setup.
This does not necessarily mean anything is wrong. DNS caching is designed to make browsing faster and reduce unnecessary lookups. The result is that one person may see the new website while another still reaches the old one for a while.
Plan important changes outside peak trading hours where possible. Avoid making several unrelated DNS changes at once, as that makes troubleshooting harder. Once the new nameservers are active, test the main domain, `www` version, email delivery and any critical subdomains from more than one connection or device.
Common nameserver problems and what they mean
A website showing a server error after a move may be a hosting configuration issue rather than a nameserver issue. But if the domain cannot be found at all, displays an old site or sends email to the wrong place, DNS is a likely cause.
The most common problems are incomplete DNS records at the new provider, a spelling error in the nameserver hostname, nameservers registered with the wrong domain account, or a domain that is still using cached details. Another frequent mistake is setting nameservers to a new host before the hosting account and website have been configured.
For a simple website, the usual essentials are an A record for the root domain and a record for `www`. For a business domain, the DNS zone can be much more detailed. This is why copying the existing zone before making a change is good practice, even when the move appears straightforward.
If you are unsure which records are needed, do not guess or delete entries to tidy up the zone. Ask your hosting, domain or email provider for confirmation. At Blended Hosts, 24/7 technical support can help customers check the practical steps involved in a hosting or domain move.
Do you need your host’s nameservers?
No. Your website can run perfectly well without using your hosting provider’s nameservers. The host only needs the correct DNS records to point visitors to its servers.
Using your host’s nameservers is often the easier route for a new site or a single-provider setup. Keeping nameservers with your registrar or a dedicated DNS provider can be preferable when you need independent DNS control, manage multiple hosting environments or rely on advanced email and third-party records.
The key is ownership and visibility. Make sure the person responsible for the domain can access the registrar account and knows where DNS is managed. A domain is a valuable business asset, and its DNS settings should not be left unclear when a developer, agency or supplier changes.
Before changing nameservers, take ten minutes to document what your domain currently does. That simple check protects the services your customers depend on and gives you the confidence to make the move at the right time.
