Move from explanation to action with the matching DomainCheck.co.uk tools for this topic.
Check live resolution before and after a DNS or transfer change.
Useful when a UK domain transfer depends on TAG or registrar handling.
Check TLD context when transfer and DNS behaviour can vary by namespace.
Changing nameservers is one of those tasks that sounds simple but can disrupt a live site if the DNS zone is not ready. It is different from changing a registrar, and it is different from moving email. A website can go offline simply because the new nameserver does not yet contain the right web records. This guide focuses on the website side only. That keeps the advice practical and avoids mixing it with email records, which deserve their own checklist.
When you change nameservers, you are telling the domain to use a different DNS zone as the source of truth. That zone contains the records that direct visitors to the website.
If the new zone is missing the correct website records, the domain may still resolve, but it may resolve incorrectly. That is why a nameserver change needs preparation, not just a settings update.
The safest approach is to build the replacement DNS zone first.
Check that the new DNS host has:
If you are not sure what records the site uses, export the current zone or copy it record by record. Do not rely on memory.
| Record | Why it matters | Typical failure |
|---|---|---|
| A / AAAA | Routes the bare domain to the website host. | The root domain stops resolving or points to the wrong server. |
| CNAME for www | Keeps the www hostname aligned with the main site. | The www version loads differently from the root domain. |
| Verification TXT | Proves ownership to hosting or CDN services. | SSL, CDN, or platform integrations fail to validate. |
| Subdomains | Supports app, checkout, staging, or booking flows. | Only the homepage works and a key workflow breaks. |
One of the easiest mistakes is deleting or disabling the old DNS zone too early. Even after you change nameservers, caches and resolvers can continue to refer to the previous setup for a short period.
Leaving the old zone in place temporarily gives you a fallback if you spot a missing record or typo. That is especially helpful for business sites where even a small outage is visible to customers.
A nameserver switch is not the moment to clean up old DNS in a hurry. Keep the old zone available until you have checked the live site from more than one network.
If your DNS provider lets you edit TTL values, lowering them before the move can reduce the time it takes for future changes to settle.
That said, TTL is not a magic switch. It can help with the next lookup cycle, but it does not guarantee instant global change. Different resolvers behave differently, so plan for a transition period.
Once the new zone is complete and checked, update the domain's nameservers at the registrar.
After the change, test:
If the site uses redirects, confirm they still work. If the site sits behind a CDN or platform service, confirm that the provider-specific records are still correct.
The new zone matches the old one and users never notice the change.
The apex record or www record was missed, so one hostname works and the other does not.
The DNS zone is incomplete, so the domain resolves to nowhere or to the wrong host.
The most common problems are simple but costly:
These mistakes often show up as "domain not resolving", a blank site, or a certificate mismatch.
Modern websites often depend on more than one service. You may need records for a hosted website builder, CDN, analytics, domain verification, or security tooling.
When you move nameservers, those platform records need to exist in the new DNS zone too. If a provider gives you a specific record set, copy it exactly. Recreate the values, not just the names.
If the goal is to keep the website live, avoid bundling in extra changes unless there is a good reason.
Do not change:
Those can all be managed separately. Keeping the change narrow makes it easier to spot the real cause if something stops working.
Watch the site for a short period after the update.
Check:
If something fails, compare the old and new zones record by record. A missing A record or typo in a CNAME is often enough to cause the problem.
You can change nameservers without breaking a website if the new DNS zone is complete before the switch, the old zone stays available during the transition, and you verify the live site afterwards.
In practice, the safest rule is simple: build first, switch second, test last.