Edward Lewis wrote:
I'm not sure who, but apparently someone wrote this to some mailing list at some time in the past.
> The reason why I got interested was because section 8.2 of > draft-ietf-dnsop-ipv6-dns-issues-08.txt (see below) shows that the > application should be able to be aware of the TTL of the records, > easily, so that it could discard expired records from the memory if > it's built around in such a way that it would be feasible to do so.
Please recall that the purpose of the TTL is for cache coherency, not a statement on the quality nor timeliness of the data in DNS.
I would argue that if an application is using the results of a previous DNS lookup which it has stored in memory, then that is "caching" by any meaningful definition of the term. And if an app is caching, we should provide a way for the app to do so in a coherent manner. This implies making the TTL visible. Whether this is in getaddrinfo() or some other API, I'm not qualified to comment.
Like others, I've had problems with apps that "lock on" to a particular IP address. Particularly in dynamically load-balanced scenarios.
- Kevin
. dnsop resources:_____________________________________________________ web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
