README 2.7 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162
  1. Copyright (C) 2004, 2010, 2011 Internet Systems Consortium, Inc. ("ISC")
  2. Copyright (C) 2000, 2001 Internet Software Consortium.
  3. See COPYRIGHT in the source root or http://isc.org/copyright.html for terms.
  4. This is a simple test environment for running BIND 10 system tests
  5. involving multiple name servers. It was originally developed for BIND
  6. 9, and has been ported to test BIND 10 implementations. Ideally we
  7. should share the same framework for both versions, so some part of
  8. the original setup are kept, even though they are BIND 9 specific and
  9. not currently used.
  10. Also, these tests generally rely on BIND 9 programs, most commonly its
  11. dig, and will sometimes be its name server (named). So, the test
  12. environment assumes that there's a source tree of BIND 9 where its
  13. programs are built, and that an environment variable "BIND9_TOP" is
  14. set to point to the top directory of the source tree.
  15. There are multiple test suites, each in a separate subdirectory and
  16. involving a different DNS setup. They are:
  17. glue/ Glue handling tests
  18. (the following tests are planned to be added soon)
  19. dnssec/ DNSSEC tests
  20. masterfile/ Master file parser
  21. xfer/ Zone transfer tests
  22. Typically each test suite sets up 2-5 instances of BIND 10 (or BIND 9
  23. named) and then performs one or more tests against them. Within the
  24. test suite subdirectory, each instance has a separate subdirectory
  25. containing its configuration data. By convention, these
  26. subdirectories are named "nsx1", "nsx2", etc for BIND 10 ("x" means
  27. BIND 10), and "ns1", "ns2", etc. for BIND 9.
  28. The tests are completely self-contained and do not require access to
  29. the real DNS. Generally, one of the test servers (ns[x]1) is set up
  30. as a root name server and is listed in the hints file of the others.
  31. To enable all servers to run on the same machine, they bind to
  32. separate virtual IP address on the loopback interface. ns[x]1 runs on
  33. 10.53.0.1, ns[x]2 on 10.53.0.2, etc. Before running any tests, you
  34. must set up these addresses by running "ifconfig.sh up" as root.
  35. Mac OS X:
  36. If you wish to make the interfaces survive across reboots
  37. copy org.isc.bind.system and org.isc.bind.system to
  38. /Library/LaunchDaemons then run
  39. "launchctl load /Library/LaunchDaemons/org.isc.bind.system.plist" as
  40. root.
  41. The servers use port 53210 instead of the usual port 53, so they can be
  42. run without root privileges once the interfaces have been set up.
  43. The tests can be run individually like this:
  44. sh run.sh xfer
  45. sh run.sh glue
  46. etc.
  47. To run all the tests, just type "make systest" either on this directory
  48. or on the top source directory. Note: currently these tests cannot be
  49. run when built under a separate build directory. Everything must be
  50. run within the original source tree.