Re: [Sks-devel] [PATCH] auto-refresh membership DNS

[Phil Pennock]

On 2009-03-23 at 10:17 +0000, Kim Minh Kaplan wrote:
> I think I have a much simpler solution for the problem at hand.  As I
> just mentionned the first fix is to not do any DNS resolution at client
> accept time.  This is trivial and already in my source tree.
> 
> Then to mitigate that membership IPs would be slow to come into the
> cache, do a round of DNS lookup on all currently unknown IPs at
> membership reload time.  Note that the loading of the membership and the
> DNS lookup round are done in separate steps.  I.e. the loading will
> always success (it's fast) while the lookup may be interrupted partway
> by a timeout in which case no harm is done and the cache still contains
> more IPs.
> 
> See any problem with that approach?

No.

So, the IP addresses will be held internally after all?  How long for?
When do they expire?  How is this different in effect on DNS being
cached unreasonably from using -membership_reload_interval with a value
similarly sized (0.5 or whatever)?

I'm tired and headed to bed, so perhaps I'm just missing what the
difference is.

-Phil