Namecheap Nameserver Options at a Glance
| Nameserver Type | Use Case | Change Time | Managed Where |
|---|---|---|---|
| Namecheap BasicDNS | Default — Namecheap hosting | Immediate | Namecheap Advanced DNS |
| Namecheap PremiumDNS | Higher uptime + DNSSEC | Immediate | Namecheap Advanced DNS (£3.65/yr ex-VAT) |
| Cloudflare | CDN, DDoS protection, proxy | Up to 48 hours to propagate | Cloudflare dashboard |
| Custom (WordPress host) | Pointing to SiteGround, WP Engine, Kinsta | Up to 48 hours to propagate | Your hosting provider |
| Google Workspace | Google-managed email via Gmail | Up to 48 hours to propagate | Google Admin Console |
PremiumDNS price ex-VAT. UK customers add 20% at checkout.
Verdict: Changing nameservers in Namecheap takes 2 minutes in the dashboard. The wait is DNS propagation — up to 48 hours globally, though most users see changes in 1–4 hours. This guide covers all four common scenarios: Cloudflare, WordPress hosting, Google Workspace, and troubleshooting propagation.
How to Change Nameservers on Namecheap — The Universal Steps
These steps apply regardless of where you are pointing your domain:
- Log in to Namecheap
- Click Domain List in the left menu
- Find your domain and click Manage
- On the Domain tab, find the NAMESERVERS section
- Click the dropdown — it will show “Namecheap BasicDNS”
- Select Custom DNS
- Enter the nameservers provided by your target service (1 per line)
- Click the green checkmark to save
Important: Once you switch to Custom DNS (Cloudflare, host, etc.), Namecheap’s DNS editor is disabled. All future DNS changes must be made at your new nameserver provider. If you switch back to Namecheap BasicDNS, your previous Namecheap DNS records are restored.
Scenario 1: Point Namecheap Domain to Cloudflare
Cloudflare is the most common reason to change Namecheap nameservers. It gives you: free CDN, DDoS protection, free SSL, and a very fast DNS editor.
Step 1 — Add your site to Cloudflare
- Go to cloudflare.com and create a free account
- Click Add a site
- Enter your domain name (e.g.
yourdomain.com) — do not include www - Choose the Free plan and click Continue
- Cloudflare scans your existing DNS and imports all records
- Review the imported records — check that A records, CNAME, MX, and TXT records all look correct
- Click Continue
Step 2 — Get your Cloudflare nameservers
Cloudflare will show you two nameservers, e.g.:
aria.ns.cloudflare.combob.ns.cloudflare.com
Every Cloudflare account gets a unique pair. Copy both nameservers exactly.
Step 3 — Enter nameservers in Namecheap
- Follow the universal steps above
- Paste both Cloudflare nameservers, one per field
- Save with the green checkmark
Return to Cloudflare and click Done, check nameservers. Cloudflare will send you an email when propagation is confirmed (usually 10 minutes to 4 hours).
Step 4 — Configure Cloudflare proxy settings
After propagation, in Cloudflare’s DNS editor you will see an orange cloud (proxied) or grey cloud (DNS only) next to each record:
- Orange cloud (proxied): Traffic routes through Cloudflare’s CDN. Hides your origin IP. Enables DDoS protection and cache.
- Grey cloud (DNS only): Cloudflare resolves DNS but does not proxy traffic. Use this for mail, FTP, and SSH records.
For WordPress: set your A record (root domain) and CNAME (www) to proxied (orange cloud). Set MX records to DNS only (grey cloud) — email does not route through Cloudflare’s proxy.
Scenario 2: Point to a WordPress Host (SiteGround, WP Engine, Kinsta, etc.)
When you move your WordPress site to a managed WordPress host, they give you nameservers to use. The process is identical to Cloudflare.
Where to find the nameservers
| Host | Where to find nameservers |
|---|---|
| SiteGround | Site Tools → Domain → Nameservers |
| WP Engine | User Portal → Domains → Add domain → Nameservers tab |
| Kinsta | MyKinsta → Sites → your site → Domains → DNS |
| Cloudways | Platform → Applications → Domain Management → Nameservers |
| EasyWP (Namecheap) | No nameserver change needed — domain stays on Namecheap BasicDNS |
EasyWP exception: If you are moving a Namecheap domain to Namecheap’s own EasyWP managed WordPress, you do not change nameservers. EasyWP works within the existing Namecheap DNS. Just point your A record to the EasyWP IP shown in the EasyWP dashboard.
Steps
- Copy the nameservers from your WordPress host (usually 2–4 nameservers)
- Log in to Namecheap → Domain List → Manage → Nameservers → Custom DNS
- Enter each nameserver on a separate line
- Save and wait for propagation (1–48 hours)
Your WordPress host will also provide the IP address for your site. You do not need to set A records yourself if you are using the host’s nameservers — they manage all DNS records for you.
Scenario 3: Set Up Google Workspace with Namecheap Domain
Google Workspace (Gmail for your domain, Google Drive, Meet) requires specific MX records pointing to Google’s mail servers. You have two options:
Option A — Stay on Namecheap DNS, add Google MX records
This is simpler and does not require changing nameservers. Keep Namecheap BasicDNS and add MX records manually:
- In Namecheap, go to Domain List → Manage → Advanced DNS
- Under Mail Settings, select Custom MX
- Delete any existing MX records
- Add these 5 Google MX records:
| Host | Mail server | Priority |
|---|---|---|
| @ | ASPMX.L.GOOGLE.COM | 1 |
| @ | ALT1.ASPMX.L.GOOGLE.COM | 5 |
| @ | ALT2.ASPMX.L.GOOGLE.COM | 5 |
| @ | ALT3.ASPMX.L.GOOGLE.COM | 10 |
| @ | ALT4.ASPMX.L.GOOGLE.COM | 10 |
- Also add the Google verification TXT record that Google Admin Console provides
- Click Save
Option B — Use Cloudflare nameservers and add MX records there
If you are already using Cloudflare for CDN, add the same Google MX records in Cloudflare’s DNS editor instead. Make sure MX records are set to DNS only (grey cloud) — never proxy MX records through Cloudflare.
SPF and DKIM records for Google Workspace
After setting MX records, add these records to prevent email landing in spam:
| Type | Host | Value |
|---|---|---|
| TXT | @ | v=spf1 include:_spf.google.com ~all |
| CNAME | google._domainkey | [from Google Admin Console → Apps → Gmail → Authenticate email → Generate DKIM key] |
| TXT | _dmarc | v=DMARC1; p=none; rua=mailto:youremail@yourdomain.com |
The DKIM CNAME value is unique to your account — generate it in Google Admin Console. Without SPF and DKIM, Google Workspace email will pass but may be flagged as spam by some recipients.
DNS Propagation — What It Is and How to Check It
When you change nameservers, your new settings do not instantly appear worldwide. DNS resolvers across the internet cache nameserver records for a period defined by the TTL (Time To Live) value. During propagation:
- Some users see your site on the old host
- Some users see your site on the new host
- Email may route to the old server
Typical propagation times:
| Change type | Typical time | Maximum |
|---|---|---|
| A record (IP address) | 5–30 minutes | Up to 4 hours |
| MX record (email routing) | 30 minutes–4 hours | Up to 24 hours |
| Nameserver change | 1–4 hours | Up to 48 hours |
| CNAME | 5–30 minutes | Up to 4 hours |
How to check propagation status
Use these free tools to see what DNS resolvers around the world are returning:
- whatsmydns.net — check A, MX, NS, CNAME records from 22+ global locations
- dnschecker.org — similar, shows propagation map
- Google Admin Toolbox (toolbox.googleapps.com/apps/checkmx/) — specifically for checking Google Workspace MX and SPF records
Enter your domain, select record type (NS for nameservers, A for your IP, MX for email), and click Check. Green ticks mean that location has the new record. Red X means it still has the old cached record.
How to speed up propagation
You cannot force other resolvers to flush their cache, but you can:
- Lower TTL before the change: 24 hours before switching nameservers, reduce your A record TTL to 300 seconds (5 minutes) in Namecheap Advanced DNS. Resolvers will then cache for only 5 minutes instead of the default 1800 seconds.
- Flush your own DNS cache: On Mac:
sudo dscacheutil -flushcache. On Windows:ipconfig /flushdns. This clears your own computer’s cache — you will see the new records immediately.
Common Nameserver Mistakes
| Mistake | Symptom | Fix |
|---|---|---|
| Trailing dot or space in nameserver | Domain resolves to nothing | Check for extra spaces/punctuation in Namecheap DNS fields — must be plain hostname only |
| Adding nameservers while keeping Namecheap BasicDNS selected | Changes do not save or have no effect | Must change the dropdown to “Custom DNS” before entering custom nameservers |
| Forgetting to add MX records at the new nameserver | Email stops working after switch | Before switching, export all existing DNS records and re-enter them at the new provider |
| Proxying MX records through Cloudflare | Email fails completely | MX records must be grey cloud (DNS only) in Cloudflare — never orange cloud |
Frequently Asked Questions
How long does it take to change nameservers on Namecheap?
The change in Namecheap’s dashboard takes about 2 minutes. Global DNS propagation for nameserver changes typically takes 1–4 hours and completes within 24 hours for 99% of users. The theoretical maximum is 48 hours, but this is rare in practice.
Will changing nameservers take my website offline?
During propagation, visitors may see either the old or new server depending on which DNS resolver they use. To minimise disruption: set up your site fully on the new host before changing nameservers, lower your TTL to 300 seconds 24 hours before the switch, and schedule the change for low-traffic hours.
Can I use Cloudflare nameservers and still have email at Namecheap?
Yes. Point your nameservers to Cloudflare, then in Cloudflare’s DNS editor add MX records pointing to your email provider (Namecheap Private Email, Google Workspace, etc.). Cloudflare does not host email — it just resolves DNS. Ensure MX records are set to grey cloud (DNS only) in Cloudflare.
What are the default Namecheap nameservers?
Namecheap BasicDNS nameservers are: dns1.registrar-servers.com and dns2.registrar-servers.com. PremiumDNS nameservers are: pdns1.registrar-servers.com and pdns2.registrar-servers.com. If you switch to a third-party provider and want to revert, set these in the Custom DNS field.
Do I need to change nameservers to use Namecheap’s own hosting?
No. If you register a domain and buy hosting with Namecheap, your domain is automatically pointed to Namecheap BasicDNS and your hosting IP is automatically configured. You only need to change nameservers if you are using a third-party hosting provider (Cloudflare, SiteGround, WP Engine, etc.).
