bind9/bin/tests/system/dnssec
Brian Wellington 66b84e8952 - test insecurity proofs
- use digcomp.pl's ability to check rcode
- generate less unneeded output
- use separate output files for each test, so that output isn't deleted
2000-07-08 00:39:17 +00:00
..
ns1 add RCS id string 2000-06-22 22:00:42 +00:00
ns2 add RCS id string 2000-06-22 22:00:42 +00:00
ns3 added CNAME RR for RT #153 regression test 2000-07-07 22:33:20 +00:00
ns4 add RCS id string 2000-06-22 22:00:42 +00:00
ns5 add RCS id string 2000-06-22 22:00:42 +00:00
clean.sh add RCS id string 2000-06-22 22:00:42 +00:00
random.data Missing file 2000-06-12 20:59:33 +00:00
README add RCS id string 2000-06-22 22:00:42 +00:00
setup.sh add RCS id string 2000-06-22 22:00:42 +00:00
tests.sh - test insecurity proofs 2000-07-08 00:39:17 +00:00

Copyright (C) 2000  Internet Software Consortium.
See COPYRIGHT in the source root or http://www.isc.org/copyright for terms.

$Id: README,v 1.3 2000/06/22 21:51:32 tale Exp $

The test setup for the DNSSEC tests has a secure root.

ns1 is the root server.

ns2 and ns3 are authoritative servers for the various test domains.

ns4 is a caching-only server, configured with the correct trusted key
for the root.

ns4 is a caching-only server, configured with the an incorrect trusted
key for the root.  It is used for testing failure cases.