“DNS propagation” is often used to describe several different problems: a cached answer, an edit made at the wrong provider, or an application redirect that sends visitors back to the old host. Identify which layer is responsible before making another change.
Recommended steps
- Check the domain's active nameservers. Make sure you edited the authoritative zone rather than a zone stored in an unused hosting control panel. A correct record at the wrong provider has no effect on public answers.
- Compare the website A and AAAA answers. If one still points to the old server, visitors may receive different destinations depending on their network. Review the www hostname independently from the bare domain.
- Record the old TTL and the time of the change. A resolver may legitimately continue returning an answer cached before the update. Test more than one resolver or network and compare the results rather than assuming a universal deadline.
- If DNS already returns the new destination, inspect browser caching, a CDN cache and application redirects. Check the site's configured canonical URL and any redirect rules on both the old and new hosting accounts.
- Confirm that the destination serves the intended document root and hostname. An apparently old website can also be a copied backup or a default virtual host on the correct server.
Send Support the exact hostname, current DNS answers, nameservers and a screenshot of the unexpected result if the cause is still unclear. Keep the previous records available for reference, and avoid deleting mail records during website troubleshooting.
