How to change nameservers: step-by-step guide for any registrar

To change your nameservers, go to your registrar's dashboard, find the domain settings, locate the nameserver section, and replace the current values with the new ones. Propagation takes between 1 hour and 48 hours, with 2 to 4 hours being typical. The most common mistake: changing nameservers before configuring DNS records at the new provider, which takes your site and email offline until you fix it.

Why change nameservers?

Nameservers define which DNS provider has authority over your domain. There are four situations where you would change them:

Moving to Cloudflare is the most frequent reason (for the CDN, DDoS protection, and faster DNS. Following a hosting provider's setup instructions is the second most common case (Shopify, Squarespace, and WP Engine all ask you to point NS at their infrastructure). Consolidating DNS management to a specialist provider like AWS Route 53 is typical for larger infrastructures. And finally, recovering a domain whose nameservers were changed without authorization) a signal of compromise that Domain Sentinel can alert you to automatically.

Before you start: configure DNS records at the new provider first

This is the step that causes outages. The correct sequence:

1. Create an account at the new DNS provider (Cloudflare, Route 53, your new host...).
2. Add the domain and manually recreate all existing DNS records, copy them from your current DNS interface before touching anything.
3. Only after all records are in place: change the nameservers at your registrar.

Do not change nameservers if you cannot access your current DNS interface to export the records first. The records that are most often forgotten: MX records (your email disappears silently if these are missing), TXT records for SPF/DKIM, and any CNAME records for SaaS services like Mailchimp, Intercom, or HubSpot.

If your MX records disappear and no one notices for 48 hours, emails sent to your domain during that window are gone, they are not delivered later once you fix the records.

How to change nameservers: by registrar

Namecheap

1. Log in to Namecheap.
2. Go to Domain List and click "Manage" next to the domain.
3. Find the "Nameservers" section on the domain management page.
4. Change the dropdown from "Namecheap BasicDNS" (or whatever is currently selected) to "Custom DNS".
5. Enter the nameserver values (e.g., ns1.cloudflare.com and ns2.cloudflare.com).
6. Click the green checkmark to save.

Effect: typically within 1 hour, sometimes almost immediately.

GoDaddy

1. Log in to GoDaddy.
2. Go to My Products > Domains and click on the domain.
3. Scroll to the "Additional Settings" section and click "Manage DNS".
4. Under "Nameservers", click "Change".
5. Select "Enter my own nameservers (advanced)".
6. Enter the nameserver values. Delete the empty rows, or fill them all if your provider gives you more than two.
7. Save.

GoDaddy has a reputation for slower propagation of its own changes, expect up to 48 hours in the worst case, though 12–24 hours is more common.

OVH / OVHcloud

1. Log in to the OVH Manager.
2. Go to Web Cloud > Domain names > [your domain] > DNS servers.
3. Click "Modify DNS servers".
4. Switch to custom nameservers and enter the values.
5. Confirm. OVH may ask you to confirm via email.

Propagation: 24–48 hours is typical for OVH changes to take full effect globally.

Cloudflare Registrar

If your domain is registered at Cloudflare, you cannot point it to external nameservers. Cloudflare keeps its own nameservers fixed for domains it registers. This is a hard limitation, not a configuration option. If you need to use a different DNS provider, you would need to transfer the domain out of Cloudflare first.

What you can do at Cloudflare Registrar: manage all DNS records directly within Cloudflare's DNS interface, which is separate from the nameserver question.

Generic procedure for other registrars

The path is nearly always the same across registrars: Domain Settings > DNS or Nameservers > Modify or Customize > enter NS1 and NS2 values. If your provider gives you NS3 or NS4, add those too. Look for "Custom nameservers", "Change DNS servers", or "Use my own nameservers" in the interface.

Case study: migrating to Cloudflare DNS

This is the most common use case, so here are the specific steps:

1. Create a free Cloudflare account at cloudflare.com.
2. Click "Add a site", enter your domain, and choose the free plan.
3. Cloudflare automatically scans your existing DNS records and imports them. Review the list carefully, not all records are always detected. Pay particular attention to MX records and any TXT records for email authentication (SPF, DKIM, DMARC).
4. Add any missing records manually before proceeding.
5. Cloudflare displays two nameservers to use (something like ada.ns.cloudflare.com and brett.ns.cloudflare.com, the names vary per account).
6. Go to your registrar and enter those two nameserver values using the instructions above.
7. Return to Cloudflare and click "Done, check nameservers". Cloudflare will verify the change once propagation completes.

The automatic import is convenient but not perfect, always do a manual review of the imported records before confirming.

Propagation time: how long to wait

Change type	Typical delay	Maximum
Namecheap nameservers	1–4 hours	24 hours
GoDaddy nameservers	12–24 hours	48 hours
OVH nameservers	24–48 hours	48 hours
Cloudflare DNS nameservers	2–6 hours	24 hours

For more detail on why propagation varies and how TTL affects it, see DNS propagation: how long it takes and why it varies.

How to verify the change was applied

Command line, dig:

dig NS example.com

The ANSWER SECTION should list your new nameservers. If it still shows the old ones, propagation is still in progress.

To query a specific resolver directly (bypassing your local cache):

dig NS example.com @1.1.1.1

RDAP lookup:

curl https://rdap.org/domain/example.com

Look for the nameservers field in the JSON response, it shows the authoritative nameservers as registered at the registry level.

Online propagation checkers: whatsmydns.net and dnschecker.org let you see nameserver values from 20+ global locations simultaneously. This is the fastest way to check whether propagation is complete in a specific region.

Domain Sentinel checks your nameservers every day and will alert you if they change unexpectedly, which is useful both for confirming legitimate changes and for catching unauthorized modifications.

Conclusion

Configure records first, change nameservers second, verify third. Plan your nameserver change outside of peak business hours, if something was missed in the record migration, you want to be available to fix it immediately. Once the change is live, set up monitoring to catch any unexpected nameserver modifications going forward.