Gratuitous AXFRs of RPZ after 9.18.11

I have a primary server and a couple of secondaries. After making adjustments to my RPZ yesterday (which almost never change), I noticed an oddity. One of my secondaries is performing gratuitous AXFRs of the RPZ. This isn't a huge performance issue, as my RPZ is only 7.3KB. I want to understand

Re: rpz testing -> shut down hung fetch while resolving

On Thu, Jan 26, 2023 at 07:03:37PM +0100, Havard Eidnes via bind-users wrote: > Hi, > > I recently made an upgrade of BIND to version 9.18.11 on our > resolver cluster, following the recent announcement. Shortly > thereafter I received reports that the validation that lookups of > "known entries"

rpz testing -> shut down hung fetch while resolving

Hi, I recently made an upgrade of BIND to version 9.18.11 on our resolver cluster, following the recent announcement. Shortly thereafter I received reports that the validation that lookups of "known entries" in our quite small RPZ feed (it's around 1MB on-disk) no longer succeeds as expected, but

lame-servers: info: no valid RRSIG resolving

Hi All, Sorry for asking what is almost certainly a "noob" question, but I'm seeing a lot of "lame-servers: info: no valid RRSIG resolving './NS/IN':" messages in our auth_servers.log for the DNS Root Servers' IPv4 addresses. Is this normal, or do we have an issue that we need to resolve. T