Namecheap DNS Not Propagating? 6 Fixes That Work (2026)

By Alex Morgan | Last updated: May 2026

Affiliate disclosure: This page contains affiliate links. If you sign up through our links, we may earn a commission at no extra cost to you. Full disclosure here.

Short answer: If your Namecheap DNS change isn’t showing up, the most likely cause isn’t slow propagation — it’s a configuration error you can fix in 2 minutes. Work through the 6 fixes below in order. Fix 1 resolves approximately 70% of cases.

Fix 1: Verify the Record Was Actually Saved Correctly (Resolves ~70% of Cases)

Before assuming propagation is slow, confirm the record is correct in Namecheap’s DNS panel. This is the most common cause of “DNS not propagating” complaints — the record either wasn’t saved, has a typo, or is the wrong record type.

The record type is correct. An A record must point to an IP address (e.g. 185.230.63.186). A CNAME record must point to a hostname (e.g. example.com), not an IP. Mixing these up is the most common error.
The Host field is correct. For a root domain, use @. For www, use www. For a subdomain like blog.yourdomain.com, use blog only — not the full domain.
You clicked the green checkmark/Save button. Namecheap’s DNS editor doesn’t auto-save. If you edited a value and navigated away without saving, the change wasn’t applied.
No conflicting records exist. Two A records with the same Host value will conflict. Check for duplicates.

If everything looks correct here, move to Fix 2.

Fix 2: Flush Your Local DNS Cache

Your computer caches DNS results so it doesn’t have to look them up on every request. If you updated a DNS record, your computer may still be serving the old cached version even when the new record has propagated globally.

Windows:

Open Command Prompt as Administrator, then run: ipconfig /flushdns

Mac:

Open Terminal, then run: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Linux (Ubuntu/Debian with systemd):

Open Terminal, then run: sudo systemd-resolve --flush-caches

After flushing, open a new browser tab and try your domain again. If it’s still showing the old result, move to Fix 3.

Fix 3: Use an External DNS Checker to See Real Global Status

Your ISP may be caching old DNS records even after the new record has propagated to most of the world. Use an external checker to see what the record actually looks like from multiple global locations:

dnschecker.org — shows your record from 30+ locations worldwide
whatsmydns.net — similar, clean interface
mxtoolbox.com — better for MX and mail-related records

Enter your domain and select the record type (A, CNAME, MX, etc.) you changed. If the checker shows the new record value from most locations but your browser still shows the old site, the problem is local DNS caching — Fix 2 should have resolved it. If the checker shows the old value from most locations, propagation is genuinely still in progress.

Important context: Namecheap sets the default TTL (Time to Live) for new records at 30 minutes. This means old cached values can persist for up to 30 minutes after a change — but no longer. If it’s been more than 60 minutes and a third-party checker still shows the old value, re-check Fix 1.

Fix 4: Check Your Nameservers Are Set Correctly

This fix applies if you recently changed where your domain is hosted or moved to a new DNS provider. If the domain’s nameservers aren’t pointing to the right place, your DNS records simply won’t be read — regardless of whether they’re configured correctly.

How to verify your nameservers:

Log in to Namecheap → Domain List → Manage.
Under Nameservers, confirm what’s set: either “Namecheap BasicDNS” or specific custom nameservers (e.g. ns1.yourhost.com).
If you added DNS records in Namecheap’s Advanced DNS panel, the nameservers must be set to Namecheap’s servers (BasicDNS). If you’re using custom nameservers (e.g. pointing to Cloudflare or your host), the DNS records need to be set in THAT provider’s panel — not in Namecheap.

The most common confusion: editing records in Namecheap’s Advanced DNS while the nameservers point somewhere else. Namecheap’s records will be ignored.

Fix 5: Reduce TTL Before Your Next Change

This is a proactive fix for future changes, not for right now. Before making a DNS change:

At least 30 minutes before the change, set the TTL on the record you’re about to modify to its minimum value (300 seconds / 5 minutes).
Wait 30 minutes for the reduced TTL to propagate.
Make your DNS change. The old cached version will now expire across the internet within 5 minutes instead of 30.
After the change is stable, restore the TTL to 1800 seconds (30 minutes) or higher.

In Namecheap’s Advanced DNS, TTL is set per record when editing. The minimum allowed is 60 seconds, though 300 seconds (5 minutes) is a practical floor.

Fix 6: Nameserver Changes Genuinely Take Longer — Wait Them Out

If you changed the nameservers for your domain (not just individual DNS records), this takes significantly longer than a record change. Here’s the realistic timeline:

A record or CNAME change: 30–60 minutes in most cases (Namecheap’s TTL default is 30 minutes)
MX record change: 30–60 minutes, occasionally up to a few hours
Nameserver change: 4–24 hours in practice; up to 48 hours in edge cases
.co.uk and country-code TLDs: Up to 48 hours, occasionally longer

Namecheap’s documentation says “up to 48 hours.” In reality, nameserver changes typically complete within 4–12 hours for .com, .net, and .org domains. If it’s been more than 24 hours and dnschecker.org still shows inconsistent results globally, contact Namecheap support via live chat — there may be an issue at the registry level.

When to Contact Namecheap Support

Contact support if:

It’s been more than 48 hours since a nameserver change and dnschecker.org still shows old nameservers from most locations.
You’ve verified Fix 1 (record is correct and saved) but dnschecker.org shows no record at all — even from Namecheap’s own servers.
You see “NXDOMAIN” errors from multiple global locations — this suggests the domain itself may not be resolving.

Namecheap live chat is available 24/7 and typically responds within 2 minutes on weekdays. Have your domain name and a screenshot of dnschecker.org results ready when you contact them. See our Namecheap live chat review for response time data.

Quick Diagnostic Checklist

[ ] DNS record type, host value, and target are all correct in Advanced DNS
[ ] You clicked Save after making changes
[ ] No duplicate/conflicting records for the same Host
[ ] Local DNS cache has been flushed
[ ] dnschecker.org shows the new value from most global locations
[ ] Nameservers are set to the provider where you added the records
[ ] If nameserver change: at least 12 hours have passed

Need reliable DNS for a new domain? Register at Namecheap — includes free DNS hosting →

Frequently Asked Questions

Why is my Namecheap DNS not propagating after 24 hours?

If it’s been more than 24 hours and a DNS checker still shows the old record from most locations, the most likely cause is an incorrect record configuration — wrong record type, wrong host value, or the record wasn’t saved. Re-check Fix 1. If the record is definitely correct and saved, contact Namecheap support.

How long does Namecheap DNS propagation take?

For A records and CNAME changes: typically 30–60 minutes (Namecheap’s default TTL is 30 minutes). For nameserver changes: 4–24 hours for .com, .net, .org. Up to 48 hours for country-code TLDs. See our full propagation time guide.

My DNS records look correct but my site isn’t loading — why?

The most common cause after confirming the DNS record is correct: local DNS cache on your computer or browser. Flush your DNS cache (Fix 2 above) and try in an incognito window or on a different device.

How do I check if my Namecheap DNS has propagated?

Use dnschecker.org or whatsmydns.net. Enter your domain, select the record type (A for most websites, MX for email), and see results from 30+ global locations. If most locations show the new value, propagation is complete — the issue is local caching.

Can I speed up Namecheap DNS propagation?

For future changes: reduce TTL to 300 seconds (5 minutes) at least 30 minutes before making any change. For changes already made: flush your local DNS cache and check with an external tool. You cannot force ISPs worldwide to update their cache faster than the TTL dictates.

Information verified May 2026. DNS troubleshooting steps apply to Namecheap’s current DNS management interface.