Your hosting account is live. Your files are uploaded. Your domain still shows a registrar parking page that cheerfully announces it's registered — and nothing else.
Nothing is broken. The domain just hasn't been told where to look yet. Here's how to change nameservers properly, plus the one step that quietly kills people's email for a day.
Quick Answer (as of July 2026): Log in to the registrar where you bought the domain — not your hosting panel — open the domain's nameserver settings, switch from the registrar's default option to custom nameservers, and enter the two addresses your host gave you. Save. Most domains resolve to the new host within 1-4 hours and finish worldwide inside 24-48 hours.
That's the whole job. Five minutes of clicking.
We handle 20-30 client issues every day, and this one still lands in the queue constantly — usually after something has already gone sideways. So this is the version we'd write out for you in a ticket: the exact steps, the honest timing, and the traps. On stacks like Hostaccent's, the failure we see is almost never the nameserver field itself. It's step 4.
What Are Nameservers, and Why Do They Matter?
Nameservers are the servers that tell the internet which company holds the authoritative DNS records for your domain. They don't host your website. They answer the question "who's in charge of this domain's records?"
Think of it in two layers. Your registrar holds the ownership record — the deed. The nameservers say which filing cabinet holds the actual instructions: which IP address serves the site, where email goes, which subdomains exist.
When someone types your domain, their resolver walks a chain: root servers → the TLD registry (for .com, that's Verisign) → your nameservers → the specific record it needs. Cloudflare's primer on what DNS actually does walks that path well, and the whole system is still governed by RFC 1035, the specification that defines the domain name system, published in 1987 and remarkably intact.
The practical consequence: change your nameservers, and you move your entire DNS zone to a new provider — every record, all at once. Not just the website. Everything.
That's the part people miss, and it's why this guide spends more time on email than on buttons.
Pro Tip: Nameservers and DNS records are not the same setting. If you only need to point one subdomain somewhere, or verify a domain with a TXT record, you want DNS records — leave the nameservers alone. Changing nameservers is the nuclear option: it hands the whole zone to a different provider.
If you're still assembling the pieces of a first site, our rundown of What Do You Need to Make a Website? Full 2026 List covers where this step fits in the sequence.
Where to Find Your Host's Nameservers (Do This First)
Your host's nameservers arrive in three predictable places, and you should confirm all three before touching anything.
The welcome email. Every host sends nameserver details when the account is provisioned. Search your inbox — including spam — for "nameserver" or "ns1".
The hosting control panel. In cPanel, they sit in the right-hand sidebar under General Information → Server Information; cPanel's own documentation confirms the layout. Plesk shows them under the domain's DNS settings.
The client area. Most hosts list them on the service details page in the billing portal.
They almost always look like this:
bashns1.yourhost.com ns2.yourhost.com
Some hosts assign account-specific pairs — ns1.something.hostdomain.com — and some issue four rather than two. Use exactly what you were given. Two is standard; there's no benefit to inventing a third.
Insider Insight: Copy and paste them. Never type them. Across the 4,000+ sites we've migrated, a hand-typed "ns2" where "ns1" belonged, or a trailing space the registrar silently accepted, is a genuinely common cause of a "why isn't this working after 24 hours" ticket. The field looks correct. It isn't.
How to Change Nameservers at Any Registrar: 5 Steps
Registrar dashboards differ in wording, but the path is functionally identical everywhere.
Step 1 — Log in to your registrar, not your host. This is the single biggest confusion in the tickets we see. The nameserver setting lives with whoever you bought the domain from. If your domain and hosting are with different companies, your host cannot make this change for you — they don't have access. If you're unsure who your registrar is, a WHOIS lookup on your domain names them.
Step 2 — Open the domain's management page. Look for "Domain Settings", "Manage", or "DNS". Select the specific domain if you own several.
Step 3 — Find the nameserver section. Labels vary: "Nameservers", "DNS Management", "Name Server Settings". You'll usually see a choice between the registrar's default (often labelled "Use our nameservers" or "Basic DNS") and custom nameservers. Select the custom option.
Step 4 — Replace, don't append. Delete every existing nameserver entry, then paste the new ones. Leaving one old nameserver in place is the mistake that produces the worst symptom of all: the site loads perfectly for you and fails for a third of your visitors, at random, because two providers are answering with different records. Hostaccent's support engineers see this exact pattern most often on domains that were pointed somewhere new in a hurry.
Step 5 — Save, then verify. Registrars sometimes require a confirmation email click before they update nameservers at the registry. Check your inbox. An unconfirmed change is not a change.
That's it. Now the waiting — and this is where the folklore starts.
How Long Nameserver Change Propagation Actually Takes
Nameserver change propagation is faster than the internet's favourite number suggests, and slower than your registrar's progress bar implies.
Here's the honest mechanic almost nobody explains. Your delegation lives at the TLD registry as an NS record with its own TTL — for .com, that's typically 172800 seconds (48 hours). Resolvers that already cached your old delegation will keep using it until that TTL expires. Resolvers that have never looked your domain up get the new answer immediately.
So the real timeline looks like this:
| Timeframe | What's happening | |---|---| | 0-30 minutes | Registry updated; fresh resolvers see the new nameservers | | 1-4 hours | Most consumer ISPs have refreshed; your site loads for the majority | | 24-48 hours | Cached delegations everywhere have expired; change is complete |
Meanwhile, your individual records (A, MX, CNAME) follow your zone's TTL — commonly 86400 seconds (24 hours) by default, or 300 seconds if the zone was tuned before a migration. Two different clocks. That's why a site can resolve in twenty minutes while email still bounces the next morning.
The 60-Second Nameserver Check — run this before you panic:
- Query the registry directly, not your browser:
dig NS yourdomain.com +trace(ornslookup -type=ns yourdomain.com 8.8.8.8on Windows). If the new nameservers appear, the change worked. - Flush your own resolver — your router and OS both cache. Test on mobile data as a second opinion.
- Query one record specifically:
dig A yourdomain.com @ns1.yourhost.com. If the new nameserver answers correctly, everything else is just cache expiry.
If step 1 returns nothing at all, you're looking at a different problem — our guide to Fix dns_probe_finished_nxdomain Error Fast (2026 Guide) covers the NXDOMAIN cases, including the DNSSEC trap below.
Pro Tip: Don't wait for propagation to install your SSL. Once the new nameservers resolve for the validating authority, your host issues an SSL certificate automatically — usually within minutes. If validation fails, it's almost always because the A record points somewhere the old zone still controls.
Custom Nameservers: When You Actually Need Them
Honest answer: most people never do.
Custom nameservers — sometimes called vanity nameservers — let you use ns1.yourdomain.com instead of your host's branded pair. They require glue records registered at the TLD registry, mapping those hostnames to IP addresses, because otherwise you've created a lookup loop: to find yourdomain.com's nameserver, the resolver needs to look up yourdomain.com.
They make sense in exactly two situations. You're a reseller and your clients shouldn't see whose infrastructure they're on. Or you're a agency running white-label hosting under your own brand.
For a single business site, they add a failure point and buy you nothing measurable. Skip them.
If you're weighing extensions before any of this matters, .com vs .net vs .io: Which Domain Extension Wins 2026 is worth ten minutes.
Common Nameserver Mistakes We See in the Ticket Queue
Email dies the moment the site comes up. This is the big one. MX records do not travel with your domain — they live in the DNS zone you just abandoned. If your mail runs through Google Workspace, Microsoft 365, or anything that isn't your new host, you must recreate those MX records in the new zone before you update nameservers. Write them down first. Our walkthrough on How to Create Email With Own Domain (2026 Guide) shows exactly which records to copy.
Changing DNS at the host instead of the registrar. Editing an A record in cPanel does nothing if the domain still delegates to a different provider's nameservers. You're editing a zone nobody is reading.
DNSSEC left enabled at the old provider. If DNSSEC was on and you move nameservers without disabling it first, resolvers reject the new answers as forged. The symptom is a hard NXDOMAIN that no amount of waiting fixes. Turn DNSSEC off at the registrar, change nameservers, re-enable afterwards.
Assuming files came along. Nameservers move DNS. They do not move your website. Upload your site to the new host first, then point the domain — otherwise you've swapped a parking page for a 404.
From the Ticket Queue: Across our monthly support volume, WordPress issues account for roughly 30%, brute-force and malware 25%, Linux server issues 25%, and SSL problems 20% — and a meaningful slice of that SSL bucket traces straight back to a nameserver change made before the records were ready. First-party data from our own queue.
For a broader pre-purchase checklist, Domain & Hosting Buying Guide: What to Check First is the companion piece to this one.
Ready to Point Your Domain at a Host That Answers?
Quick recap: change nameservers at the registrar, replace rather than append, copy your MX records before you switch, disable DNSSEC first, and give it 24-48 hours before you assume anything is wrong.
starting If you'd rather not juggle two providers at all, keeping the domain and the hosting in one account removes this entire step — the nameservers are pre-filled and the zone arrives ready. Hostaccent has been trading since 2012 and UK-incorporated since 2018, with 10,000+ websites launched, 15 datacenter locations, a 99.9% uptime guarantee and a 30-day money-back guarantee. You can register your domain from $13.99/yr for a .com (renewing at the same $13.99/yr — no bait pricing) and pair it with a Linux shared hosting plan starting from $1.99 month renewal $1.99 month. Honest limitation: shared hosting isn't the right home for a high-traffic store or a custom stack — that's a VPS conversation. Also worth reading before you decide: Free Domain With Hosting: Costs, Terms & Buyer Checklist.
Frequently Asked Questions About Changing Nameservers
How to change nameservers when your registrar and host are different companies?
Make the change at the registrar only. Your host cannot access the setting — it lives with whoever sold you the domain. Get the two nameserver addresses from your host's welcome email or control panel, then paste them into the registrar's custom nameservers field and save.
How long does it take for nameservers to update?
Most domains resolve to the new host within 1-4 hours. Full completion takes 24-48 hours, because the .com registry publishes your delegation with a 48-hour TTL and cached resolvers honour it. Query with dig NS yourdomain.com +trace to confirm the registry itself has updated.
Will changing nameservers break my email?
It will, unless you prepare. MX records live in the DNS zone you're leaving, and they don't follow the domain. Export or screenshot every MX, TXT and CNAME record from the old provider, recreate them at the new one, and only then update nameservers. This is the most common failure we see.
Can I change nameservers back if something goes wrong?
Yes. Nameserver changes are fully reversible — paste the old values back at the registrar and save. Expect the same 24-48 hour settling period on the way back, though, since the reversal is subject to the identical TTL rules. Nothing is deleted by switching.
Why are my nameservers not updating after 24 hours?
Three usual culprits: the registrar sent a confirmation email you never clicked, an old nameserver was left alongside the new ones, or DNSSEC is still active at the previous provider. Check the registry directly rather than trusting your browser — local and router caches lie convincingly.
Do I need custom nameservers for my domain?
Almost certainly not. Custom nameservers require glue records at the TLD registry and only benefit resellers or agencies wanting white-label branding. For a single site, they add complexity with no performance or reliability gain. Hostaccent's shared and reseller plans support them if you genuinely need them.
Discussion
Have a question or tip about this topic? Share it below — your comment will appear after review.