bind9

mirror of https://github.com/isc-projects/bind9.git synced 2026-03-01 04:50:50 -05:00

History

Evan Hunt e43b3c1fa1 further tidying of primary/secondary terminology in system tests this changes most visble uses of master/slave terminology in tests.sh and most uses of 'type master' or 'type slave' in named.conf files. files in the checkconf test were not updated in order to confirm that the old syntax still works. rpzrecurse was also left mostly unchanged to avoid interference with DNSRPS.		2020-07-01 11:12:12 -07:00
..
ns1	further tidying of primary/secondary terminology in system tests	2020-07-01 11:12:12 -07:00
ns2	further tidying of primary/secondary terminology in system tests	2020-07-01 11:12:12 -07:00
ns3	add "primaries" as a synonym for "masters" in named.conf	2020-07-01 11:11:34 -07: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	Complete rewrite the BIND 9 build system	2020-04-21 14:19:48 +02:00
tests.sh	further tidying of primary/secondary terminology in system tests	2020-07-01 11:12:12 -07: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.