Deprecation notice for BIND 9: "resolver-nonbackoff-tries", "resolver-retry-interval"

[Petr Špaček]

On 07. 12. 23 22:12, Fred Morris wrote:
> I welcome birds of a feather. Need to define / refine the problem
> statement first.
> 
> On 12/7/23 12:30 AM, Petr Špaček wrote:
> 
>> On 07. 12. 23 1:05, Fred Morris wrote:
>>> On Wed, 6 Dec 2023, Evan Hunt wrote:
>>> I say go ahead, if nothing else consider it a "scream test". But can
>>> you take a moment and tell us which stakeholder group(s) you think
>>> you're optimizing for, why, and how?
>> On the technical level we optimize using real (anonymized!) traffic
>> provided to us by operators. Here's what we need:
>> https://kb.isc.org/docs/collecting-client-queries-for-dns-server-testing
>>
>> If you want us to optimize for your use-case let's talk how we can get
>> the data and replicate your setup!
> I run Dnstap (for $reasons), but I'd be able to run dnscap and from the
> look of that KB page you only want the queries. I'm not sure that really
> captures the qualitative issue(s). I plan to dig into this some more
> over the winter anyway, maybe I should turn the tables and ask if there
> are other systemic issues I should look at or for?

We are certainly interested in hearing what metric is of interest and 
what we might be missing.

Right now we monitor everything we can from statistics provided by DNS 
Shotgun [1], BIND statistics channel [2], and system resource monitoring 
[3].

[1] https://dns-shotgun.readthedocs.io/en/stable/
[2] 
https://bind9.readthedocs.io/en/v9.19.18/reference.html#namedconf-statement-statistics-channels
[3] 
https://gitlab.isc.org/isc-projects/resource-monitor/-/blob/main/resmon.yaml

-- 
Petr Špaček
Internet Systems Consortium