262N/ACopyright (C) 2004 Internet Systems Consortium, Inc. ("ISC")
262N/ACopyright (C) 2000, 2001 Internet Software Consortium.
262N/AThis is a simple test environment for running bind9 system tests
262N/Ainvolving multiple name servers.
262N/AThere are multiple test suites, each in a separate subdirectory and
262N/Ainvolving a different DNS setup. They are:
262N/A forward/ Forwarding tests
262N/A glue/ Glue handling tests
262N/A limits/ Tests of handling of large data (close to server limits)
262N/A lwresd/ Tests of the lightweight resolver library and daemon
262N/A notify/ More NOTIFY tests
262N/A nsupdate/ Dynamic update and IXFR tests
262N/A resolver/ Regression tests for resolver bugs that have been fixed
262N/A (not a complete resolver test suite)
262N/A stub/ Tests of stub zone functionality
5680N/A unknown/ Unknown type and class tests
262N/A upforwd/ Update forwarding tests
5680N/A views/ Tests of the "views" statement
5680N/A xferquota/ Zone transfer quota tests
5992N/ATypically each test suite sets up 2-5 name servers and then performs
262N/Aone or more tests against them. Within the test suite subdirectory,
262N/Aeach name server has a separate subdirectory containing its
5992N/Aconfiguration data. By convention, these subdirectories are named
844N/AThe tests are completely self-contained and do not require access to
5992N/Athe real DNS. Generally, one of the test servers (ns1) is set up as a
262N/Aroot name server and is listed in the hints file of the others.
1258N/ATo enable all servers to run on the same machine, they bind to
262N/Aseparate virtual IP address on the loopback interface. ns1 runs on
5992N/A10.53.0.1, ns2 on 10.53.0.2, etc. Before running any tests, you must
5992N/AThe servers use port 5300 instead of the usual port 53, so they can be
7165N/Arun without root privileges once the interfaces have been set up.
7165N/AThe tests can be run individually like this:
5680N/ATo run all the tests, just type "make test".
262N/A$Id: README,v 1.12 2004/03/05 04:59:12 marka Exp $