README 7.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251
  1. This is the source for the development version of BIND 10.
  2. BIND is the popular implementation of a DNS server, developer
  3. interfaces, and DNS tools. BIND 10 is a rewrite of BIND 9. BIND 10
  4. is written in C++ and Python and provides a modular environment
  5. for serving, maintaining, and developing DNS.
  6. BIND10-devel is new development leading up to the production
  7. BIND 10 release. It contains prototype code and experimental
  8. interfaces. Nevertheless it is ready to use now for testing the
  9. new BIND 10 infrastructure ideas. The Year 2 milestones of the
  10. five year plan are described here:
  11. https://bind10.isc.org/wiki/Year2Milestones
  12. This release includes the bind10 master process, b10-msgq message
  13. bus, b10-auth authoritative DNS server (with SQLite3 backend),
  14. b10-recurse forwarding DNS server, b10-cmdctl remote control daemon,
  15. b10-cfgmgr configuration manager, b10-xfrin AXFR inbound service,
  16. b10-xfrout outgoing AXFR service, b10-zonemgr secondary manager,
  17. b10-stats statistics collection and reporting daemon, and a new
  18. libdns++ library for C++ with a python wrapper.
  19. Documentation is included and also available via the BIND 10
  20. website at http://bind10.isc.org/
  21. The latest released source may be downloaded from:
  22. ftp://ftp.isc.org/isc/bind10/
  23. Users and developers are encouraged to participate on the BIND 10
  24. mailing lists:
  25. https://lists.isc.org/mailman/listinfo/bind10-users
  26. https://lists.isc.org/mailman/listinfo/bind10-dev
  27. Bugs may be reported as tickets via the developers website:
  28. http://bind10.isc.org/
  29. BUILDING
  30. See the Guide for detailed installation directions at
  31. doc/guide/bind10-guide.html.
  32. Simple build instructions:
  33. ./configure
  34. make
  35. If building from Subversion repository, run:
  36. autoreconf --install
  37. before running ./configure
  38. Requires autoconf 2.59 or newer.
  39. Use automake-1.11 or better for working Python 3.1 tests.
  40. Alternatively, you could manually specify an absolute path to python
  41. executable by the --with-pythonpath option of the configure script,
  42. e.g.,
  43. % ./configure --with-pythonpath=/usr/local/bin/python3.1
  44. Operating-System specific tips:
  45. - FreeBSD
  46. You may need to install a python binding for sqlite3 by hand. A
  47. sample procedure is as follows:
  48. - add the following to /etc/make.conf
  49. PYTHON_VERSION=3.1
  50. - build and install the python binding from ports, assuming the top
  51. directory of the ports system is /usr/ports
  52. % cd /usr/ports/databases/py-sqlite3/
  53. % make
  54. % sudo make install
  55. INSTALLATION
  56. Install with:
  57. make install
  58. TESTS
  59. The tests use the googletests framework for C++. It is available
  60. from http://code.google.com/p/googletest/. To enable the tests,
  61. configure BIND 10 with:
  62. ./configure --with-gtest
  63. Then run "make check" to run these tests.
  64. TEST COVERAGE
  65. Code coverage reports may be generated using make. These are
  66. based on running on the unit tests. The resulting reports are placed
  67. in coverage-cpp-html and coverage-python-html directories for C++
  68. and Python, respectively.
  69. The code coverage report for the C++ tests uses LCOV. It is available
  70. from http://ltp.sourceforge.net/. To generate the HTML report,
  71. first configure BIND 10 with:
  72. ./configure --with-lcov
  73. The code coverage report for the Python tests uses coverage.py (aka
  74. pycoverage). It is available from http://nedbatchelder.com/code/coverage/.
  75. To generate the HTML report, first configure BIND 10 with:
  76. ./configure --with-pycoverage
  77. Doing code coverage tests:
  78. make coverage
  79. Does the clean, perform, and report targets for C++ and Python.
  80. make clean-coverage
  81. Zeroes the code coverage counters and removes the HTML reports
  82. for C++ and Python.
  83. make perform-coverage
  84. Runs the C++ (using the googletests framework) and Python
  85. tests.
  86. make report-coverage
  87. Generates the coverage reports in HTML for C++ and Python.
  88. make clean-cpp-coverage
  89. Zeroes the code coverage counters and removes the HTML report
  90. for the C++ tests.
  91. make clean-python-coverage
  92. Zeroes the code coverage counters and removes the HTML report
  93. for the Python tests.
  94. make report-cpp-coverage
  95. Generates the coverage report in HTML for C++, excluding
  96. some unrelated headers. The HTML reports are placed in a
  97. directory called coverage-cpp-html/.
  98. make report-python-coverage
  99. Generates the coverage report in HTML for Python. The HTML
  100. reports are placed in a directory called coverage-python-html/.
  101. DEVELOPERS
  102. The generated run_*.sh scripts available in the src/bin directories
  103. are for running the code using the source tree.
  104. RUNNING
  105. You can start the BIND 10 processes by running bind10 which is
  106. installed to the sbin directory under the installation prefix.
  107. The default location is:
  108. /usr/local/sbin/bind10
  109. For development work, you can also run the bind10 services from the
  110. source tree:
  111. ./src/bin/bind10/run_bind10.sh
  112. (Which will use the modules and configurations also from the source
  113. tree.)
  114. The server will listen on port 5300 for DNS requests.
  115. CONFIGURATION
  116. Commands can be given through the bindctl tool.
  117. The server must be running for bindctl to work.
  118. The following configuration commands are available
  119. help: show the different command modules
  120. <module> help: show the commands for module
  121. <module> <command> help: show info for the command
  122. config show [identifier]: Show the currently set values. If no identifier is
  123. given, the current location is used. If a config
  124. option is a list or a map, the value is not
  125. shown directly, but must be requested separately.
  126. config go [identifier]: Go to the given location within the configuration.
  127. config set [identifier] <value>: Set a configuration value.
  128. config unset [identifier]: Remove a value (reverts to default if the option
  129. is mandatory).
  130. config add [identifier] <value>: add a value to a list
  131. config remove [identifier] <value>: remove a value from a list
  132. config revert: Revert all changes that have not been committed
  133. config commit: Commit all changes
  134. config diff: Show the changes that have not been committed yet
  135. EXAMPLE SESSION
  136. ~> bindctl
  137. ["login success "] login as root
  138. > help
  139. BindCtl, verstion 0.1
  140. usage: <module name> <command name> [param1 = value1 [, param2 = value2]]
  141. Type Tab character to get the hint of module/command/paramters.
  142. Type "help(? h)" for help on bindctl.
  143. Type "<module_name> help" for help on the specific module.
  144. Type "<module_name> <command_name> help" for help on the specific command.
  145. Available module names:
  146. help Get help for bindctl
  147. config Configuration commands
  148. Xfrin same here
  149. Auth same here
  150. Boss same here
  151. > config help
  152. Module config Configuration commands
  153. Available commands:
  154. help (Get help for module)
  155. show (Show configuration)
  156. add (Add entry to configuration list)
  157. remove (Remove entry from configuration list)
  158. set (Set a configuration value)
  159. unset (Unset a configuration value)
  160. diff (Show all local changes)
  161. revert (Revert all local changes)
  162. commit (Commit all local changes)
  163. go (Go to a specific configuration part)
  164. > config show
  165. Xfrin/ module
  166. Auth/ module
  167. Boss/ module
  168. > config show Xfrin
  169. transfers_in: 10 integer
  170. > config go Auth
  171. /Auth> config show
  172. database_file: None string
  173. /Auth> config set database_file /tmp/bind10_zones.db
  174. /Auth> config commit
  175. /Auth> config go /
  176. > config show Auth/
  177. database_file: /tmp/bind10_zones.db string
  178. > config diff
  179. {}
  180. > config set Auth/foobar
  181. Error: missing identifier or value
  182. > config set Auth/database_file foobar
  183. > config diff
  184. {'Auth': {'database_file': 'foobar'}}
  185. > config revert
  186. > config diff
  187. {}
  188. > quit