Why does a DNS change take time? TTL and caches

What TTL means

TTL specifies how long a DNS record may be cached. For example, 3600 seconds means one hour. Users can temporarily receive different answers because their DNS services fetched the information at different times.

Lowering TTL does not remove old answers already in caches. For a planned destination change, lower it in advance when the DNS provider permits. Nameserver changes involve separate caches.

Check the change in order

1. Confirm the domain's active nameservers and that you edited their DNS management service.
2. Check the saved record type, name and value. For example, www and the root domain are different records.
3. Compare a public DNS lookup with the value expected in the dashboard. On Windows, nslookup -type=A example.com shows the A answer through your configured DNS service. Replace the example with your own domain.
4. Try the website from another network. If answers differ, record both results and the time.
5. Allow the previous TTL to pass and check again. Avoid repeatedly changing the record during investigation.

Separate DNS from website caching

If DNS already returns the right destination but the website content is old, check browser, application and any CDN caches. Clearing the browser cache does not refresh DNS answers for every internet provider.

When to ask for help

If the answer remains wrong after waiting, send support the domain, changed record type, change time and lookup result. Do not post secret TXT verification values on a public forum.