DNS changes may appear quickly in some locations and take longer in others. The delay depends on previously cached answers, the record’s time-to-live (TTL), the type of change, and the systems involved.
What to expect
- Editing an existing DNS record: many lookups begin using the new value after their cached answers expire; that may take minutes or hours depending on the previous TTL.
- Changing nameservers: resolver and registry behavior can vary, so allow additional time for the change to be seen consistently.
- Moving a website: even when DNS is correct, browser, CDN, and application caches can show older content.
- Changing email routing: mail delivered during the transition may still follow cached MX records. Plan migrations carefully to avoid split delivery.
There is no single universal “propagation time” that applies to every DNS change.
How to check a change
- Confirm the intended record name, type, and value with your service provider.
- Ask your DNS administrator to verify the record was saved in the authoritative DNS zone, not an unused account.
- Use an independent DNS lookup tool if you are comfortable reading DNS results, or ask support to check multiple resolvers.
- Test the website or email service separately. A DNS answer can be correct even when the destination server is not working.
- Allow for old cached results to expire before repeatedly editing the same record.
Common problem: updating the wrong DNS provider
If your domain uses Cloudflare nameservers, records edited only in your registrar’s unused DNS zone normally will not affect public lookups. Always verify which nameservers are authoritative.
Still need help?
Send the domain, record name/type, old and new values, time of the change, and which service is affected. Redact sensitive account credentials.