bind9/bin/tests/system/mirror
Evan Hunt 0b09ee8cdc explicitly set dnssec-validation in system tests
the default value of dnssec-validation is 'auto', which causes
a server to send a key refresh query to the root zone when starting
up. this is undesirable behavior in system tests, so this commit
sets dnssec-validation to either 'yes' or 'no' in all tests where
it had not previously been set.

this change had the mostly-harmless side effect of changing the cached
trust level of unvalidated answer data from 'answer' to 'authanswer',
which caused a few test cases in which dumped cache data was examined in
the serve-stale system test to fail. those test cases have now been
updated to expect 'authanswer'.
2023-06-26 13:41:56 -07:00
..
ns1 explicitly set dnssec-validation in system tests 2023-06-26 13:41:56 -07:00
ns2 explicitly set dnssec-validation in system tests 2023-06-26 13:41:56 -07:00
ns3 explicitly set dnssec-validation in system tests 2023-06-26 13:41:56 -07:00
clean.sh Add shell interpreter line where missing 2022-11-14 19:54:42 +00:00
README Update the copyright information in all files in the repository 2022-01-11 09:05:02 +01:00
setup.sh Update the copyright information in all files in the repository 2022-01-11 09:05:02 +01:00
tests.sh Simplify start/stop helper func in system tests 2022-11-25 09:27:33 +01:00
tests_sh_mirror.py Add pytest functions for shell system tests 2023-05-22 14:11:39 +02:00

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

SPDX-License-Identifier: MPL-2.0

This Source Code Form is subject to the terms of the Mozilla Public
License, v. 2.0.  If a copy of the MPL was not distributed with this
file, you can obtain one at https://mozilla.org/MPL/2.0/.

See the COPYRIGHT file distributed with this work for additional
information regarding copyright ownership.
-->

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.