Open onlime opened 1 year ago
So sorry for the late follow up - I didn't get an email notification of this issue for some reason and just spotted it when reviewing the site...
I've updated the page to explain the need for double negation (good question!) and updated to sha256 too. Many thanks!
On https://dnsprivacy.org/encrypted-zone-transfer (BTW great documentation! had it implemented easily thanks to this nice overview) you recommend the following
acl
for Bind9 configuration:Can you please explain that double negation? Could that acl be simplified to the following?:
I would like to achieve that only secondaries (listed in
acl xot-secondaries
) are allowed to transfer zones, and only if those are providing the same shared secretxot-key
.Also, I would like to point out that
hmac-sha256
algorithm should be preferred overhmac-md5
in your documentation. Please also document how to generate thexot-key
, e.g. with the TSIG key generation tooltsig-keygen
(which defaults tohmac-sha256
, at least in Debian Bookworm's bind9 9.18.19:Thanks, Philip