Two layers: delegation and records
Your registrar holds one setting that matters here: the nameservers. They tell the rest of the internet which DNS service is authoritative for your domain. An NS record does exactly that job: it indicates which server should be used for authoritative DNS. [5] The records themselves, such as the A record for your site and the MX records for your mail, live in a zone at that DNS service.
So there are two different jobs. Adding a record changes one answer at the current DNS host. Changing nameservers moves the whole question to a different host, which answers only with whatever records exist there. Namecheap's nameserver options make this concrete: Namecheap BasicDNS uses dns1.registrar-servers.com and dns2.registrar-servers.com; Web Hosting DNS uses dns1.namecheaphosting.com and dns2.namecheaphosting.com; Custom DNS points to anyone else, such as Cloudflare. [1]
| You want to | Change nameservers? | What to do |
|---|---|---|
| Verify a domain for an email platform | No | Add the TXT or CNAME at your current DNS host |
| Point the website at a new host | No | Edit the A, AAAA or CNAME record |
| Switch mail provider | No | Replace MX, update SPF, add DKIM |
| Move all DNS management to Cloudflare | Yes | Recreate every record at Cloudflare first [3] |
| Use Namecheap shared hosting's cPanel DNS | Yes, to Web Hosting DNS | Expect custom records to be overwritten [1] |
Why switching nameservers wipes your setup
Nothing is literally deleted at the old host, but nobody asks it anymore. Namecheap says that when you switch between custom nameservers and its default ones, host records will not be added to the new nameservers automatically, so you need to save the settings and recreate them after the switch. [1] Switching to Namecheap Web Hosting DNS is harsher: Namecheap says all custom DNS records will be overwritten with its hosting ones. [1]
Cloudflare offers to scan and import your existing records, but says the quick scan is not guaranteed to find all of them, and that missing records can cause visitors to see DNS_PROBE_FINISHED_NXDOMAIN errors. [3] Email records are the easiest to miss. A scan can only find names it knows to ask about, and DKIM records sit under selector names such as privateemail._domainkey that differ for every provider.
Copy these records before you switch
Open the DNS panel at your current host and copy every row, not just the ones you remember adding. Cloudflare reminds users that the exact mail records depend on your email provider and to confirm them with that provider. [3]
- A and AAAA records on @ and www, plus any ALIAS record. [2]
- CNAME records: www, platform verification, email DKIM and branded-link records.
- All MX records with their priorities.
- The SPF TXT on @ (one record only), and every other TXT on @ used for ownership verification.
- DKIM records under each selector._domainkey name, TXT or CNAME.
- The DMARC TXT on _dmarc.
- SRV and autodiscover records used by mail apps.
- Any URL Redirect records. These are a Namecheap feature, so at a host without an equivalent you will need another redirect method. [2]
- DNSSEC status at the registrar; Cloudflare says turn it off before replacing nameservers. [3]
Decision table: BasicDNS, PremiumDNS, Web Hosting DNS or Cloudflare
Pick based on where you want to edit records day to day, not on speed claims.
| Nameserver option | Where you edit records | What happens on switch | Fits |
|---|---|---|---|
| Namecheap BasicDNS | Namecheap Advanced DNS [2] | Records not carried over from a custom host [1] | Domain registered at Namecheap, simple site and mail |
| Namecheap PremiumDNS | Namecheap Advanced DNS [2] | Requires a PremiumDNS subscription attached to the domain [1] | Paid DNS add-on; works for domains at other registrars [1] |
| Namecheap Web Hosting DNS | The hosting account; Advanced DNS host records are only for BasicDNS, FreeDNS and PremiumDNS [2] | Custom records overwritten with hosting ones [1] | Site and mail both on Namecheap shared hosting |
| Custom DNS: Cloudflare | Cloudflare dashboard | Scan imports some records; review all [3] | Using Cloudflare proxy, rules or Email Routing |
| Custom DNS: another host | That host's panel | Records must be recreated there [1] | A platform that requires its own nameservers |
Worked example: moving example.com from BasicDNS to Cloudflare
Suppose example.com is on Namecheap BasicDNS with a website on a platform host, Namecheap Private Email, and a newsletter platform sending from email.example.com. The steps below keep mail flowing throughout.
- A day ahead, lower the TTL on the records you will touch; Namecheap's propagation article gives 300 seconds as an example and suggests waiting up to 30 minutes after updating records before changing nameservers. [4]
- Export or screenshot every row in Advanced DNS, including the Private Email MX, SPF, DKIM and DMARC records.
- Add the domain in Cloudflare, let it scan, then compare its list to your export line by line and add anything missing. [3]
- Turn off DNSSEC at Namecheap if it is on. [3]
- In Namecheap, open Domain List, Manage, Nameservers, choose Custom DNS and paste the two Cloudflare nameservers exactly. [1] [3]
- Wait up to 24 hours, then send a test email in and out and load the site from a mobile network. [1] [3]
- Re-enable DNSSEC through Cloudflare once the domain shows as active. [3]
Registry rules that can catch you out
Some country-code domains add their own nameserver rules, and Namecheap lists several. [1] Check these before planning a change on a deadline.
| Extension | Rule per Namecheap [1] |
|---|---|
| .CM | Changing nameservers 3 times within 28 days sets a registry lock |
| .IS | At least two different nameservers that do not resolve to the same IP |
| .MX | Maximum of 5 nameservers |
| .TO | Maximum of 4 nameservers |
| .CA | 2 to 6 nameservers, each with a unique IP |
| .FR | At least two nameservers; an SOA record should exist at the third-party host first |
Questions before you decide
A service told me to add a CNAME. Do I change nameservers?
No. Add the CNAME in the DNS panel of whichever service your nameservers point to. Change nameservers only when you are deliberately moving all DNS hosting to another provider.
Will my email break if I switch nameservers?
It will if the new DNS host lacks your MX, SPF, DKIM and DMARC records. Namecheap says records are not copied to new nameservers automatically, and Cloudflare says its import scan is not guaranteed to find every record.
How long does a nameserver change take?
Namecheap says it may take up to 24 hours, more in rare cases, for ISPs to update. Its propagation article says a nameserver change may take up to 24 to 48 hours. Cloudflare tells users to wait up to 24 hours.
Do I need to turn off DNSSEC first?
Cloudflare says yes: turn DNSSEC off at your registrar before replacing nameservers, because changing them with DNSSEC on can make the domain unreachable. Re-enable it at the new host once the domain is active.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Namecheap Knowledgebase: How to change DNS for a domain Accessed 30 Oct 2026
- Namecheap Knowledgebase: How do I set up host records for a domain? Accessed 30 Oct 2026
- Cloudflare DNS docs: Full setup Accessed 30 Oct 2026
- Namecheap Knowledgebase: DNS propagation explained Accessed 30 Oct 2026
- Cloudflare DNS docs: DNS record types Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.