README 6.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222
  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-cmdctl remote control daemon, b10-cfgmgr configuration manager,
  15. b10-xfrin AXFR inbound service, b10-xfrout outgoing AXFR service,
  16. b10-zonemgr secondary manager, b10-stats statistics collection and
  17. reporting daemon, and a new libdns++ library for C++ with a python
  18. 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. The code coverage report for the C++ tests uses LCOV. It is available
  66. from http://ltp.sourceforge.net/. To generate your own HTML report,
  67. first configure BIND 10 with:
  68. ./configure --with-lcov
  69. Doing code coverage tests:
  70. make coverage
  71. Does the following:
  72. make clean-coverage
  73. Zeroes the lcov code coverage counters and removes the coverage HTML.
  74. make perform-coverage
  75. Runs the C++ tests (using googletests framework).
  76. make report-coverage
  77. Generates the coverage HTML, excluding some unrelated headers.
  78. The HTML reports are placed in a directory called coverage/.
  79. DEVELOPERS
  80. The generated run_*.sh scripts available in the src/bin directories
  81. are for running the code using the source tree.
  82. RUNNING
  83. You can start the BIND 10 processes by running bind10 which is
  84. installed to the sbin directory under the installation prefix.
  85. The default location is:
  86. /usr/local/sbin/bind10
  87. For development work, you can also run the bind10 services from the
  88. source tree:
  89. ./src/bin/bind10/run_bind10.sh
  90. (Which will use the modules and configurations also from the source
  91. tree.)
  92. The server will listen on port 5300 for DNS requests.
  93. CONFIGURATION
  94. Commands can be given through the bindctl tool.
  95. The server must be running for bindctl to work.
  96. The following configuration commands are available
  97. help: show the different command modules
  98. <module> help: show the commands for module
  99. <module> <command> help: show info for the command
  100. config show [identifier]: Show the currently set values. If no identifier is
  101. given, the current location is used. If a config
  102. option is a list or a map, the value is not
  103. shown directly, but must be requested separately.
  104. config go [identifier]: Go to the given location within the configuration.
  105. config set [identifier] <value>: Set a configuration value.
  106. config unset [identifier]: Remove a value (reverts to default if the option
  107. is mandatory).
  108. config add [identifier] <value>: add a value to a list
  109. config remove [identifier] <value>: remove a value from a list
  110. config revert: Revert all changes that have not been committed
  111. config commit: Commit all changes
  112. config diff: Show the changes that have not been committed yet
  113. EXAMPLE SESSION
  114. ~> bindctl
  115. ["login success "] login as root
  116. > help
  117. BindCtl, verstion 0.1
  118. usage: <module name> <command name> [param1 = value1 [, param2 = value2]]
  119. Type Tab character to get the hint of module/command/paramters.
  120. Type "help(? h)" for help on bindctl.
  121. Type "<module_name> help" for help on the specific module.
  122. Type "<module_name> <command_name> help" for help on the specific command.
  123. Available module names:
  124. help Get help for bindctl
  125. config Configuration commands
  126. Xfrin same here
  127. Auth same here
  128. Boss same here
  129. > config help
  130. Module config Configuration commands
  131. Available commands:
  132. help (Get help for module)
  133. show (Show configuration)
  134. add (Add entry to configuration list)
  135. remove (Remove entry from configuration list)
  136. set (Set a configuration value)
  137. unset (Unset a configuration value)
  138. diff (Show all local changes)
  139. revert (Revert all local changes)
  140. commit (Commit all local changes)
  141. go (Go to a specific configuration part)
  142. > config show
  143. Xfrin/ module
  144. Auth/ module
  145. Boss/ module
  146. > config show Xfrin
  147. transfers_in: 10 integer
  148. > config go Auth
  149. /Auth> config show
  150. database_file: None string
  151. /Auth> config set database_file /tmp/bind10_zones.db
  152. /Auth> config commit
  153. /Auth> config go /
  154. > config show Auth/
  155. database_file: /tmp/bind10_zones.db string
  156. > config diff
  157. {}
  158. > config set Auth/foobar
  159. Error: missing identifier or value
  160. > config set Auth/database_file foobar
  161. > config diff
  162. {'Auth': {'database_file': 'foobar'}}
  163. > config revert
  164. > config diff
  165. {}
  166. > quit