A safe TTL change sequence
Lower the TTL before a planned move while the old service is still healthy. Make the record change, verify answers and application health from more than one network, then restore a sensible TTL after the new service is stable.
Why “propagation” is not a single timer
Resolvers refresh on their own schedules. Users may see different answers until older cached responses expire, and negative answers can also be cached. Record the previous values before a migration so a rollback is possible.
Check real data now
Use the live IIPP tool to inspect the domain or IP address you are working with.
DNS Record Lookup →