Walkthrough · Beginner · 5 minutes plus propagation
How to Change Nameservers
Hand a domain's DNS to a different provider with every record arriving in one piece — a hands-on walkthrough in plain words that names the classic mistake before you reach it.
The short answer
The job: hand a domain's DNS to a different provider with every record arriving in one piece. Time to set aside: 5 minutes plus propagation. Skill needed: beginner.
Below are the precise steps, the classic stumble, and one tip from the support desk. Wherever the platform already does a step for you, the guide says so rather than handing you a machine's chores.
By the Hosting & Domains team · Reviewed 18 August 2026
Beginner
Experience required
4
Stages, start to finish
Free
Support included
Proven
On the platform itself
No prior knowledge assumed — a hosting account, a browser and 5 minutes plus propagation of attention is the whole entry requirement. Every instruction runs on our platform exactly as printed, and carries over to any standard cPanel host.
First rule: read the snag section before you start, not afterwards. It was distilled from the tickets of everyone who tried the other order.
How the work divides up
Over the whole job, you will take a copy of the zone as it stands, build the new zone first, change the delegation at the registrar and check it, then test the lot.
Every stage is a few minutes of unhurried clicking — the total depends mostly on how well you already know the control panel. The detailed instructions are further down; read the whole path once before you begin.
Where it comes off, and how to stay on
Leaving the TXT records behind. SPF, DKIM keys and service verifications fail without a murmur, and you find out when mail bounces or an integration goes quiet, by which point nobody links it to the nameserver change.
It earns a section of its own because it is no obscure edge case — it is the single commonest reason this task reaches a support queue. Knowing it in advance turns the whole job from risky into routine.
The habit that keeps this easy for good
Leave the old provider's zone in place for a fortnight afterwards. An untouched copy sitting there is an immediate way back if something turns out to have been missed.
Habits this small are what separate the people who find hosting effortless from the people who find it draining. The same tools on both sides — a different way of working.
The steps already done before you arrive
Steps that never deserved your time are taken out: certificates issue and reissue themselves, the installer handles application setup, the daily copy absorbs the what-ifs, and per-site settings live in a panel rather than a configuration file. The guide covers the remainder — the part that is actually about your site.
Should a step still misfire, support answers at any hour with an actual fix rather than a knowledge-base link and a shrug. Half the guides on this site began as repeat patterns in our ticket queue.
The hosting these steps were tested on
Tutorials written against imaginary hosting go stale fast. Ours are written against the real thing: the same panel, installer and defaults waiting in your account.
NVMe storage and LiteSpeed caching sit under every tier, the smallest plan included — that is the floor here, not an upgrade.
- Every step checked exactly as published
- The snag named before it arrives
- The dull steps taken out of your way
- People reachable at any hour you stall
Why Hosting & Domains
Standard on every plan
Honest about how big it is
Hand a domain's DNS to a different provider with every record arriving in one piece is a beginner-level job — set aside 5 minutes plus propagation, with the platform-absorbed steps marked.
Works exactly as printed
Every step is proven on the platform we run — none of the 'your host may vary' hedging.
Help that keeps your hours, not ours
Stuck on step three at midnight? Support answers at any hour, mid-walkthrough included.
Every undo written out
Any step that could bite is marked, together with the exact way to wind it back.
Taken from real tickets
These guides came out of the support queue, so every snag flagged is one people genuinely hit.
4 steps, nothing padded
Each stage is a few minutes of steady clicking, and the fiddly moments are labelled fiddly.
Quick Start
Order placed to site online
- 1
Take a copy of the zone as it stands
Export or photograph every record at the current provider: A, CNAME, MX, TXT, the lot. Once delegation moves, only the new nameservers reply, and any record you failed to carry across simply no longer exists.
- 2
Build the new zone first
Enter the records you need at the receiving provider before the switch. The new nameservers then hold the right answers from the very first query, and no visitor meets a gap.
- 3
Change the delegation at the registrar
In the registrar's panel for that name, replace the old nameserver pair with the new one. That single edit is the handover itself; everything before it was preparation.
- 4
Check it, then test the lot
Look the domain up from two or three different networks or through a propagation tool, then confirm the website, the mail and any verification records are all coming out of the new zone.
Built In
Fitted to every plan
- No set-up charge at any point, and no joining fee
- Webmail in the browser plus IMAP, POP and SMTP for any client
- A daily copy, with restores you run yourself from the panel
- DDoS filtering absorbed at the network edge
- WordPress and 400+ further applications installed in one click
- LiteSpeed caching in the server itself rather than bolted on by plugin
- PHP versions set per site from the control panel
- cPanel, which is what most of the industry already runs
- Money back within 30 days on hosting plans, 7 on reseller
- A renewal figure identical to the one you registered at
Frequently Asked
The questions that come up most
How long does a nameserver change take from start to finish?
The registry updates within minutes. Resolvers around the world catch up over the following one to forty-eight hours, depending on the TTLs that were set beforehand. In practice most of your traffic is on the new zone inside a few hours.
Can the nameservers carry my own brand?
They can. Reseller and VPS accounts can run private nameservers such as ns1.yourbrand.com, supported by glue records at the registrar. For one website it is decoration; for anybody selling hosting under their own name it repays the setup.
Can more than one website run on a single plan?
From the Turbo tier upward, yes — several sites, each with its own name, mailboxes and certificate, inside one account. If the extra sites belong to clients rather than to you, look at reseller hosting instead: it keeps each one properly walled off.
Does hosting include mail?
Yes — every hosting plan includes mailboxes at your own name, with webmail, IMAP, POP and SMTP plus spam filtering on from the start. There is standalone email hosting too, for a name whose website lives somewhere else.
Keep reading
How to Minify CSS and JavaScript
Slim down and reorder how code reaches the browser, without wrecking the site on the way — intermediate level, about 30 minutes.
How to Restore From a Backup
Get files, database, or both back without panic, and no further back than necessary — beginner level, about 10–30 minutes.
DNS (Domain Name System) (Glossary)
The full definition, along with the practical consequence nobody bothers to mention.
WordPress Hosting
WordPress looked after for you — LiteSpeed caching, staging copies and a daily backup.
Web Hosting
cPanel hosting on NVMe drives — SSL, the migration and year one of the name all included.
Changing hosts? Run through our checklist first.
A plain order of work for a move nobody visiting will notice: which files go over first, how to carry the mail across without losing a message, when exactly to repoint DNS, and the two mistakes behind nearly every outage we are asked to rescue.
The name is waiting.
NVMe hosting with SSL and the migration included, people answering at any hour, and a price that stays where it was.
View WordPress Hosting plans