]> git.ipfire.org Git - thirdparty/knot-resolver.git/commit
projects / thirdparty / knot-resolver.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: ec1606c) | patch
lib/rules: fix RPZ if it contains apex NS record docs-develop-rpz-7rpq6b/deployments/3526
authorVladimír Čunát <vladimir.cunat@nic.cz>
Wed, 20 Mar 2024 09:51:41 +0000 (10:51 +0100)
committerVladimír Čunát <vladimir.cunat@nic.cz>
Wed, 20 Mar 2024 10:01:36 +0000 (11:01 +0100)
commitd034c523c6eac98e3142a2707992a158670a5951
tree475905e80938cf91b361212991d5dd583389edc7tree
parentec1606c47042532ab2cd27a10c08838f99f45662commit | diff
lib/rules: fix RPZ if it contains apex NS record

The spec even requires (at least one) NS record in apex
https://datatracker.ietf.org/doc/html/draft-vixie-dns-rpz-00#section-2
but until now the implementation took it as override for the root NS,
which obviously broke resolution (depending on the supplied name/s).
NEWS diff | blob | blame | history
lib/rules/zonefile.c diff | blob | blame | history
Mirror of https://gitlab.nic.cz/knot/knot-resolver.git