ComputerSurge/bind9
3
0
Fork 0
Code Pull Requests 1 Activity

Use rndc_dumpdb() in the "serve-stale" system test

Browse Source
This commit is contained in:
Michał Kępień
2019-08-08 14:27:55 +02:00
parent 443449863b
commit 52beeed444
3 changed files with 3 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
bin/tests/system/serve-stale/tests.sh
View File

@@ -96,15 +96,11 @@ grep "data\.example\..*2.*IN.*TXT.*A text record with a 1 second ttl" dig.out.te
# Run rndc dumpdb, test whether the stale data has correct comment printed.
# The max-stale-ttl is 3600 seconds, so the comment should say the data is
# stale for somewhere between 3500-3599 seconds.
$RNDCCMD 10.53.0.1 dumpdb > rndc.out.test$n 2>&1 || ret=1
for i in 0 1 2 3 4 5 6 7 8 9; do
grep '^; Dump complete$' ns1/named_dump1.db > /dev/null 2>&1 && break
sleep 1
done
awk '/; stale/ { x=$0; getline; print x, $0}' ns1/named_dump1.db |
rndc_dumpdb ns1 || ret=1
awk '/; stale/ { x=$0; getline; print x, $0}' ns1/named_dump.db.test$n |
grep "; stale (will be retained for 35.. more seconds) data\.example.*A text record with a 1 second ttl" > /dev/null 2>&1 || ret=1
# Also make sure the not expired data does not have a stale comment.
awk '/; answer/ { x=$0; getline; print x, $0}' ns1/named_dump1.db |
awk '/; answer/ { x=$0; getline; print x, $0}' ns1/named_dump.db.test$n |
grep "; answer longttl\.example.*A text record with a 600 second ttl" > /dev/null 2>&1 || ret=1
if [ $ret != 0 ]; then echo_i "failed"; fi
status=`expr $status + $ret`