[nsd-users] Patch: {max,min}-{refresh,retry}-time

[Anand Buddhdev]

On 17/06/16 21:27, Daisuke HIGASHI wrote:

I would like to echo Daisuke's comment. If you introduce this new
feature, don't also activate it automatically, because it will catch
users by surprise. Remember what happened with RRL? If RRL is compiled
in, then NSD also applies some hard-coded defaults, and a user has to
explicitly turn off RRL. So a packager who wants to ship NSD with RRL
compiled it, but not on by default has to use the option:

--enable-ratelimit-default-is-off

New features, especially those that change how the software departs from
a standard, should default to off.

Regards,
Anand

> Hi,
> 
> I also appreciate these options but I'd like
> to comment on default value of min-{refresh,retry}-time,
> which seems to be 300 and 500 respectively.
> 
> It changes default behavior of NSD, and will surprise people (including me)
> who really want small REFRESH value to minimise zone propagation time.
> 
> So I suggest that default value of min-{refresh,retry}-time option
> to be 0, to leave NSD's default behavior unchanged.
> 
> The option is useful for to "secondary DNS provider"
> who want to supress refresh flooding. If they want to do it
> they would select appropriate values and set these options.
> 
> Regards,