+3940. [func] "rndc nta" now allows negative trust anchors to be
+ set for up to one week. [RT #37069]
+
3939. [func] Improve UPDATE forwarding performance by allowing TCP
connections to be shared. [RT #37039]
CHECK(result);
}
- if (ntattl > 86400) {
- msg = "NTA lifetime cannot exceed one day";
+ if (ntattl > 604800) {
+ msg = "NTA lifetime cannot exceed one week";
CHECK(ISC_R_RANGE);
}
<option>lifetime</option>. The default lifetime is
configured in <file>named.conf</file> via the
<option>nta-lifetime</option>, and defaults to
- one hour. The lifetime cannot exceed one day.
+ one hour. The lifetime cannot exceed one week.
</para>
<para>
A negative trust anchor selectively disables
if [ $ret != 0 ]; then echo "I:failed"; fi
status=`expr $status + $ret`
+echo "I:testing rndc nta time limits"
+ret=0
+$RNDC -s 10.53.0.4 -p 9956 -c ns4/key6.conf nta -l 2h nta1.example 2>&1 | grep "Negative trust anchor added" > /dev/null || ret=1
+$RNDC -s 10.53.0.4 -p 9956 -c ns4/key6.conf nta -l 1d nta2.example 2>&1 | grep "Negative trust anchor added" > /dev/null || ret=1
+$RNDC -s 10.53.0.4 -p 9956 -c ns4/key6.conf nta -l 1w nta3.example 2>&1 | grep "Negative trust anchor added" > /dev/null || ret=1
+$RNDC -s 10.53.0.4 -p 9956 -c ns4/key6.conf nta -l 8d nta4.example 2>&1 | grep "NTA lifetime cannot exceed one week" > /dev/null || ret=1
echo "I:exit status: $status"
exit $status
For convenience, TTL-style time unit suffixes can be
used to specify the NTA lifetime in seconds, minutes
or hours. <option>nta-lifetime</option> defaults to
- one hour. It cannot exceed one day.
+ one hour. It cannot exceed one week.
</para>
</listitem>
</varlistentry>