bind9/bin/tests/system/chain
Michał Kępień d8905b7a9c Automatically run clean.sh from run.sh
The first step in all existing setup.sh scripts is to call clean.sh.  To
reduce code duplication and ensure all system tests added in the future
behave consistently with existing ones, invoke clean.sh from run.sh
before calling setup.sh.
2019-12-06 14:11:01 +01:00
..
ans3 Update license headers to not include years in copyright in all applicable files 2018-02-23 10:12:02 +01:00
ans4 update file headers 2018-03-15 18:33:13 -07:00
ns1 update system tests so validation won't fail when using IANA key 2018-05-31 18:22:33 +02:00
ns2 Remove 2>&1 from the dnssec-signzone invocation in tests 2019-07-31 10:05:52 +02:00
ns5 update system tests so validation won't fail when using IANA key 2018-05-31 18:22:33 +02:00
ns7 test case 2018-08-08 14:33:19 -07:00
clean.sh update system tests so validation won't fail when using IANA key 2018-05-31 18:22:33 +02:00
prereq.sh RSA and ECDSA cryptography is now mandatory; remove the checks for those 2018-07-19 12:47:03 -04:00
README update file headers 2018-03-15 18:33:13 -07:00
setup.sh Automatically run clean.sh from run.sh 2019-12-06 14:11:01 +01:00
tests.sh chain: add 'start test' messages to named.run 2018-10-04 12:26:28 +10:00

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

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

ns1 is the root server.

ns2 and ns5 are both authoritative servers.

ans3 is a mock authoritative server that can return various broken
responses.

ans4 is a mock authoritative server that can return CNAME or DNAME
responses of arbitrary size in arbitrary order.

ns7 is the resolver under test.