cache and ttl, resolvers and clients

[Robert Bowles]

Are there many pitfalls with various dns clients/resolvers honoring (or not
honoring) ttl?  What if the ttl values are on the order of 1-2 minutes?

Its easy enough to verify (I'm specifically interested in Solaris' nscd
honoring small ttls without having to turn caching off altoghether).

I have seen issues with the Java runtime maintaining its own DNS resolution
cache and it did not appear to honor ttl at all.  (And in fact would only hit
the Solaris resolver when the runtime was restarted.)

Any comments or observations welcome. 


-- 
Bob Bowles
rbowles at mediaone.net