Frantisek Sumsal 0e251ccf9f test: explicitly set nsec3-iterations to 0 ...

knot v3.2 and later does this by default. knot v3.1 still has the default set to
10, but it also introduced a warning that the default will be changed to 0 in
later versions, so it effectively complains about its own default, which then
fails the config check. Let's just set the value explicitly to zero to avoid
that.

~# knotc --version
knotc (Knot DNS), version 3.1.6
~# grep nsec3-iterations test/knot-data/knot.conf || echo nope
nope
~# knotc -c /build/test/knot-data/knot.conf conf-check
warning: config, policy[auto_rollover_nsec3].nsec3-iterations defaults to 10, since version 3.2 the default becomes 0
Configuration is valid

Follow-up to 0652cf8e7b.

(cherry picked from commit cb3244c0dcea80ad35e5bcaf7a07bd449ac65325)
(cherry picked from commit 3158eb9f8f3e64b2729107dc9ef06509b100150e)
(cherry picked from commit 478a284b639a80a377694d615573ddcd33ab3916)

2024-02-28 10:29:35 +00:00

..

zones

test: add a test for the OPENPGPKEY RR

2023-01-27 15:45:00 +01:00

knot.conf

test: explicitly set nsec3-iterations to 0

2024-02-28 10:29:35 +00:00