DNS connects a domain name to services such as your website and email. After a DNS change, some networks may still use previously cached information until its time to live (TTL) expires.
What affects the timing?
- The TTL on the old DNS record.
- Whether you changed a record or changed the domain's authoritative nameservers.
- Cached answers, including earlier "not found" answers, at the resolver your device uses.
- Whether the new DNS configuration is correct.
Different people can see the change at different times. A nameserver change can also involve registrar and registry processing. There is no single propagation time that applies to every change.
What you can check
- Confirm which provider manages the domain's authoritative DNS. A domain registered through one company can use DNS hosted somewhere else.
- Check that the intended records were changed at that provider, including mail records when moving email.
- Try the site from another network, such as cellular data.
- If only your device sees the old result, try clearing its DNS cache.
Refreshing a page repeatedly does not force other networks to discard their DNS caches. Lowering a TTL after a change also does not shorten the lifetime of an answer already cached under the old TTL.
Do not change nameservers just to change a website address unless the migration plan requires it. If DNS is managed in Cloudflare or another service, cPanel DNS changes may not affect the public records.
Need help? Open a support ticket. Include the affected domain and the exact error message, but do not include your password.
