- Changing nameservers moves control of every DNS record to a new provider, so the full zone must be copied there before you switch.
- Nameservers are set at the registrar where the domain is registered, while the actual DNS records live at whichever provider runs those nameservers.
- Email is the most common casualty of a nameserver change, so recreate MX, SPF, DKIM and DMARC records before updating the delegation.
- If DNSSEC is enabled, remove or update the DS record at the registrar before changing nameservers, or the domain may stop resolving entirely.
- Keep the old DNS zone running for a few days after switching, because some resolvers will continue querying the previous nameservers until caches expire.
Check a name while you read
Nameservers decide who answers DNS questions for your domain. When you point a domain at new nameservers, you are handing control of every record (your website, your email, your verification codes) to a different DNS provider. The change itself takes about a minute at any registrar. The part that goes wrong is everything around it: records that were never copied, email that silently stops, or DNSSEC that breaks resolution entirely. This guide walks through the safe way to do it, whichever registrar you use.
What nameservers actually do
When someone types your domain, their resolver asks the registry for your TLD (for example, the .com registry) which nameservers are authoritative for the name. The registry replies with the NS records your registrar has on file, such as ns1.examplehost.com and ns2.examplehost.com. The resolver then asks those nameservers for the actual records: the A record for your website, the MX records for your mail, and so on.
That means there are two separate places involved:
- Your registrar, where you set which nameservers the domain uses. This is the delegation.
- Your DNS host, which runs those nameservers and stores your records. This might be the registrar itself, your web host, or a dedicated DNS provider.
Changing nameservers moves the second role. Editing an A or MX record does not require a nameserver change at all; it only requires editing the zone wherever it currently lives. Before you begin, run a nameserver lookup to see which provider is answering for your domain right now. Many people discover they were editing records at a provider that was not even live.
Before you change anything: copy your records
When you switch nameservers, the new provider starts with whatever zone you have built there. If it is empty, your site and email go dark for everyone whose resolver picks up the new delegation. So the most important step happens before you touch the registrar.
- Export or list every record at the current provider. Many DNS hosts offer a zone file export. If not, take screenshots or copy the records into a document.
- Cross-check with public lookups. Use the DNS lookup to confirm A, AAAA and CNAME records, the MX lookup for mail routing, and the TXT record lookup for SPF, DMARC and verification strings. Note that public tools can only see names you query, so check common subdomains like
www,mail,autodiscoverand any DKIM selectors you know about. - Recreate the zone at the new provider. Some providers will scan and import existing records automatically. Treat that import as a draft and compare it line by line against your list, because scans routinely miss subdomains they cannot guess.
- Check DNSSEC. If DNSSEC is enabled, the DS record at the registrar must match keys at the new provider. The safest path for most people is to disable DNSSEC (remove the DS record) at the registrar, wait for the old DS record to expire from caches, switch nameservers, then re-enable DNSSEC with the new provider's DS details.
How to change nameservers: the general steps
Every registrar's dashboard looks different, but the flow is nearly identical:
- Get the new nameserver hostnames from your new DNS host. They are usually two to four names, often shown on a setup or "point your domain" screen. Copy them exactly.
- Sign in to the registrar where the domain is registered, not where it is hosted. If you are unsure, a WHOIS lookup shows the registrar of record.
- Open the domain's management page and look for a section called Nameservers, DNS, or DNS settings.
- Choose the custom nameservers option.Registrars often label this "Use custom nameservers" or "Change nameservers" as opposed to their default DNS.
- Replace the existing entries with the new hostnames. Remove any old ones rather than mixing providers, unless you are deliberately running a multi-provider setup with synchronized zones.
- Save and confirm any email or two-factor prompt the registrar sends.
The registrar then submits the change to the registry. That submission is usually fast, but the old NS records may stay cached by resolvers for a while, which is covered in our guide to how long DNS propagation takes.
Where to find the setting at common registrar types
| Where your domain is registered | Where the setting usually lives | Watch out for |
|---|---|---|
| A large retail registrar | Domain list, then the domain, then DNS or Nameservers | A default "parked" DNS option that hides the custom field until you switch modes |
| A web host that also sells domains | Domains section of the hosting control panel | The host may only show nameservers, not let you edit the zone, if the domain points elsewhere |
| A website builder | Domain settings inside the builder | Some builders require you to transfer out or use their DNS to edit records freely |
| A reseller or agency account | The reseller's portal, or only through the agency | You may need the agency to make the change or give you direct access |
Verify the change
After saving, confirm the new delegation from the outside. Run the nameserver lookup again: once the registry is updated, it should list the new hostnames. Then check that the records you care about resolve to the right places with the DNS lookup and MX lookup. If you can, send a test email to and from the domain and load the site from a mobile connection, which uses a different resolver than your home or office network.
For the command line, dig NS example.com or nslookup -type=ns example.com shows what your local resolver currently believes. Adding +trace to dig follows the delegation from the root and shows what the registry is publishing, which bypasses most caching.
Common mistakes and how to avoid them
Changing nameservers when you only needed a record
If a website builder asks you to "connect your domain", check whether it offers an A or CNAME record option. Pointing a couple of records is often less disruptive than moving the whole zone, especially if your email is already set up elsewhere. See how to connect a domain to your website.
Forgetting email records
The most common casualty of a nameserver change is email. If MX, SPF, DKIM and DMARC records are not recreated, incoming mail can bounce and outgoing mail can land in spam. Our SPF and DMARC checker confirms the authentication records survived the move.
Typos in hostnames
A single wrong character, or a trailing dot entered where the registrar does not expect it, can cause the change to fail or delegate to a nonexistent server. Paste the values rather than typing them.
Domain locks and recent changes
A registrar lock does not normally prevent nameserver changes, but a registry lock (a higher-security service on some valuable domains) does, and requires a manual unlock process. If the save button fails, check for locks or an unverified contact email.
Quick checklist
- Confirm the current DNS host with a nameserver lookup
- Copy every record, including subdomains and TXT verification strings
- Build the full zone at the new provider before switching
- Handle DNSSEC before the switch, not after
- Update nameservers at the registrar, then verify from outside your network
- Keep the old zone in place for a few days in case resolvers still query it
FAQ
Will changing nameservers cause downtime?
Not if the new provider has a complete copy of your records before you switch. Resolvers move to the new nameservers gradually, so both providers should serve identical records during the transition.
How long do nameserver changes take?
The registrar usually updates the registry within minutes, but resolvers may keep the old NS records cached for up to a day or two, depending on the TTL the registry publishes for delegations.
What is the difference between nameservers and DNS records?
Nameservers are the servers that answer for your domain, set at the registrar. DNS records such as A, MX and TXT are the answers themselves, stored in the zone at whichever provider runs those nameservers.
Can I use nameservers from a different company than my registrar?
Yes. Registration and DNS hosting are independent. You can register a domain with one company and point its nameservers to a web host, a CDN or a dedicated DNS provider.