How to Change Nameservers (and What Breaks If You Rush It)
Two fields, a save button, and a warning that the change “may take up to 48 hours”. That’s all most registrar panels show you before you change nameservers, which is not much to go on when the change is about to affect your website, your email and possibly your search rankings all at once.
Nameservers themselves are simple. What breaks when people change them in a hurry is almost never the nameserver setting itself. It’s everything attached to the records that don’t get copied across first.
Here’s what nameservers actually do, how to change them without losing email or taking the site down, and how long the change really takes to settle. It’s one of the more technical steps covered across the switching hosts guides, worth reading alongside the rest if a full move is what’s driving the change.
Short answer: Copy every DNS record, especially MX records for email, from the old nameservers to the new ones before you switch. Lower the TTL a day or two beforehand to shorten the wait, then change the nameservers at your registrar. Most changes are visible within a few hours, with 48 hours as the commonly quoted worst case.
What are nameservers, and why would you need to change them?
Nameservers are the servers that hold your domain’s DNS records and answer the question “where does this domain actually point?” whenever someone visits your site or sends you an email. Changing them means telling your domain to ask a different set of servers for those answers, usually because you’re moving to a new host that manages DNS itself.
You’d typically change nameservers, rather than just editing individual DNS records, when you’re switching to a host that wants full control of your DNS zone. If you’re only changing where your site points but keeping the same DNS management, editing individual records instead is usually simpler and safer.
What breaks if you change nameservers without preparing first?
Email is the most common casualty. If the MX records aren’t recreated at the new nameservers before the switch, mail addressed to your domain starts bouncing or disappearing the moment the change takes effect, because there’s nowhere for it to be routed. Website downtime is the second most common issue, if the new nameservers don’t yet have a working A record pointing at a live server.
- Missing MX records mean email stops arriving with no obvious error message anywhere.
- A missing or wrong A record means visitors hit an error page instead of your site.
- Subdomains, like a staging site or a mail-related subdomain, silently stop resolving if they weren’t copied across.
- SPF and any other TXT records get dropped if someone just copies the “obvious” records and skips the rest.
None of these need to happen if the records are prepared properly first, and the site itself doesn’t have to go down during the process at all. The guide to avoiding downtime during a migration covers the same preparation from the site’s side rather than the DNS side.
How do you change nameservers step by step?
Get everything ready at the new nameservers before you touch the switch itself, then make the change and confirm it’s landed correctly. Rushing the order is what causes almost every problem people run into.
- List every DNS record currently in use: A, MX, TXT (including SPF), CNAME, and anything else showing in your current DNS zone.
- Recreate every one of those records at the new nameservers before changing anything at the registrar.
- Lower the TTL on your current records to 300 seconds a day or two before the planned change, so old cached answers clear faster.
- Update the nameservers at your domain registrar to the new values.
- Check that the site, email and any subdomains are resolving correctly on the new nameservers.
- Keep the old host and its DNS active for a few days as a safety net before fully decommissioning it.
The domain and hosting side of a full move is covered together in the step-by-step guide to moving a website to a new host, worth reading before you start if the nameserver change is part of a wider migration rather than a standalone task. The migration checklist is a useful companion to work through alongside this list, since it catches a few things beyond DNS that are easy to miss.
How long does a nameserver change actually take to go live?
For .au domains, registry and nameserver changes are typically visible within a few hours. The commonly quoted worst case is up to 48 hours, and that figure comes from resolvers holding a cached copy of the old records until their TTL expires, not from any central process pushing the change out.
| TTL on the old record | What it means for the wait |
|---|---|
| 300 seconds (5 minutes) | Old answers clear almost immediately once you switch |
| 3,600 seconds (1 hour) | Most resolvers pick up the change within the hour |
| 86,400 seconds (24 hours) | Some visitors can keep reaching the old nameservers for a full day |
That’s why lowering the TTL before you make the change matters more than anything you do on the day itself. If the record has been sitting at a 24 hour TTL for years, dropping it to 300 seconds the moment you switch doesn’t help. Resolvers need to see that shorter TTL before the old high value expires, which is why the change needs a day or two of lead time.
How do you change nameservers without breaking your email?
Confirm your MX records at the new nameservers before you switch, not after, and check them against exactly what’s currently live at the old nameservers. A mismatched or missing MX record is the single most common reason email stops working after a nameserver change, and it’s entirely avoidable with a five minute check beforehand.
If your email runs through a different provider than your hosting, which is common, get their exact MX values first rather than guessing from an old screenshot or a support article that may be out of date. Test by sending a message to the domain once the new nameservers are live, and don’t decommission the old nameservers until you’ve confirmed mail is actually arriving.
How do you check whether a nameserver change has actually worked?
Query the new nameservers directly rather than trusting what your own browser shows you, since your own device may still be holding a cached answer. A DNS lookup tool that lets you specify which server to ask will confirm what the domain’s authoritative nameservers are actually returning right now, which is the only answer that matters.
Check the record at the new nameservers first, then check again through a general public resolver to see what a typical visitor would get. If the two disagree, that’s expected for a while and simply reflects caching still working its way through, not a sign anything is broken.
Frequently asked questions
Can I change nameservers myself, or do I need my host to do it?
You can usually do it yourself through your domain registrar’s account panel, which is where nameservers are set regardless of who hosts the site. Some hosts will also do it for you as part of a migration if you’d rather not handle that step directly.
What’s the difference between changing nameservers and changing a single DNS record?
Changing nameservers hands over management of your entire DNS zone to a new set of servers, so every record needs recreating there first. Changing a single record, like an A record, edits just that one entry while everything else stays exactly where it was. Nameserver changes are the bigger, riskier move of the two.
Will changing nameservers affect my domain’s WHOIS or ownership record?
No, nameservers only control where DNS queries are answered. Ownership, registration details and the licence itself are entirely separate from which nameservers a domain is pointed at, and changing them doesn’t touch any of that.
Can I revert to my old nameservers if something goes wrong?
Yes, as long as the old nameservers and their records are still active, you can point the domain back at them the same way you changed it in the first place. That’s exactly why it’s worth keeping the old hosting running for a few days after a switch rather than cancelling it immediately.
Do I need to change nameservers every time I move to a new host?
Not always. If the new host is happy for DNS to stay managed elsewhere, you can often just update the individual A and MX records instead and leave the nameservers as they are. Whether that’s the right approach depends on how your DNS is currently set up and managed.
If a nameserver change is part of a bigger move rather than a standalone fix, GoodHost’s migrations page sets out what the wider process involves, including how the DNS side is handled alongside moving the site itself.