bind9

Files

T

Michał KępieńandEvan Hunt 7d6b8f7c12 Log a message when a mirror zone becomes unusable

Log a message if a mirror zone becomes unusable for the resolver (most
usually due to the zone's expiration timer firing).  Ensure that
verification failures do not cause a mirror zone to be unloaded
(instead, its last successfully verified version should be served if it
is available).

2019-01-16 10:38:12 -08:00

ns1

Fix handling of TAT sending failures

2018-07-20 01:55:50 +10:00

ns2

Log a message when a transferred mirror zone comes into effect

2019-01-16 10:33:02 -08:00

ns3

Test whether mirror zones can be added and removed dynamically

2018-10-24 20:32:56 +02:00

clean.sh

Test whether mirror zones can be added and removed dynamically

2018-10-24 20:32:56 +02:00

README

Replace the "mirror" zone option with "type mirror;"

2018-10-24 20:32:55 +02:00

setup.sh

Replace the "mirror" zone option with "type mirror;"

2018-10-24 20:32:55 +02:00

tests.sh

Log a message when a mirror zone becomes unusable

2019-01-16 10:38:12 -08:00

README

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

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

This test checks whether zones configured with "type mirror;" behave as
expected.

ns1 is an authoritative-only server.  It only serves the root zone, which is
mirrored by ns3.

ns2 is an authoritative-only server.  It serves a number of zones, some of which
are delegated to it by ns1 and used in recursive resolution tests aimed at ns3
while others are only served so that ns3 has a primary server to mirror zones
from during various tests of the mirror zone implementation.

ns3 is a recursive resolver.  It has a number of mirror zones configured.  This
is the only server whose behavior is being examined by this system test.