Not the one you're replying to, but I'd keep TTL high normally and lower it one TTL ahead of a planned change.
I would define high as "double time needed to fix a dns issue" and account for weekends
This is the way.
I would define high as "double time needed to fix a dns issue" and account for weekends