TTL belongs to a cached answer
TTL limits how long a response may be cached. Lowering it after a change does not erase responses already stored with the old TTL. Lower relevant values ahead of a planned migration, allow the previous TTL to elapse and restore sensible values afterwards.
A wrong answer is still a configuration issue
First check active nameservers and the new record. Waiting cannot fix an edit made at the old provider, a wrong IP or a stale AAAA alongside a new A. Compare resolvers without assuming a universal completion time.
Your practical checklist
- Lower TTL before migration.
- Allow previous caches to expire.
- Check the active zone.
- Keep the old service available temporarily.
A useful question
Does repeatedly saving help?
It does not clear existing caches. Check the configuration and allow valid cached responses to expire.
Ready to check your name? Start with the exact domain, then compare alternatives. Find a domain →
Sources & further reading
Original guide by chname.ch editorial. Archive dates organise this library; this guide was created and reviewed on . Provider and registry instructions take precedence when requirements change.