4 ms·
And this folks is one of the reasons you don't use a 1 minute TTL on your DNS responses...
by londons_explore 5y ago
And this folks is one of the reasons you don't use a 1 minute TTL on your DNS responses...
- Mo3 5y agoshamefully opens domain registrar and changes TTL
- Maxburn 5y ago15 min?
- belorn 5y agoI would recommend an hour for almost everything except where very fast updates is expected, in which case 5m is my lowest number (I work at a registrar).
- slenk 5y agoObviously registrars allow 1m - is there a reason not too besides extra load on DNS servers?
- remram 5y agoIf the DNS server is out for more than 1 minute you'll get an outage. You also increase latency by preventing anybody from caching the response for more than 1 minute.
- teddyh 5y agoThere are rumors of DNS resolvers deciding that some TTLs are “too low” to be valid, and applying their own default TTL value instead, thereby negating any benefit a low TTL would have had.
- londons_explore 5y agoI use 24 hours on anything I'm not planning on making changes to. High TTL is a better experience for customers because they'll probably have it in local-ish caches even if there is internet routing disruption. And 10 mins on anything I'm about to make changes to. That means if I accidentally make the wrong change, the 'blast radius' is minimized. Obviously, when changing 24h down to 10 mins, keep a close eye on DNS server load, packet loss on links close to it, etc. If in doubt, raise and lower ttl's slowly.