Remi Gacogne

``` Error during execution of maintenance function(s): ./dnsdist-resolver.lua:89: attempt to call local 'resout' (a nil value) stack traceback: ./dnsdist-resolver.lua:89: in function ``` This does not match the lines from the...

> We have to decide explicitly if this change is wanted. As a data point, the new behaviour is what DNSdist has been doing for a long time, and I'm...

Right, the inclusion/exclusion lists were not designed with this in mind but what you are suggesting makes to me. I'm tentatively assigning this to 2.1.0 milestone as I'm not sure...

I don't quite get why we would want to process notify queries for authoritative zones: is there a way to reload them without using `rec_control reload-zones` or the API?

> So I think I'll be removing the notify_allowed field for auth zones. Makes sense to me.

I see we already have an accessor for the DNSSEC OK bit (`dnsdist_ffi_dnsquestion_get_do`) and for EDNS options (`dnsdist_ffi_dnsquestion_get_edns_options`). There is no other flag defined as far as I know, so...

Wonderful, thank you for testing!

So it's slightly more complicated than that: your third attempt actually works! But, for performance reasons, the timestamp we are using for the dynamic block is obtained via `CLOCK_MONOTONIC`, and...

I'm not sure I understand what you mean, because the callback passed to `DynBlockRulesGroup:setNewBlockInsertedHook()` will be invoked right after a dynamic block has been added, so the time when the...

Right, I see what you meant now, thanks! I understand the use-case, but it would require adding a new field to the internal `DynBlock` structure to store the initial duration,...