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

Wait for the "fast-expire" zone to be transferred

Browse Source 
In order for a "fast-expire/IN: response-policy zone expired" message to
be logged in ns3/named.run, the "fast-expire" zone must first be
transferred in by that server.  However, with unfavorable timing, ns3
may be stopped before it manages to fetch the "fast-expire" zone from
ns5 and after the latter has been reconfigured to no longer serve that
zone.  In such a case, the "rpz" system test will report a false
positive for the relevant check.  Prevent that from happening by
ensuring ns3 manages to transfer the "fast-expire" zone before getting
shut down.

(cherry picked from commit 39191052ad)
This commit is contained in:
Michał Kępień
2020-11-05 07:53:43 +01:00
parent 1e8cab780b
commit 64ca2e0061
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
bin/tests/system/rpz/tests.sh
View File

@@ -782,7 +782,10 @@ EOF
done
fi
# reconfigure the ns5 master server without the fast-exire zone, so
# Ensure ns3 manages to transfer the fast-expire zone before shutdown.
wait_for_log 20 "zone fast-expire/IN: transferred serial 1" ns3/named.run
# reconfigure the ns5 primary server without the fast-expire zone, so
# it can't be refreshed on ns3, and will expire in 5 seconds.
cat /dev/null > ns5/expire.conf
rndc_reconfig ns5 10.53.0.5