DNS Propagation: Why Your Website or Email Still Shows the Old Server
Website SSL Certificate Error? Common HTTPS Problems Explained
September 21, 2026Website Redirect Loop: How to Fix Too Many Redirects
September 21, 2026DNS propagation describes how cached answers age after an authoritative record changes. It does not repair a record placed in the wrong DNS zone. First confirm which nameservers are authoritative and what answer they give.
Before checking DNS propagation, locate the active provider
Check the nameservers at the registrar or through a reliable lookup. Edit records at that provider. Many migrations leave a copy of the zone at the old host, but edits there no longer affect the public domain. Export or record the live zone before making more changes.
Inspect the specific record
Website traffic may depend on A, AAAA or CNAME records, while incoming mail depends on MX. Check record name, value and TTL. Root and www hosts can have different answers. A correct website record does not mean email authentication or routing records survived a nameserver move.
DNS propagation and cached answers
Resolvers may use an old answer until its TTL expires. DNS propagation can therefore look different on two networks. A device or browser can also cache data. Compare the authoritative answer with public resolvers. If authoritative data is wrong, waiting for propagation will only spread the wrong result. Lowering TTL after a change does not erase answers already cached elsewhere.
Separate website and email tests
Open the site on another network and check the destination server. Send external mail and review the MX route separately. Do not change MX merely because a website still shows an old page. A working website does not prove the mailbox is receiving mail.
Verify services after DNS propagation
Once the authoritative answer is right, monitor public resolution and test HTTPS, inner pages, forms and inbound mail. Keep old hosting available until critical paths are confirmed. Record what changed and when so a later outage can be traced without guessing.
Related: migration support and post-DNS-change checklist.
Use the authoritative answer as your baseline
Cloudflare’s DNS troubleshooting documentation explains why a resolver can retain an old or empty answer. Compare like-for-like records and note which resolver produced each result. A screenshot saying that a domain has propagated is less useful than the hostname, record type, returned value and test time. Keep that evidence alongside the change record when escalating to the DNS or hosting provider.
