This sounds a lot like prefetch in unbound, and the configuration option
gives some analysis on increased traffic.
prefetch: <yes or no>
If yes, message cache elements are prefetched before they expire
to keep the cache up to date. Default is no. Turning it on
gives about 10 percent more traffic and load on the machine, but
popular items do not expire from the cache.
Also, if the original TTL of the RR is less than STOP * HAMMER_TIME then
the cache entry, it cannot be used anymore and the resolver should
"Break it down".
Best regards,
Matthijs
On 07/02/2013 03:44 AM, John Levine wrote:
>> We would like to draw your attention to a new draft.
>
> It looks like it should work, assuming that your cache uses the
> existing logic to remember queries in progress so it doesn't hammer a
> record that's already in the process of being refetched.
>
> My main observation is that I have no idea what the tradeoffs are
> between the increased DNS traffic and faster responses to clients.
> Have you done simulations or live experiments?
>
> R's,
> John
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
