|
BIND 9 has a lot of configuration options. Some have lost value over the years, but the policy was to keep the options to not break old configurations.
|
|
BIND 9 has a lot of configuration options. Some have lost value over the years, but the policy was to keep the options to not break old configurations.
|
|
|
|
|
|
|
|
**:question: Does this policy apply only to named.conf options, or to, e.g. algorithms, builds, etc?
|
|
|
|
|
|
However, we also want to clean up the code at some point. Keeping these options increases the number of corner cases and makes maintenance more cumbersome. It can also be confusing to new users. We are trying to establish an orderly, staged process that gives existing users ample time to react and adapt to obsoleted options.
|
|
However, we also want to clean up the code at some point. Keeping these options increases the number of corner cases and makes maintenance more cumbersome. It can also be confusing to new users. We are trying to establish an orderly, staged process that gives existing users ample time to react and adapt to obsoleted options.
|
|
|
|
|
|
This policy describes the procedure for removing named.conf options.
|
|
This policy describes the procedure for removing named.conf options.
|
... | | ... | |