previously, a managed-keys zone was created for every view
regardless of whether rfc5011 was in use; when it was not in
use, the zone would be left empty. this made for some confusing
log messages.
we now only set up the managed-keys zone if dnssec-validation is
set to the default value of "auto".
certain system test servers have had their dnssec-validation settings
changed to auto because the tests depended on the existence of the
zone.
}
}
- CHECK(add_keydata_zone(view, directory, named_g_mctx));
+ if (auto_root) {
+ CHECK(add_keydata_zone(view, directory, named_g_mctx));
+ }
cleanup:
return (result);
pid-file "named.pid";
listen-on { 10.53.0.1; };
listen-on-v6 { none; };
- dnssec-validation yes;
+ dnssec-validation auto;
minimal-responses no;
recursion no;
notify yes;
pid-file "named.pid";
listen-on { 10.53.0.2; };
listen-on-v6 { none; };
- dnssec-validation yes;
+ dnssec-validation auto;
minimal-responses no;
recursion no;
notify yes;
listen-on-v6 { none; };
recursion yes;
notify no;
- dnssec-validation yes;
+ dnssec-validation auto;
bindkeys-file "managed.conf";
trust-anchor-telemetry no;
};
listen-on-v6 { none; };
recursion yes;
notify no;
- dnssec-validation yes;
+ dnssec-validation auto;
trust-anchor-telemetry no;
};
echo_i "testing automatic zones are reported ($n)"
ret=0
$RNDC -s 10.53.0.4 -p ${EXTRAPORT6} -c ns4/key6.conf status > rndc.out.1.test$n || ret=1
-grep "number of zones: 201 (198 automatic)" rndc.out.1.test$n > /dev/null || ret=1
+grep "number of zones: 199 (198 automatic)" rndc.out.1.test$n > /dev/null || ret=1
if [ $ret != 0 ]; then echo_i "failed"; fi
status=$((status+ret))