There is no single timer for every DNS change. Authoritative records, cached answers and nameserver delegation can update on different schedules. Check what is being returned and where, rather than treating every problem as something that will automatically disappear after a fixed wait.
Before you begin
- Record the change and time.
- Check authoritative answers before waiting.
- Separate DNS from hosting and HTTPS errors.
Understand what changed
A website record edit at the existing DNS host is different from a nameserver move. A record edit changes an answer; a delegation move changes which service supplies answers. Record the type of change and the time it was made before troubleshooting.
For an ordinary record update, check the authoritative server first. If it still serves the old value, waiting for other caches will not fix the underlying configuration. Confirm you edited the active zone and saved the intended value.
Compare authoritative and cached answers
Recursive resolvers can retain an earlier answer for its cache lifetime. This can explain why a phone on mobile data and a laptop on office Wi-Fi behave differently. The answer each network sees is more informative than repeatedly refreshing one browser.
Browser, operating-system and application caches can add another layer of old behaviour. However, an error can also be caused by hosting or HTTPS after DNS is correct. Keep those possibilities separate rather than making repeated DNS edits without evidence.
Use a checking order
Write down what each check shows so a support conversation has something concrete to work with.
- Confirm the current authoritative nameservers.
- Check the requested record at the active DNS host.
- Compare a cached answer from the network experiencing the problem.
- Check both root and www if the website uses them.
- Test the hosting response and certificate once the address resolves.
Avoid restarting the change repeatedly
Switching values back and forth can leave different networks with several generations of answers. If the authoritative configuration is correct, allow the relevant caches to expire and keep monitoring the affected service. If it is wrong, correct the specific error first.
A new registration can also need service setup before it shows a website. Domain renewal pricing and DNS timing are separate matters: paying for a longer registration does not make caches refresh faster. Keep a clear change log alongside your domain record.
Prepared with AI-assisted drafting and illustration, then checked against the linked sources and NameUK’s current service. The artwork is conceptual; setup values must come from your own provider.
Further readingCloudflare: time to live ↗Cloudflare: how DNS works ↗NameUK registration and renewal prices ↗Extension rules and provider processes can change. Check the current registrar instructions before a registration, transfer or renewal.
Low-cost registration. Affordable UK renewals.
Register .co.uk for £9.99 for one year, with annual renewal currently £9.99. Or choose a new three-year .co.uk registration for £25.99. Check the selected name and term before payment. Future renewal prices can change.