3 ms·
It will not, in fact, just work bc many clients cache old entries for a long time so you won’t be able to solve your load spreading problem quickly at least in
by dilyevsky 6y ago
It will not, in fact, just work bc many clients cache old entries for a long time so you won’t be able to solve your load spreading problem quickly at least in general case
- fulafel 6y agoIn browsers at least this should be a thing of the past - Chrome and Firefox both are documented to internally cache only for 1 minute. You might of course have non browser clients that don't respect DNS TTL which might be a problem if you're trying to introduce this into existing old systems.
- dilyevsky 6y agoAnd then chrome and ff will query your isp resolver than caches for a day just because - oops
- fulafel 6y agoThose ISP resolver caches do respect the DNS TTL per the spec, otherwise all kinds of stuff breaks. If you're concerned that this would still be an issue you could easily do some measurements. There's no incentive for ISPs to break the this given the "my internet is broken" UX and how tiny DNS traffic is.