bind9/bin/tests/system/mkeys
Michal Nowak 20b446cdc3 mkeys: Prevent failing grep invocations
Some 'grep' invocations were not guarded from interrupting the test
prematurely, e.g. when no text was matched.
2020-01-22 14:53:01 +00:00
..
ns1 use DS style trust anchors in all system tests 2019-11-15 15:47:57 -08:00
ns2 convert ns_client and related objects to use netmgr 2019-11-07 11:55:37 -08:00
ns3 Rename 'dnssec-keys' to 'trust-anchors' 2019-12-05 12:19:17 +01:00
ns4 remove "dnssec-enable" from all system tests 2019-03-14 23:30:13 -07:00
ns5 convert ns_client and related objects to use netmgr 2019-11-07 11:55:37 -08:00
ns6 use DS style trust anchors in all system tests 2019-11-15 15:47:57 -08:00
ns7 remove "dnssec-enable" from all system tests 2019-03-14 23:30:13 -07:00
clean.sh Add tests for mkeys with unsupported algorithm 2019-02-20 19:44:33 -08:00
README Rename 'dnssec-keys' to 'trust-anchors' 2019-12-05 12:19:17 +01:00
setup.sh Automatically run clean.sh from run.sh 2019-12-06 14:11:01 +01:00
tests.sh mkeys: Prevent failing grep invocations 2020-01-22 14:53:01 +00:00

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

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

This is for testing RFC 5011 Automated Updates of DNSSEC Trust Anchors.

ns1 is the root server that offers new KSKs and hosts one record for
testing. The TTL for the zone's records is 2 seconds.

ns2 is a validator that uses managed keys.  "-T mkeytimers=2/20/40"
is used so it will attempt do automated updates frequently. "-T tat=1"
is used so it will send TAT queries once per second.

ns3 is a validator with a broken initializing key in trust-anchors.

ns4 is a validator with a deliberately broken managed-keys.bind and
managed-keys.jnl, causing RFC 5011 initialization to fail.

ns5 is a validator which is prevented from getting a response from the
root server, causing key refresh queries to fail.

ns6 is a validator which has unsupported algorithms, one at start up,
one because of an algorithm rollover.

ns7 is a validator with multiple views configured.  It is used for
testing per-view rndc commands and checking interactions between options
related to and potentially affecting RFC 5011 processing.