Hosting Cost
Beginner Domains & DNS

How to Change Nameservers

Elena Novak, WordPress & Managed Editor
Elena Novak

WordPress & Managed Editor

Disclosure: Some links on this page are affiliate links — if you sign up through one, we may earn a commission at no extra cost to you. It never changes our ratings, rankings or verdicts: we don't sell hosting and take no pay-for-placement.

Who it's for

  • People switching hosts
  • DIY site builders
  • First-time domain owners

What Changing Nameservers Does

Nameservers are the DNS servers officially authorized to answer for a domain. Changing them at the registrar hands full control of that domain’s DNS zone to a new provider — usually a hosting company. Once changed, every record for that domain — A, CNAME, MX, TXT — must exist at the new nameservers. The old provider is no longer consulted at all.

Step-by-Step: How to Change Nameservers

  1. Get the new nameservers from the host. Most provide two or more, in the format ns1.hostname.com / ns2.hostname.com. Find these in the welcome email or hosting dashboard.
  2. Log in to the domain registrar — the company where the domain is registered, which may or may not be the same as the current or new host.
  3. Find the nameserver / DNS settings for the domain, usually under “Domain Management” or “DNS.”
  4. Replace the existing nameservers with the new host’s nameservers.
  5. Recreate any needed records at the new host before or immediately after the switch. This especially matters for MX records for email, and any custom subdomains.
  6. Save and wait for propagation — see DNS propagation for expected timing.
  7. Verify the domain resolves through the new nameservers using a DNS lookup tool.
a hand holding a phone photographing a laptop showing a domain management page with two nameserver input fields and a save button, bright ho

Timing: How Long a Nameserver Change Takes

Nameserver changes are among the slower DNS changes to fully propagate. The delegation record at the domain’s registry has its own TTL — often 24 to 48 hours — separate from any individual record’s TTL underneath. Expect the visible switch to complete within that window for the vast majority of visitors. The change is often visible from some locations within a couple of hours, though.

Record and Field Reference

Nameserver settings themselves are NS records at the registry level, pointing to the authoritative servers for the zone. Everything below that — the actual A, CNAME, and MX records — lives at whichever provider the nameservers point to. These records have to be set up there from scratch after a switch, since they do not carry over automatically from the old provider.

a tablet showing a colourful website mockup propped on a tidy desk beside a notebook and a pot plant, warm morning light

Troubleshooting Nameserver Changes

  • Site down after changing nameservers: the A record likely hasn’t been created yet at the new host. Nameserver changes only redirect where DNS is queried — they don’t copy any existing records.
  • Email stopped working: the most common nameserver-change mistake. MX records must be manually recreated at the new nameservers, since email routing depends entirely on them.
  • Old site still showing: either propagation hasn’t completed, or the registrar’s nameserver change didn’t actually save — recheck the registrar’s domain settings.
  • “Nameserver not responding” error: double-check for a typo in the nameserver hostnames — a single wrong character breaks resolution entirely.

Nameservers vs Individual Record Edits

Changing nameservers is not the only way to point a domain at a new host. Editing individual DNS records at the existing provider is the alternative. It’s worth choosing deliberately rather than defaulting to a nameserver change every time. A full nameserver switch makes sense when the new host should manage everything going forward, including email and any subdomains. Editing records directly makes more sense when other services are already configured at the current DNS provider and shouldn’t be disturbed by a wholesale handover.

a sunlit windowsill with a small potted herb and a ceramic mug, soft morning haze

Relationship to Hosting

Changing nameservers is the most common single step in pointing a domain to hosting and in switching web hosts entirely. It’s a full handover of DNS control, which is exactly why it needs a checklist rather than a single click. Every service depending on DNS — web, email, subdomains, verification records — has to be accounted for at the new provider before or right after the switch.

FAQ

Do I change nameservers at my domain registrar or my host? Always at the registrar — that’s where the domain’s official nameserver delegation lives, regardless of who’s providing the new hosting.

Will changing nameservers delete my current website? No — it only changes where DNS queries are answered. The old hosting account and files remain untouched until separately cancelled.

How do I know which nameservers to use? The new hosting provider supplies them directly, typically in the account setup email or hosting dashboard under domain or DNS settings.

Can I switch nameservers back if something goes wrong? Yes — simply re-enter the previous nameservers at the registrar, subject to the same propagation delay as any other nameserver change.