Re: AW: Problems with (unsigned) forward zones, dnssec-validation auto and validate-except on BIND 9.16 and 9.17

On 27. 01. 22 16:05, Gehrkens.IT GmbH | Heiko Wundram wrote: Hello Tony, The other things that can cause the behaviour you observed are synth-from- dnssec and qname-minimization. thanks for the heads up concerning synth-from-dnssec; I thought the default was "no", but that seems to have

Re: test - ignore

On 2022-01-27 08:42, Matus UHLAR - fantomas wrote: however, this discussion should be probably closed as it's not anymore related to this mailing list operatiorns. i only replyed to isc ignore in first place to heads up on that thay break there own dkim signer, when maillists do this all

AW: Problems with (unsigned) forward zones, dnssec-validation auto and validate-except on BIND 9.16 and 9.17

Hello Tony, > The other things that can cause the behaviour you observed are synth-from- > dnssec and qname-minimization. thanks for the heads up concerning synth-from-dnssec; I thought the default was "no", but that seems to have changed somewhere between 9.14 and 9.16... I've just changed that

Re: Problems with (unsigned) forward zones, dnssec-validation auto and validate-except on BIND 9.16 and 9.17

Gehrkens.IT GmbH | Heiko Wundram wrote: > > From what I gather, this behaviour sounds almost like what RFC 8020 proposes > (NXDOMAIN cut), but at least according to the corresponding ticket, that > isn't implemented in BIND. The other things that can cause the behaviour you observed are

Re: 9.18.0 now available and broken on ppc64le

Unfortunately that makes initial release of new stable branch not working on ppc64le architecture at all. All IBM Power8 or Power9 I were testing reports cacheline size 128, and therefore fails probably on any such processor. Not even unit test or dig or host command would run on it. More in MR