Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsChange a Namecheap domain’s nameservers from Domain List → Manage → Nameservers. Select BasicDNS, Web Hosting DNS, CustomDNS or PremiumDNS, enter the provider’s nameserver hostnames when required, and save with the green checkmark. Before saving, copy every website, email, verification and security record: switching nameservers changes the authoritative DNS service, and Namecheap does not copy host records to the new service automatically.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
What changing nameservers actually does
Nameservers tell the internet which DNS service is authoritative for your domain. That service publishes the records that map the domain to a website, mail servers, verification services, subdomains and security policies. Changing nameservers therefore changes where those records are managed; it is different from changing one A, CNAME or MX record inside the same DNS service.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
The change does not instantly erase the old zone. During propagation, some networks may still use cached answers from the previous nameservers while others query the new service. Once caches expire, visitors and mail systems rely on the records present at the new authoritative provider. If those records were not recreated, a website, email or verification process can stop working even though the domain registration itself remains active.
Choose the right Namecheap nameserver option
In Namecheap’s domain settings, the Nameservers menu offers four modes. Select the mode that matches the service that should operate authoritative DNS.
#1 Best Overall
| Option | Who operates authoritative DNS | Nameserver values | Where records are edited | Important effects |
|---|---|---|---|---|
| BasicDNS | Namecheap’s standard DNS service | dns1.registrar-servers.comdns2.registrar-servers.com |
Namecheap Advanced DNS remains available | Suitable when Namecheap should host the zone; Namecheap forwarding features are available |
| Web Hosting DNS | Namecheap shared hosting | dns1.namecheaphosting.comdns2.namecheaphosting.com |
Manage the hosting zone through the hosting environment, commonly cPanel | Replaces the current DNS configuration with the shared-hosting zone |
| CustomDNS | A third-party host, DNS provider, reseller plan, VPS, dedicated server or your own DNS infrastructure | Provider-supplied hostnames, such as ns1.example.tld and ns2.example.tld |
At that DNS provider or your own nameserver system; Namecheap Advanced DNS is not the editing location | Records must be created in the new zone; Namecheap’s URL forwarding, email forwarding and Dynamic DNS do not work with custom nameservers |
| PremiumDNS | Namecheap PremiumDNS, when the domain has an active PremiumDNS subscription | Use the values shown for the subscription | Namecheap Advanced DNS remains available | Requires the corresponding PremiumDNS service |
For CustomDNS, enter hostnames only in the Nameservers field. If the provider also gave you IP addresses, those addresses are used for the provider’s own setup or glue-record process; Namecheap’s CustomDNS field expects the nameserver names, not their IP addresses.
Prepare before changing anything
A short inventory prevents the most common outage: moving authority to an empty DNS zone. Complete these checks while the old DNS service is still working.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Identify the provider that should answer DNS queries after the change. A hosting company may provide nameservers even when the domain is registered at Namecheap.
- Export or copy every current record, including A and AAAA records, CNAMEs, MX records, TXT verification and SPF entries, DKIM and DMARC records, SRV records, redirects and records for subdomains.
- Record the current TTL values if you may need to roll back. TTL controls how long resolvers can cache an answer; it does not make the nameserver switch instantaneous.
- Confirm that the new DNS provider has a zone for the exact domain and that the required records are already present or ready to create.
- Check email dependencies separately. Website records can appear correct while missing MX, SPF, DKIM or DMARC records cause mail delivery or authentication failures.
- Make sure you can sign in to the new DNS provider or hosting control panel. After the switch, Namecheap may no longer be the place where records can be edited.
- If the domain is using Namecheap shared hosting, decide whether replacing the entire DNS configuration is acceptable. If an existing site, email service or custom record must remain, editing individual records instead may be safer.
Step-by-step: change nameservers in Namecheap
- Sign in to Namecheap. Use the account that manages the domain registration.
- Open Domain List. Select Domain List in the left sidebar.
- Open the domain’s management page. Click Manage beside the domain you want to update.
- Find Nameservers. In the Nameservers section, open the selector. Namecheap displays BasicDNS, Web Hosting DNS, CustomDNS and PremiumDNS as the available choices.
- Select the mode supplied by your provider. Choose BasicDNS when Namecheap should remain authoritative, Web Hosting DNS for a Namecheap shared-hosting plan, CustomDNS for nameservers supplied by another service, or PremiumDNS when the domain has that subscription.
- Enter CustomDNS hostnames when applicable. Add each provider-supplied hostname in the requested fields, using a form such as
ns1.example.tld. Do not replace those hostnames with IP addresses. - Save the change. Click the green checkmark. Wait for Namecheap to confirm the new nameserver setting before closing the page.
- Verify the destination zone. At the selected DNS provider, confirm that the website, mail, verification and security records match the inventory you made before switching.
Changing the selection without clicking the green checkmark does not submit the update. Conversely, saving the change does not migrate records, so the destination zone still needs its own complete record set.
Will changing nameservers delete my DNS records?
Namecheap warns that when you switch between custom nameservers and Namecheap’s defaults, host records are not added to the new nameservers automatically. The old provider’s records generally remain stored there, but they are no longer authoritative once resolvers begin using the new nameservers. The practical result is the same as an empty zone for any record you did not recreate: the domain can stop resolving, mail can be rejected, and third-party verification can fail.
For shared hosting, Namecheap describes the nameserver change as replacing the current DNS configuration. Treat that operation as a migration, not as a simple pointer. Copy records first, recreate them at the destination, then switch authority.
Where to edit records after the switch
Namecheap’s Advanced DNS editor is available only when the domain uses BasicDNS, FreeDNS or PremiumDNS. If the domain uses third-party nameservers or Namecheap hosting nameservers, the records must be managed at that DNS provider or in the hosting control panel, such as cPanel.
This distinction explains why an apparently correct record may be ignored: editing Namecheap Advanced DNS has no effect when another provider’s nameservers are authoritative. Always determine the active nameserver mode before troubleshooting a record.
How long propagation takes
Namecheap states that nameserver changes do not propagate instantly. Its general support guidance says local ISP caches may take up to 24 hours to update and, rarely, longer. Namecheap’s shared-hosting guidance gives a broader worldwide window of up to 24–48 hours.
Propagation is not a single global event. Different recursive resolvers refresh at different times, and a device may continue displaying an older answer until its resolver’s cache expires. During the transition, test from more than one network and avoid assuming that one successful or failed lookup represents every visitor.
What to monitor during propagation
- Resolve the domain from your normal connection and from a separate network, such as mobile data.
- Check the authoritative nameserver set and confirm that it matches the provider you selected.
- Test the bare domain, the
wwwhostname and important subdomains separately. - Send and receive a test email if mail is hosted on the domain.
- Watch certificate, payment, analytics and other integrations that depend on DNS verification.
Common problems and precise fixes
The website works for you but not for someone else
This usually reflects resolver caching during propagation. Compare results from multiple networks, verify that the new zone contains the correct web records, and allow the stated 24-hour general or 24–48-hour shared-hosting window to pass before treating the change as failed.
The website disappeared immediately
Check the new provider’s zone for the apex A or AAAA record and the required www CNAME or A record. If the records were left only at the old provider, recreate them in the new authoritative zone. Do not edit Namecheap Advanced DNS unless the domain is actually using BasicDNS, FreeDNS or PremiumDNS.
Email stopped arriving
Recreate the complete MX set and any supporting SPF, DKIM and DMARC TXT records at the new DNS provider. Check for typos, priority values and the exact host names required by the mail service. A website record alone is not enough to restore mail.
The provider gave IP addresses, but Namecheap rejects the entry
Use the provider’s nameserver hostnames in CustomDNS. IP addresses do not substitute for those hostnames in Namecheap’s nameserver fields. If you are building personal nameservers, handle the IP association through glue records as described below.
I cannot find the record editor in Namecheap
The domain is likely using third-party or Namecheap hosting nameservers. Edit the zone at the authoritative provider or in cPanel. The Namecheap editor is available only for BasicDNS, FreeDNS and PremiumDNS.
Forwarding stopped working
Namecheap’s API documentation warns that URL forwarding, email forwarding and Dynamic DNS do not work with custom nameservers. If those features are essential, use a compatible Namecheap DNS mode or implement equivalent services through the provider operating your custom zone.
The nameserver change was saved but nothing resolves after the full window
Confirm the spelling and order of every nameserver, check that the provider has created the zone, and verify that the domain’s delegation at Namecheap shows the intended values. If delegation is correct, inspect the destination zone for missing records or DNSSEC-related requirements configured by the provider. Contact the DNS provider when its nameserver service is not answering authoritatively.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.When changing nameservers is not the best approach
Point the domain with an A record
If you want to keep Namecheap (or another existing provider) authoritative for DNS, the provider may supply an IP address for an A record instead of nameservers. This lets you direct the website while retaining existing email and other records in the current zone. Namecheap documents this as an alternative to changing nameservers; follow the hosting provider’s exact record instructions, including any required www CNAME.
Use a hosts-file entry for a private preview
Editing your computer’s hosts file can preview a site on one device before public DNS changes. It changes only that device’s local resolution and does not alter the public DNS zone, so it is not a production replacement for an A record or nameserver change.
Recommended Free Tools
Register personal nameservers and glue records
Registering personal nameservers creates glue records that associate a nameserver hostname with an IP address. Registration alone does not delegate your domain to those nameservers. You must still select CustomDNS and enter the registered hostnames, and your nameserver servers must be running and authoritative for the domain.
The domain is registered elsewhere
If another registrar holds the domain, make the nameserver change in that registrar’s control panel. Namecheap can manage DNS only when the relevant delegation and registrar settings point there; contact the actual registrar for its procedure.
Using the API or automating the change
Namecheap’s API describes custom DNS as a comma-separated list of nameservers. Automation should therefore submit provider-supplied hostnames in the required list format and preserve the same safeguards as the dashboard procedure: save the current zone, verify the destination zone, and account for propagation. API access does not migrate records and does not remove the limitations of custom nameservers.
Quick Recap
A safe post-change checklist
- The Nameservers field shows the intended mode and every hostname exactly as supplied.
- The destination provider answers authoritatively for the domain.
- Apex and
wwwwebsite records resolve to the intended service. - All subdomains used by applications, stores or APIs resolve correctly.
- MX, SPF, DKIM and DMARC records are present and mail tests succeed.
- TXT, CNAME and other verification records pass checks in the services that use them.
- Forwarding and Dynamic DNS expectations match the selected nameserver mode.
- You retain a copy of the previous DNS zone in case a rollback is necessary.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →
