Duane/Evan/Mukund/All,
What do feel is the consensus on lowering the value to 1 second ?
>From the previous suggested text:
Resolvers MUST cache resolution failures for at least 1 second.
The initial duration SHOULD be configurable by the operator. A
longer cache duration for resolution failures will reduce the
processing burden from repeated queries, but will also lengthen
the recovery period from transitory issues.
It does sound like this paragraph works better.
Resolvers SHOULD employ an exponential or linear backoff algorithm to
increase
the amount of time for subsequent resolution failures. For example,
the initial time for negatively caching a resolution failure is set
to 5 seconds. The time is increased after each retry that results in
another resolution failure. Consistent with [RFC2308], resolution
failures MUST NOT be cached for longer than 5 minutes.
May we get some feedback on this?
thanks
tim
On Mon, Jul 24, 2023 at 11:41 AM Evan Hunt <[email protected]> wrote:
> On Mon, Jul 24, 2023 at 06:26:46PM +0000, Wessels, Duane wrote:
> > It was not our intention that “2” would be the only possible exponent in
> > the backoff algorithm. Would this slightly revised text be more
> > agreeable?
> >
> > Resolvers SHOULD employ an exponential or linear backoff algorithm to
> > increase the amount of time for subsequent resolution failures. For
> > example, the initial time for negatively caching a resolution failure
> > is set to 5 seconds. The time is increased after each retry that
> > results in another resolution failure. Consistent with [RFC2308],
> > resolution failures MUST NOT be cached for longer than 5 minutes.
>
> That's definitely an improvement, yes.
>
> --
> Evan Hunt -- [email protected]
> Internet Systems Consortium, Inc.
>
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
