Re:Poor Man's Global Traffic Manager
by zhfliz on Saturday August 20, 2022 @05:02PM
(#32535117)
isn't it usually the opposite, except for client applications that ignore the ttl they got from their recursive resolver as they don't want to bother with keeping track of ttls?
[ Parent
| on HN ]
When I ran a small web hosting provider, we had some clients (mostly bots, I think) hitting old IPs for months. We had kept the TTL below 5 minutes for a very long time before migration.
Also, older Java apps would cache DNS lookups forever, until you restarted the JVM. I remember arguing back and forth in email with a "vendor." They finally believed me and restarted their app server.
Re:Poor Man's Global Traffic Manager
by paranoidrobot on Sunday August 21, 2022 @02:34AM
(#32537899)
> Also, older Java apps would cache DNS lookups forever, until you restarted the JVM. I remember arguing back and forth in email with a "vendor." They finally believed me and restarted their app server.
New JVM-based apps do the same thing. I've had the same conversations with a "partner".
I figured, after all these years, the JVM would switch to a sane default for DNS caching. Sadly that is not the case...
that's what i meant.
the resolvers (which those apps talk to) are (afaik) generally rfc-conforming and respect ttl, though they may have lower max ttl values, allowing faster refreshes in some cases.
certain bad applications however just don't bother dealing with ttls at all and assume dns is static and never changes.