What is 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.
The short answer above covers the decision most buyers are making. The main entry for dns ttl best practice carries the complete definition, a usage note and the terms most often confused with it, so the two pages together answer both the quick question and the follow-ups.