DNS TTL Best Practice
domains
TTL tuning balances agility against resolver load: short TTLs (60–300s) around migrations let you revert quickly, while stable records suit 3600 seconds or more. Always plan TTL changes ahead of the change itself.
Lower TTLs 24–48 hours before a cutover, then raise them again once the new records are stable.
Related topics
Frequently asked question
What is DNS TTL Best Practice?
TTL tuning balances agility against resolver load: short TTLs (60–300s) around migrations let you revert quickly, while stable records suit 3600 seconds or more. Always plan TTL changes ahead of the change itself. Lower TTLs 24–48 hours before a cutover, then raise them again once the new records are stable.
Read the full answer