Files
bind9/bin/tests/system/rpz
Michał Kępień 39191052ad Wait for the "fast-expire" zone to be transferred
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.
2020-11-05 07:53:43 +01:00
..

Copyright (C) Internet Systems Consortium, Inc. ("ISC")

See COPYRIGHT in the source root or https://isc.org/copyright.html for terms.

The test setup for the RPZ tests prepares a query perf tool and sets up
policy zones.

Name servers
------------

ns1 is the root server.

ns2 and ns4 are authoritative servers for the various test domains.

ns3 is the main rewriting resolver.

ns5 and ns7 are additional rewriting resolvers.

ns6 is a forwarding server.


Updating the response policy zones
----------------------------------

test1, test2, test3, test4, test5, and test6 are dynamic update files.  These
updates are made against ns3.  The script function "start_group" is called to
start an new batch of tests that may depend on certain server updates.  The
function takes an optional file name and if provided the server updates are
performed before executing the test batch.