Home Explore Help
Sign In
zorun
/
kea
1
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Tree: 25747d9b65
Branches Tags
kea
/
doc
/
guide
/
bind10-guide.html

bind10-guide.html 51 KB
History Raw

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681 
  1. <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>BIND 10 Guide</title><link rel="stylesheet" href="./bind10-guide.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><meta name="description" content="BIND 10 is a Domain Name System (DNS) suite managed by Internet Systems Consortium (ISC). It includes DNS libraries and modular components for controlling authoritative and recursive DNS servers. This is the reference guide for BIND 10 version 20110120. The most up-to-date version of this document, along with other documents for BIND 10, can be found at ."></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book" title="BIND 10 Guide"><div class="titlepage"><div><div><h1 class="title"><a name="id1168230298903"></a>BIND 10 Guide</h1></div><div><h2 class="subtitle">Administrator Reference for BIND 10</h2></div><div><p class="releaseinfo">This is the reference guide for BIND 10 version
    2. 

  2.         20110120.</p></div><div><p class="copyright">Copyright © 2010 Internet Systems Consortium, Inc.</p></div><div><div class="abstract" title="Abstract"><p class="title"><b>Abstract</b></p><p>BIND 10 is a Domain Name System (DNS) suite managed by
    3. 

  3. 	Internet Systems Consortium (ISC). It includes DNS libraries
    4. 

  4. 	and modular components for controlling authoritative and
    5. 

  5. 	recursive DNS servers.
    6. 

  6.       </p><p>
    7. 

  7.         This is the reference guide for BIND 10 version 20110120.
    8. 

  8. 	The most up-to-date version of this document, along with
    9. 

  9. 	other documents for BIND 10, can be found at <a class="ulink" href="http://bind10.isc.org/docs" target="_top">http://bind10.isc.org/docs</a>.  </p></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="#intro">1. Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="#id1168230299042">Supported Platforms</a></span></dt><dt><span class="section"><a href="#id1168230299068">Required Software</a></span></dt><dt><span class="section"><a href="#starting_stopping">Starting and Stopping the Server</a></span></dt><dt><span class="section"><a href="#managing_once_running">Managing BIND 10</a></span></dt></dl></dd><dt><span class="chapter"><a href="#installation">2. Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#id1168230284843">Building Requirements</a></span></dt><dt><span class="section"><a href="#quickstart">Quick start</a></span></dt><dt><span class="section"><a href="#install">Installation from source</a></span></dt><dd><dl><dt><span class="section"><a href="#id1168230285029">Download Tar File</a></span></dt><dt><span class="section"><a href="#id1168230285048">Retrieve from Git</a></span></dt><dt><span class="section"><a href="#id1168230285109">Configure before the build</a></span></dt><dt><span class="section"><a href="#id1168230285206">Build</a></span></dt><dt><span class="section"><a href="#id1168230285222">Install</a></span></dt><dt><span class="section"><a href="#id1168230285245">Install Hierarchy</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#bind10">3. Starting BIND10 with <span class="command"><strong>bind10</strong></span></a></span></dt><dd><dl><dt><span class="section"><a href="#start">Starting BIND 10</a></span></dt></dl></dd><dt><span class="chapter"><a href="#msgq">4. Command channel</a></span></dt><dt><span class="chapter"><a href="#cfgmgr">5. Configuration manager</a></span></dt><dt><span class="chapter"><a href="#cmdctl">6. Remote control daemon</a></span></dt><dd><dl><dt><span class="section"><a href="#cmdctl.spec">Configuration specification for b10-cmdctl</a></span></dt></dl></dd><dt><span class="chapter"><a href="#bindctl">7. Control and configure user interface</a></span></dt><dt><span class="chapter"><a href="#authserver">8. Authoritative Server</a></span></dt><dd><dl><dt><span class="section"><a href="#id1168230285821">Server Configurations</a></span></dt><dt><span class="section"><a href="#id1168230285886">Data Source Backends</a></span></dt><dt><span class="section"><a href="#id1168230285917">Loading Master Zones Files</a></span></dt></dl></dd><dt><span class="chapter"><a href="#xfrin">9. Incoming Zone Transfers</a></span></dt><dt><span class="chapter"><a href="#xfrout">10. Outbound Zone Transfers</a></span></dt><dt><span class="chapter"><a href="#zonemgr">11. Secondary Manager</a></span></dt><dt><span class="chapter"><a href="#resolverserver">12. Recursive Name Server</a></span></dt><dt><span class="chapter"><a href="#statistics">13. Statistics</a></span></dt></dl></div><div class="chapter" title="Chapter 1. Introduction"><div class="titlepage"><div><div><h2 class="title"><a name="intro"></a>Chapter 1. Introduction</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id1168230299042">Supported Platforms</a></span></dt><dt><span class="section"><a href="#id1168230299068">Required Software</a></span></dt><dt><span class="section"><a href="#starting_stopping">Starting and Stopping the Server</a></span></dt><dt><span class="section"><a href="#managing_once_running">Managing BIND 10</a></span></dt></dl></div><p>
    10. 

  10.       BIND is the popular implementation of a DNS server, developer
    11. 

  11.       interfaces, and DNS tools.
    12. 

  12.       BIND 10 is a rewrite of BIND 9.  BIND 10 is written in C++ and Python
    13. 

  13.       and provides a modular environment for serving and maintaining DNS.
    14. 

  14.     </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    15. 

  15.         This guide covers the experimental prototype of
    16. 

  16.         BIND 10 version 20110120.
    17. 

  17.       </p></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    18. 

  18.         BIND 10 provides a EDNS0- and DNSSEC-capable
    19. 

  19.         authoritative DNS server and a forwarding DNS server.
    20. 

  20.       </p></div><div class="section" title="Supported Platforms"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168230299042"></a>Supported Platforms</h2></div></div></div><p>
    21. 

  21.   BIND 10 builds have been tested on Debian GNU/Linux 5,
    22. 

  22.   Ubuntu 9.10, NetBSD 5, Solaris 10, FreeBSD 7 and 8, and CentOS
    23. 

  23.   Linux 5.3.
    24. 

  24. 

  25.   It has been tested on Sparc, i386, and amd64 hardware
    26. 

  26.   platforms.
    27. 

  27. 

  28.         It is planned for BIND 10 to build, install and run on
    29. 

  29.         Windows and standard Unix-type platforms.
    30. 

  30.       </p></div><div class="section" title="Required Software"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168230299068"></a>Required Software</h2></div></div></div><p>
    31. 

  31.         BIND 10 requires Python 3.1.  Later versions may work, but Python
    32. 

  32.         3.1 is the minimum version which will work.
    33. 

  33.       </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    34. 

  34. 	For this development prototype release, the only supported
    35. 

  35. 	data source backend is SQLite3. The authoritative server
    36. 

  36. 	requires SQLite 3.3.9 or newer.
    37. 

  37. 	The <span class="command"><strong>b10-xfrin</strong></span>, <span class="command"><strong>b10-xfrout</strong></span>,
    38. 

  38. 	and <span class="command"><strong>b10-zonemgr</strong></span> modules require the
    39. 

  39. 	libpython3 library and the Python _sqlite3.so module.
    40. 

  40.       </p></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    41. 

  41.           Some operating systems do not provide these dependencies
    42. 

  42.           in their default installation nor standard packages
    43. 

  43.           collections.
    44. 

  44.           You may need to install them separately.
    45. 

  45.         </p></div></div><div class="section" title="Starting and Stopping the Server"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="starting_stopping"></a>Starting and Stopping the Server</h2></div></div></div><p>
    46. 

  46.         BIND 10 is modular.  Part of this modularity is
    47. 

  47.         accomplished using multiple cooperating processes which, together,
    48. 

  48. 	provide the server functionality.  This is a change from
    49. 

  49. 	the previous generation of BIND software, which used a
    50. 

  50. 	single process.
    51. 

  51.       </p><p>
    52. 

  52. 	At first, running many different processes may seem confusing.
    53. 

  53. 	However, these processes are started, stopped, and maintained
    54. 

  54. 	by a single command, <span class="command"><strong>bind10</strong></span>.
    55. 

  55. 	This command starts a master process which will start other
    56. 

  56. 	processes as needed.
    57. 

  57. 	The processes started by the <span class="command"><strong>bind10</strong></span>
    58. 

  58. 	command have names starting with "b10-", including:
    59. 

  59.       </p><p>
    60. 

  60. 

  61.         </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
    62. 

  62.               <span class="command"><strong>b10-msgq</strong></span> &#8212;
    63. 

  63.               Message bus daemon.
    64. 

  64.               This process coordinates communication between all of the other
    65. 

  65.               BIND 10 processes.
    66. 

  66.             </li><li class="listitem">
    67. 

  67.               <span class="command"><strong>b10-auth</strong></span> &#8212;
    68. 

  68.               Authoritative DNS server.
    69. 

  69.               This process serves DNS requests.
    70. 

  70.             </li><li class="listitem">
    71. 

  71.               <span class="command"><strong>b10-cfgmgr</strong></span> &#8212;
    72. 

  72.               Configuration manager.
    73. 

  73.               This process maintains all of the configuration for BIND 10.
    74. 

  74.             </li><li class="listitem">
    75. 

  75.               <span class="command"><strong>b10-cmdctl</strong></span> &#8212;
    76. 

  76.               Command and control service.
    77. 

  77.               This process allows external control of the BIND 10 system.
    78. 

  78.             </li><li class="listitem">
    79. 

  79.               <span class="command"><strong>b10-resolver</strong></span> &#8212;
    80. 

  80.               Recursive name server.
    81. 

  81.               This process handles incoming queries.
    82. 

  82. 

  83.             </li><li class="listitem">
    84. 

  84.               <span class="command"><strong>b10-stats</strong></span> &#8212;
    85. 

  85.               Statistics collection daemon.
    86. 

  86.               This process collects and reports statistics data.
    87. 

  87.             </li><li class="listitem">
    88. 

  88.               <span class="command"><strong>b10-xfrin</strong></span> &#8212;
    89. 

  89.               Incoming zone transfer service.
    90. 

  90.               This process is used to transfer a new copy
    91. 

  91.               of a zone into BIND 10, when acting as a secondary server.
    92. 

  92.             </li><li class="listitem">
    93. 

  93.               <span class="command"><strong>b10-xfrout</strong></span> &#8212;
    94. 

  94.               Outgoing zone transfer service.
    95. 

  95. 	      This process is used to handle transfer requests to
    96. 

  96. 	      send a local zone to a remote secondary server,
    97. 

  97. 	      when acting as a master server.
    98. 

  98.             </li><li class="listitem">
    99. 

  99.               <span class="command"><strong>b10-zonemgr</strong></span> &#8212;
    100. 

  100.               Secondary manager.
    101. 

  101. 	      This process keeps track of timers and other
    102. 

  102.               necessary information for BIND 10 to act as a slave server.
    103. 

  103.             </li></ul></div><p>
    104. 

  104.       </p><p>
    105. 

  105. 	These are ran automatically by <span class="command"><strong>bind10</strong></span>
    106. 

  106. 	and do not need to be run manually.
    107. 

  107.       </p></div><div class="section" title="Managing BIND 10"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="managing_once_running"></a>Managing BIND 10</h2></div></div></div><p>
    108. 

  108. 	Once BIND 10 is running, a few commands are used to interact
    109. 

  109. 	directly with the system:
    110. 

  110.         </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
    111. 

  111.               <span class="command"><strong>bindctl</strong></span> &#8212;
    112. 

  112.               interactive administration interface.
    113. 

  113.               This is a command-line tool which allows an administrator
    114. 

  114.               to control BIND 10.
    115. 

  115.             </li><li class="listitem">
    116. 

  116.               <span class="command"><strong>b10-loadzone</strong></span> &#8212;
    117. 

  117.               zone file loader.
    118. 

  118.               This tool will load standard masterfile-format zone files into
    119. 

  119.               BIND 10.
    120. 

  120.             </li><li class="listitem">
    121. 

  121.               <span class="command"><strong>b10-cmdctl-usermgr</strong></span> &#8212;
    122. 

  122.               user access control.
    123. 

  123.               This tool allows an administrator to authorize additional users
    124. 

  124.               to manage BIND 10.
    125. 

  125.             </li></ul></div><p>
    126. 

  126.       </p></div><p>
    127. 

  127.       The tools and modules are covered in full detail in this guide.
    128. 

  128. 

  129.       In addition, manual pages are also provided in the default installation.
    130. 

  130.     </p><p>
    131. 

  131.       BIND 10 also provides libraries and programmer interfaces
    132. 

  132.       for C++ and Python for the message bus, configuration backend,
    133. 

  133.       and, of course, DNS. These include detailed developer
    134. 

  134.       documentation and code examples.
    135. 

  135. 

  136.     </p></div><div class="chapter" title="Chapter 2. Installation"><div class="titlepage"><div><div><h2 class="title"><a name="installation"></a>Chapter 2. Installation</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id1168230284843">Building Requirements</a></span></dt><dt><span class="section"><a href="#quickstart">Quick start</a></span></dt><dt><span class="section"><a href="#install">Installation from source</a></span></dt><dd><dl><dt><span class="section"><a href="#id1168230285029">Download Tar File</a></span></dt><dt><span class="section"><a href="#id1168230285048">Retrieve from Git</a></span></dt><dt><span class="section"><a href="#id1168230285109">Configure before the build</a></span></dt><dt><span class="section"><a href="#id1168230285206">Build</a></span></dt><dt><span class="section"><a href="#id1168230285222">Install</a></span></dt><dt><span class="section"><a href="#id1168230285245">Install Hierarchy</a></span></dt></dl></dd></dl></div><div class="section" title="Building Requirements"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168230284843"></a>Building Requirements</h2></div></div></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    137. 

  137.             Some operating systems have split their distribution packages into
    138. 

  138.             a run-time and a development package.  You will need to install
    139. 

  139.             the development package versions, which include header files and
    140. 

  140.             libraries, to build BIND 10 from source code.
    141. 

  141.           </p></div><p>
    142. 

  142.           Building from source code requires the Boost
    143. 

  143.           build-time headers. At least Boost version 1.35 is required.
    144. 

  144.   
    145. 

  145.   
    146. 

  146.         </p><p>
    147. 

  147. 	  The Python Library and Python _sqlite3 module are required to
    148. 

  148.           enable the Xfrout and Xfrin support.
    149. 

  149.         </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    150. 

  150.           The Python related libraries and modules need to be built
    151. 

  151.           for Python 3.1.
    152. 

  152.         </p></div><p>
    153. 

  153.           Building BIND 10 also requires a C++ compiler and
    154. 

  154.           standard development headers, make, and pkg-config.
    155. 

  155.           BIND 10 builds have been tested with GCC g++ 3.4.3, 4.1.2,
    156. 

  156.           4.1.3, 4.2.1, 4.3.2, and 4.4.1.
    157. 

  157.         </p></div><div class="section" title="Quick start"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="quickstart"></a>Quick start</h2></div></div></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    158. 

  158.           This quickly covers the standard steps for installing
    159. 

  159.           and deploying BIND 10 as an authoritative name server using
    160. 

  160.           its defaults. For troubleshooting, full customizations and further
    161. 

  161.           details, see the respective chapters in the BIND 10 guide.
    162. 

  162.         </p></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    163. 

  163.           The development prototype of the b10-auth server listens on
    164. 

  164.           0.0.0.0 (all interfaces) port 5300. (This is not the standard
    165. 

  165.           domain service port.)
    166. 

  166.         </p></div><p>
    167. 

  167.         To quickly get started with BIND 10, follow these steps.
    168. 

  168.       </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
    169. 

  169.             Install required build dependencies.
    170. 

  170.           </li><li class="listitem">
    171. 

  171.             Download the BIND 10 source tar file from
    172. 

  172.             <a class="ulink" href="ftp://ftp.isc.org/isc/bind10/" target="_top">ftp://ftp.isc.org/isc/bind10/</a>.
    173. 

  173.           </li><li class="listitem"><p>Extract the tar file:
    174. 

  174.           </p><pre class="screen">$ <strong class="userinput"><code>gzcat bind10-<em class="replaceable"><code>VERSION</code></em>.tar.gz | tar -xvf -</code></strong></pre><p>
    175. 

  175.           </p></li><li class="listitem"><p>Go into the source and run configure:
    176. 

  176.             </p><pre class="screen">$ <strong class="userinput"><code>cd bind10-<em class="replaceable"><code>VERSION</code></em></code></strong>
    177. 

  177.   $ <strong class="userinput"><code>./configure</code></strong></pre><p>
    178. 

  178.           </p></li><li class="listitem"><p>Build it:
    179. 

  179.             </p><pre class="screen">$ <strong class="userinput"><code>make</code></strong></pre><p>
    180. 

  180.           </p></li><li class="listitem"><p>Install it (to default /usr/local):
    181. 

  181.             </p><pre class="screen">$ <strong class="userinput"><code>make install</code></strong></pre><p>
    182. 

  182.           </p></li><li class="listitem"><p>Start the server:
    183. 

  183.             </p><pre class="screen">$ <strong class="userinput"><code>/usr/local/sbin/bind10</code></strong></pre><p>
    184. 

  184.           </p></li><li class="listitem"><p>Test it; for example:
    185. 

  185.             </p><pre class="screen">$ <strong class="userinput"><code>dig @127.0.0.1 -p 5300 -c CH -t TXT authors.bind</code></strong></pre><p>
    186. 

  186.          </p></li><li class="listitem"><p>Load desired zone file(s), for example:
    187. 

  187.             </p><pre class="screen">$ <strong class="userinput"><code>b10-loadzone <em class="replaceable"><code>your.zone.example.org</code></em></code></strong></pre><p>
    188. 

  188.           </p></li><li class="listitem">
    189. 

  189.             Test the new zone.
    190. 

  190.           </li></ol></div></div><div class="section" title="Installation from source"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="install"></a>Installation from source</h2></div></div></div><p>
    191. 

  191.         BIND 10 is open source software written in C++ and Python.
    192. 

  192.         It is freely available in source code form from ISC via
    193. 

  193.         the Git code revision control system or as a downloadable
    194. 

  194.         tar file. It may also be available in pre-compiled ready-to-use
    195. 

  195.         packages from operating system vendors.
    196. 

  196.       </p><div class="section" title="Download Tar File"><div class="titlepage"><div><div><h3 class="title"><a name="id1168230285029"></a>Download Tar File</h3></div></div></div><p>
    197. 

  197.           Downloading a release tar file is the recommended method to
    198. 

  198.           obtain the source code.
    199. 

  199.         </p><p>
    200. 

  200.           The BIND 10 releases are available as tar file downloads from
    201. 

  201.           <a class="ulink" href="ftp://ftp.isc.org/isc/bind10/" target="_top">ftp://ftp.isc.org/isc/bind10/</a>.
    202. 

  202.           Periodic development snapshots may also be available.
    203. 

  203.         </p></div><div class="section" title="Retrieve from Git"><div class="titlepage"><div><div><h3 class="title"><a name="id1168230285048"></a>Retrieve from Git</h3></div></div></div><p>
    204. 

  204.           Downloading this "bleeding edge" code is recommended only for
    205. 

  205.           developers or advanced users.  Using development code in a production
    206. 

  206.           environment is not recommended.
    207. 

  207.         </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    208. 

  208.             When using source code retrieved via Git additional
    209. 

  209.             software will be required:  automake (v1.11 or newer),
    210. 

  210.             libtoolize, and autoconf (2.59 or newer).
    211. 

  211.             These may need to be installed.
    212. 

  212.           </p></div><p>
    213. 

  213.           The latest development code, including temporary experiments
    214. 

  214.           and un-reviewed code, is available via the BIND 10 code revision
    215. 

  215.           control system. This is powered by Git and all the BIND 10
    216. 

  216.           development is public.
    217. 

  217.           The leading development is done in the <span class="quote">&#8220;<span class="quote">master</span>&#8221;</span>.
    218. 

  218.         </p><p>
    219. 

  219.           The code can be checked out from
    220. 

  220.           <code class="filename">git://bind10.isc.org/bind10</code>;
    221. 

  221.           for example:
    222. 

  222. 

  223.         </p><pre class="screen">$ <strong class="userinput"><code>git clone git://bind10.isc.org/bind10</code></strong></pre><p>
    224. 

  224.         </p><p>
    225. 

  225.           When checking out the code from
    226. 

  226.           the code version control system, it doesn't include the
    227. 

  227.           generated configure script, Makefile.in files, nor the
    228. 

  228.           related configure files.
    229. 

  229.           They can be created by running <span class="command"><strong>autoreconf</strong></span>
    230. 

  230.           with the <code class="option">--install</code> switch.
    231. 

  231.           This will run <span class="command"><strong>autoconf</strong></span>,
    232. 

  232.           <span class="command"><strong>aclocal</strong></span>,
    233. 

  233.           <span class="command"><strong>libtoolize</strong></span>,
    234. 

  234.           <span class="command"><strong>autoheader</strong></span>,
    235. 

  235.           <span class="command"><strong>automake</strong></span>,
    236. 

  236.           and related commands.
    237. 

  237.         </p></div><div class="section" title="Configure before the build"><div class="titlepage"><div><div><h3 class="title"><a name="id1168230285109"></a>Configure before the build</h3></div></div></div><p>
    238. 

  238.           BIND 10 uses the GNU Build System to discover build environment
    239. 

  239.           details.
    240. 

  240.           To generate the makefiles using the defaults, simply run:
    241. 

  241.           </p><pre class="screen">$ <strong class="userinput"><code>./configure</code></strong></pre><p>
    242. 

  242.         </p><p>
    243. 

  243.           Run <span class="command"><strong>./configure</strong></span> with the <code class="option">--help</code>
    244. 

  244.           switch to view the different options. The commonly-used options are:
    245. 

  245. 

  246.           </p><div class="variablelist"><dl><dt><span class="term">--prefix</span></dt><dd>Define the the installation location (the
    247. 

  247.                 default is <code class="filename">/usr/local/</code>).
    248. 

  248.               </dd><dt><span class="term">--with-boost-include</span></dt><dd>Define the path to find the Boost headers.
    249. 

  249.               </dd><dt><span class="term">--with-pythonpath</span></dt><dd>Define the path to Python 3.1 if it is not in the
    250. 

  250.                 standard execution path.
    251. 

  251.               </dd><dt><span class="term">--with-gtest</span></dt><dd>Enable building the C++ Unit Tests using the
    252. 

  252.                 Google Tests framework. Optionally this can define the
    253. 

  253.                 path to the gtest header files and library.
    254. 

  254.               </dd></dl></div><p>
    255. 

  255. 

  256.         </p><p>
    257. 

  257.           For example, the following configures it to
    258. 

  258.     find the Boost headers, find the
    259. 

  259.     Python interpreter, and sets the installation location:
    260. 

  260. 

  261.           </p><pre class="screen">$ <strong class="userinput"><code>./configure \
    262. 

  262.       --with-boost-include=/usr/pkg/include \
    263. 

  263.       --with-pythonpath=/usr/pkg/bin/python3.1 \
    264. 

  264.       --prefix=/opt/bind10</code></strong></pre><p>
    265. 

  265.         </p><p>
    266. 

  266.           If the configure fails, it may be due to missing or old
    267. 

  267.           dependencies.
    268. 

  268.         </p></div><div class="section" title="Build"><div class="titlepage"><div><div><h3 class="title"><a name="id1168230285206"></a>Build</h3></div></div></div><p>
    269. 

  269.     After the configure step is complete, to build the executables
    270. 

  270.     from the C++ code and prepare the Python scripts, run:
    271. 

  271. 

  272.           </p><pre class="screen">$ <strong class="userinput"><code>make</code></strong></pre><p>
    273. 

  273.         </p></div><div class="section" title="Install"><div class="titlepage"><div><div><h3 class="title"><a name="id1168230285222"></a>Install</h3></div></div></div><p>
    274. 

  274.           To install the BIND 10 executables, support files,
    275. 

  275.           and documentation, run:
    276. 

  276.           </p><pre class="screen">$ <strong class="userinput"><code>make install</code></strong></pre><p>
    277. 

  277.         </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The install step may require superuser privileges.</p></div></div><div class="section" title="Install Hierarchy"><div class="titlepage"><div><div><h3 class="title"><a name="id1168230285245"></a>Install Hierarchy</h3></div></div></div><p>
    278. 

  278.           The following is the layout of the complete BIND 10 installation:
    279. 

  279.           </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
    280. 

  280.                 <code class="filename">bin/</code> &#8212;
    281. 

  281.                 general tools and diagnostic clients.
    282. 

  282.               </li><li class="listitem">
    283. 

  283.               <code class="filename">etc/bind10-devel/</code> &#8212;
    284. 

  284.               configuration files.
    285. 

  285.             </li><li class="listitem">
    286. 

  286.                 <code class="filename">lib/</code> &#8212;
    287. 

  287.                 libraries and python modules.
    288. 

  288.               </li><li class="listitem">
    289. 

  289.                 <code class="filename">libexec/bind10-devel/</code> &#8212;
    290. 

  290.                 executables that a user wouldn't normally run directly and
    291. 

  291.                 are not run independently.
    292. 

  292.                 These are the BIND 10 modules which are daemons started by
    293. 

  293.                 the <span class="command"><strong>bind10</strong></span> tool.
    294. 

  294.               </li><li class="listitem">
    295. 

  295.                 <code class="filename">sbin/</code> &#8212;
    296. 

  296.                 commands used by the system administrator.
    297. 

  297.               </li><li class="listitem">
    298. 

  298.                 <code class="filename">share/bind10-devel/</code> &#8212;
    299. 

  299.                 configuration specifications.
    300. 

  300.               </li><li class="listitem">
    301. 

  301.                 <code class="filename">share/man/</code> &#8212;
    302. 

  302.                 manual pages (online documentation).
    303. 

  303.               </li><li class="listitem">
    304. 

  304.                 <code class="filename">var/bind10-devel/</code> &#8212;
    305. 

  305.                 data source and configuration databases.
    306. 

  306.               </li></ul></div><p>
    307. 

  307.         </p></div></div></div><div class="chapter" title="Chapter 3. Starting BIND10 with bind10"><div class="titlepage"><div><div><h2 class="title"><a name="bind10"></a>Chapter 3. Starting BIND10 with <span class="command"><strong>bind10</strong></span></h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#start">Starting BIND 10</a></span></dt></dl></div><p>
    308. 

  308.       BIND 10 provides the <span class="command"><strong>bind10</strong></span> command which 
    309. 

  309.       starts up the required processes.
    310. 

  310.       <span class="command"><strong>bind10</strong></span>
    311. 

  311.       will also restart processes that exit unexpectedly.
    312. 

  312.       This is the only command needed to start the BIND 10 system.
    313. 

  313.     </p><p>
    314. 

  314.       After starting the <span class="command"><strong>b10-msgq</strong></span> communications channel,
    315. 

  315.       <span class="command"><strong>bind10</strong></span> connects to it, 
    316. 

  316.       runs the configuration manager, and reads its own configuration.
    317. 

  317.       Then it starts the other modules.
    318. 

  318.     </p><p>
    319. 

  319.       The <span class="command"><strong>b10-msgq</strong></span> and <span class="command"><strong>b10-cfgmgr</strong></span>
    320. 

  320.       services make up the core. The <span class="command"><strong>b10-msgq</strong></span> daemon
    321. 

  321.       provides the communication channel between every part of the system.
    322. 

  322.       The <span class="command"><strong>b10-cfgmgr</strong></span> daemon is always needed by every
    323. 

  323.       module, if only to send information about themselves somewhere,
    324. 

  324.       but more importantly to ask about their own settings, and
    325. 

  325.       about other modules.
    326. 

  326.       The <span class="command"><strong>bind10</strong></span> master process will also start up
    327. 

  327.       <span class="command"><strong>b10-cmdctl</strong></span> for admins to communicate with the
    328. 

  328.       system, <span class="command"><strong>b10-auth</strong></span> for authoritative DNS service or
    329. 

  329.       <span class="command"><strong>b10-resolver</strong></span> for recursive name service,
    330. 

  330.       <span class="command"><strong>b10-stats</strong></span> for statistics collection,
    331. 

  331.       <span class="command"><strong>b10-xfrin</strong></span> for inbound DNS zone transfers,
    332. 

  332.       <span class="command"><strong>b10-xfrout</strong></span> for outbound DNS zone transfers,
    333. 

  333.       and <span class="command"><strong>b10-zonemgr</strong></span> for secondary service.
    334. 

  334.     </p><div class="section" title="Starting BIND 10"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="start"></a>Starting BIND 10</h2></div></div></div><p>
    335. 

  335.         To start the BIND 10 service, simply run <span class="command"><strong>bind10</strong></span>.
    336. 

  336.         Run it with the <code class="option">--verbose</code> switch to
    337. 

  337.         get additional debugging or diagnostic output.
    338. 

  338.       </p></div></div><div class="chapter" title="Chapter 4. Command channel"><div class="titlepage"><div><div><h2 class="title"><a name="msgq"></a>Chapter 4. Command channel</h2></div></div></div><p>
    339. 

  339.         The BIND 10 components use the <span class="command"><strong>b10-msgq</strong></span>
    340. 

  340.         message routing daemon to communicate with other BIND 10 components.
    341. 

  341.         The <span class="command"><strong>b10-msgq</strong></span> implements what is called the
    342. 

  342.         <span class="quote">&#8220;<span class="quote">Command Channel</span>&#8221;</span>.
    343. 

  343.         Processes intercommunicate by sending messages on the command
    344. 

  344.         channel.
    345. 

  345.         Example messages include shutdown, get configurations, and set
    346. 

  346.         configurations.
    347. 

  347.         This Command Channel is not used for DNS message passing.
    348. 

  348.         It is used only to control and monitor the BIND 10 system.
    349. 

  349.       </p><p>
    350. 

  350.         Administrators do not communicate directly with the
    351. 

  351.         <span class="command"><strong>b10-msgq</strong></span> daemon.
    352. 

  352.         By default, BIND 10 uses port 9912 for the
    353. 

  353.         <span class="command"><strong>b10-msgq</strong></span> service.
    354. 

  354.         It listens on 127.0.0.1.
    355. 

  355.       </p></div><div class="chapter" title="Chapter 5. Configuration manager"><div class="titlepage"><div><div><h2 class="title"><a name="cfgmgr"></a>Chapter 5. Configuration manager</h2></div></div></div><p>
    356. 

  356.          The configuration manager, <span class="command"><strong>b10-cfgmgr</strong></span>,
    357. 

  357.          handles all BIND 10 system configuration.  It provides
    358. 

  358.          persistent storage for configuration, and notifies running
    359. 

  359.          modules of configuration changes.
    360. 

  360.       </p><p>
    361. 

  361.         The <span class="command"><strong>b10-auth</strong></span> and <span class="command"><strong>b10-xfrin</strong></span>
    362. 

  362.         daemons and other components receive their configurations
    363. 

  363.         from the configuration manager over the <span class="command"><strong>b10-msgq</strong></span>
    364. 

  364.         command channel.
    365. 

  365.       </p><p>The administrator doesn't connect to it directly, but
    366. 

  366.         uses a user interface to communicate with the configuration
    367. 

  367.         manager via <span class="command"><strong>b10-cmdctl</strong></span>'s REST-ful interface.
    368. 

  368.         <span class="command"><strong>b10-cmdctl</strong></span> is covered in <a class="xref" href="#cmdctl" title="Chapter 6. Remote control daemon">Chapter 6, <i>Remote control daemon</i></a>.
    369. 

  369.       </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    370. 

  370.           The development prototype release only provides the
    371. 

  371.           <span class="command"><strong>bindctl</strong></span> as a user interface to
    372. 

  372.           <span class="command"><strong>b10-cmdctl</strong></span>.
    373. 

  373.           Upcoming releases will provide another interactive command-line
    374. 

  374.           interface and a web-based interface.
    375. 

  375.         </p></div><p>
    376. 

  376.         The <span class="command"><strong>b10-cfgmgr</strong></span> daemon can send all
    377. 

  377.         specifications and all current settings to the
    378. 

  378.         <span class="command"><strong>bindctl</strong></span> client (via
    379. 

  379.         <span class="command"><strong>b10-cmdctl</strong></span>).
    380. 

  380.       </p><p>
    381. 

  381.         <span class="command"><strong>b10-cfgmgr</strong></span> relays configurations received
    382. 

  382.         from <span class="command"><strong>b10-cmdctl</strong></span> to the appropriate modules.
    383. 

  383.       </p><p>
    384. 

  384.         The stored configuration file is at
    385. 

  385.         <code class="filename">/usr/local/var/bind10-devel/b10-config.db</code>.
    386. 

  386.         (The full path is what was defined at build configure time for
    387. 

  387.         <code class="option">--localstatedir</code>.
    388. 

  388.         The default is <code class="filename">/usr/local/var/</code>.)
    389. 

  389.         The format is loosely based on JSON and is directly parseable
    390. 

  390.         python, but this may change in a future version.
    391. 

  391.         This configuration data file is not manually edited by the
    392. 

  392.         administrator.
    393. 

  393.       </p><p>
    394. 

  394.       The configuration manager does not have any command line arguments.
    395. 

  395.       Normally it is not started manually, but is automatically
    396. 

  396.       started using the <span class="command"><strong>bind10</strong></span> master process
    397. 

  397.       (as covered in <a class="xref" href="#bind10" title="Chapter 3. Starting BIND10 with bind10">Chapter 3, <i>Starting BIND10 with <span class="command"><strong>bind10</strong></span></i></a>).
    398. 

  398.     </p></div><div class="chapter" title="Chapter 6. Remote control daemon"><div class="titlepage"><div><div><h2 class="title"><a name="cmdctl"></a>Chapter 6. Remote control daemon</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#cmdctl.spec">Configuration specification for b10-cmdctl</a></span></dt></dl></div><p>
    399. 

  399.       <span class="command"><strong>b10-cmdctl</strong></span> is the gateway between
    400. 

  400.       administrators and the BIND 10 system.
    401. 

  401.       It is a HTTPS server that uses standard HTTP Digest
    402. 

  402.       Authentication for username and password validation.
    403. 

  403.       It provides a REST-ful interface for accessing and controlling
    404. 

  404.       BIND 10.
    405. 

  405.     </p><p>
    406. 

  406.       When <span class="command"><strong>b10-cmdctl</strong></span> starts, it firsts
    407. 

  407.       asks <span class="command"><strong>b10-cfgmgr</strong></span> about what modules are
    408. 

  408.       running and what their configuration is (over the
    409. 

  409.       <span class="command"><strong>b10-msgq</strong></span> channel). Then it will start listening
    410. 

  410.       on HTTPS for clients &#8212; the user interface &#8212; such
    411. 

  411.       as <span class="command"><strong>bindctl</strong></span>.
    412. 

  412.     </p><p>
    413. 

  413.       <span class="command"><strong>b10-cmdctl</strong></span> directly sends commands
    414. 

  414.       (received from the user interface) to the specified component.
    415. 

  415.       Configuration changes are actually commands to
    416. 

  416.       <span class="command"><strong>b10-cfgmgr</strong></span> so are sent there.
    417. 

  417.     </p><p>The HTTPS server requires a private key,
    418. 

  418.       such as a RSA PRIVATE KEY.
    419. 

  419.       The default location is at
    420. 

  420.       <code class="filename">/usr/local/etc/bind10-devel/cmdctl-keyfile.pem</code>.
    421. 

  421.       (A sample key is at
    422. 

  422.       <code class="filename">/usr/local/share/bind10-devel/cmdctl-keyfile.pem</code>.)
    423. 

  423.       It also uses a certificate located at
    424. 

  424.       <code class="filename">/usr/local/etc/bind10-devel/cmdctl-certfile.pem</code>.
    425. 

  425.       (A sample certificate is at
    426. 

  426.       <code class="filename">/usr/local/share/bind10-devel/cmdctl-certfile.pem</code>.)
    427. 

  427.       This may be a self-signed certificate or purchased from a
    428. 

  428.       certification authority.
    429. 

  429.     </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    430. 

  430.       The HTTPS server doesn't support a certificate request from a
    431. 

  431.       client (at this time).
    432. 

  432. 

  433.       The <span class="command"><strong>b10-cmdctl</strong></span> daemon does not provide a
    434. 

  434.       public service. If any client wants to control BIND 10, then
    435. 

  435.       a certificate needs to be first received from the BIND 10
    436. 

  436.       administrator.
    437. 

  437.       The BIND 10 installation provides a sample PEM bundle that matches
    438. 

  438.       the sample key and certificate.
    439. 

  439.     </p></div><p>
    440. 

  440.       The <span class="command"><strong>b10-cmdctl</strong></span> daemon also requires
    441. 

  441.       the user account file located at
    442. 

  442.       <code class="filename">/usr/local/etc/bind10-devel/cmdctl-accounts.csv</code>.
    443. 

  443.       This comma-delimited file lists the accounts with a user name,
    444. 

  444.       hashed password, and salt.
    445. 

  445.       (A sample file is at
    446. 

  446.       <code class="filename">/usr/local/share/bind10-devel/cmdctl-accounts.csv</code>.
    447. 

  447.       It contains the user named <span class="quote">&#8220;<span class="quote">root</span>&#8221;</span> with the password
    448. 

  448.       <span class="quote">&#8220;<span class="quote">bind10</span>&#8221;</span>.)
    449. 

  449.     </p><p>
    450. 

  450.       The administrator may create a user account with the
    451. 

  451.       <span class="command"><strong>b10-cmdctl-usermgr</strong></span> tool.
    452. 

  452.     </p><p>
    453. 

  453.       By default the HTTPS server listens on the localhost port 8080.
    454. 

  454.       The port can be set by using the <code class="option">--port</code> command line option.
    455. 

  455.       The address to listen on can be set using the <code class="option">--address</code> command
    456. 

  456.       line argument.
    457. 

  457.       Each HTTPS connection is stateless and timesout in 1200 seconds
    458. 

  458.       by default.  This can be
    459. 

  459.       redefined by using the <code class="option">--idle-timeout</code> command line argument.
    460. 

  460.     </p><div class="section" title="Configuration specification for b10-cmdctl"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cmdctl.spec"></a>Configuration specification for b10-cmdctl</h2></div></div></div><p>
    461. 

  461.         The configuration items for <span class="command"><strong>b10-cmdctl</strong></span> are:
    462. 

  462. key_file
    463. 

  463. cert_file
    464. 

  464. accounts_file
    465. 

  465.       </p><p>
    466. 

  466.         The control commands are:
    467. 

  467. print_settings
    468. 

  468. shutdown
    469. 

  469.       </p></div></div><div class="chapter" title="Chapter 7. Control and configure user interface"><div class="titlepage"><div><div><h2 class="title"><a name="bindctl"></a>Chapter 7. Control and configure user interface</h2></div></div></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    470. 

  470.       For this development prototype release, <span class="command"><strong>bindctl</strong></span>
    471. 

  471.       is the only user interface. It is expected that upcoming
    472. 

  472.       releases will provide another interactive command-line
    473. 

  473.       interface and a web-based interface for controlling and
    474. 

  474.       configuring BIND 10.
    475. 

  475.     </p></div><p>
    476. 

  476.       The <span class="command"><strong>bindctl</strong></span> tool provides an interactive
    477. 

  477.       prompt for configuring, controlling, and querying the BIND 10
    478. 

  478.       components.
    479. 

  479.       It communicates directly with a REST-ful interface over HTTPS
    480. 

  480.       provided by <span class="command"><strong>b10-cmdctl</strong></span>. It doesn't
    481. 

  481.       communicate to any other components directly.
    482. 

  482.     </p><p>
    483. 

  483.       Configuration changes are actually commands to
    484. 

  484.       <span class="command"><strong>b10-cfgmgr</strong></span>. So when <span class="command"><strong>bindctl</strong></span>
    485. 

  485.       sends a configuration, it is sent to <span class="command"><strong>b10-cmdctl</strong></span>
    486. 

  486.       (over a HTTPS connection); then <span class="command"><strong>b10-cmdctl</strong></span>
    487. 

  487.       sends the command (over a <span class="command"><strong>b10-msgq</strong></span> command
    488. 

  488.       channel) to <span class="command"><strong>b10-cfgmgr</strong></span> which then stores
    489. 

  489.       the details and relays (over a <span class="command"><strong>b10-msgq</strong></span> command
    490. 

  490.       channel) the configuration on to the specified module.
    491. 

  491.     </p><p>
    492. 

  492.     </p></div><div class="chapter" title="Chapter 8. Authoritative Server"><div class="titlepage"><div><div><h2 class="title"><a name="authserver"></a>Chapter 8. Authoritative Server</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id1168230285821">Server Configurations</a></span></dt><dt><span class="section"><a href="#id1168230285886">Data Source Backends</a></span></dt><dt><span class="section"><a href="#id1168230285917">Loading Master Zones Files</a></span></dt></dl></div><p>
    493. 

  493.       The <span class="command"><strong>b10-auth</strong></span> is the authoritative DNS server.
    494. 

  494.       It supports EDNS0 and DNSSEC. It supports IPv6.
    495. 

  495.       Normally it is started by the <span class="command"><strong>bind10</strong></span> master
    496. 

  496.       process.
    497. 

  497.     </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    498. 

  498.       This development prototype release listens on all interfaces
    499. 

  499.       and the non-standard port 5300.
    500. 

  500.     </p></div><div class="section" title="Server Configurations"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168230285821"></a>Server Configurations</h2></div></div></div><p>
    501. 

  501.         <span class="command"><strong>b10-auth</strong></span> is configured via the
    502. 

  502.         <span class="command"><strong>b10-cfgmgr</strong></span> configuration manager.
    503. 

  503.         The module name is <span class="quote">&#8220;<span class="quote">Auth</span>&#8221;</span>.
    504. 

  504.         The configuration data item is:
    505. 

  505. 

  506.         </p><div class="variablelist"><dl><dt><span class="term">database_file</span></dt><dd>This is an optional string to define the path to find
    507. 

  507.                  the SQLite3 database file.
    508. 

  508. 

  509. Note: Later the DNS server will use various data source backends.
    510. 

  510. This may be a temporary setting until then.
    511. 

  511.               </dd></dl></div><p>
    512. 

  512. 

  513.       </p><p>
    514. 

  514. 

  515.         The configuration command is:
    516. 

  516. 

  517.         </p><div class="variablelist"><dl><dt><span class="term">shutdown</span></dt><dd>Stop the authoritative DNS server.
    518. 

  518.               </dd></dl></div><p>
    519. 

  519. 

  520.       </p></div><div class="section" title="Data Source Backends"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168230285886"></a>Data Source Backends</h2></div></div></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    521. 

  521.         For the development prototype release, <span class="command"><strong>b10-auth</strong></span>
    522. 

  522.         only supports the SQLite3 data source backend.
    523. 

  523.         Upcoming versions will be able to use multiple different
    524. 

  524.         data sources, such as MySQL, Berkeley DB, or in-memory DB.
    525. 

  525.       </p></div><p>
    526. 

  526.         By default, the SQLite3 backend uses the data file located at
    527. 

  527.         <code class="filename">/usr/local/var/bind10-devel/zone.sqlite3</code>.
    528. 

  528.         (The full path is what was defined at build configure time for
    529. 

  529.         <code class="option">--localstatedir</code>.
    530. 

  530.         The default is <code class="filename">/usr/local/var/</code>.)
    531. 

  531.   This data file location may be changed by defining the
    532. 

  532.   <span class="quote">&#8220;<span class="quote">database_file</span>&#8221;</span> configuration.
    533. 

  533.       </p></div><div class="section" title="Loading Master Zones Files"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168230285917"></a>Loading Master Zones Files</h2></div></div></div><p>
    534. 

  534.         RFC 1035 style DNS master zone files may imported
    535. 

  535.         into a BIND 10 data source by using the
    536. 

  536.         <span class="command"><strong>b10-loadzone</strong></span> utility.
    537. 

  537.       </p><p>
    538. 

  538.         <span class="command"><strong>b10-loadzone</strong></span> supports the following
    539. 

  539.         special directives (control entries):
    540. 

  540. 

  541.         </p><div class="variablelist"><dl><dt><span class="term">$INCLUDE</span></dt><dd>Loads an additional zone file. This may be recursive.
    542. 

  542.               </dd><dt><span class="term">$ORIGIN</span></dt><dd>Defines the relative domain name.
    543. 

  543.               </dd><dt><span class="term">$TTL</span></dt><dd>Defines the time-to-live value used for following
    544. 

  544.                 records that don't include a TTL.
    545. 

  545.               </dd></dl></div><p>
    546. 

  546. 

  547.       </p><p>
    548. 

  548.         The <code class="option">-o</code> argument may be used to define the
    549. 

  549.         default origin for loaded zone file records.
    550. 

  550.       </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    551. 

  551.         In the development prototype release, only the SQLite3 back
    552. 

  552.         end is used.
    553. 

  553.         By default, it stores the zone data in
    554. 

  554.         <code class="filename">/usr/local/var/bind10-devel/zone.sqlite3</code>
    555. 

  555.         unless the <code class="option">-d</code> switch is used to set the
    556. 

  556.         database filename.
    557. 

  557.         Multiple zones are stored in a single SQLite3 zone database.
    558. 

  558.       </p></div><p>
    559. 

  559.         If you reload a zone already existing in the database,
    560. 

  560.         all records from that prior zone disappear and a whole new set
    561. 

  561.         appears.
    562. 

  562.       </p></div></div><div class="chapter" title="Chapter 9. Incoming Zone Transfers"><div class="titlepage"><div><div><h2 class="title"><a name="xfrin"></a>Chapter 9. Incoming Zone Transfers</h2></div></div></div><p>
    563. 

  563.       The <span class="command"><strong>b10-xfrin</strong></span> process is started by
    564. 

  564.       <span class="command"><strong>bind10</strong></span>.
    565. 

  565.       It can be manually triggered to request an AXFR zone
    566. 

  566.       transfer. When received, it is stored in the BIND 10
    567. 

  567.       data store, and its records can be served by
    568. 

  568.       <span class="command"><strong>b10-auth</strong></span>.
    569. 

  569.       In combination with <span class="command"><strong>b10-zonemgr</strong></span> (for
    570. 

  570.       automated SOA checks), this allows the BIND 10 server to
    571. 

  571.       provide <span class="quote">&#8220;<span class="quote">secondary</span>&#8221;</span> service.
    572. 

  572.     </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    573. 

  573.      The current development release of BIND 10 only supports
    574. 

  574.      AXFR. (IXFR is not supported.) 
    575. 

  575.     </p></div><p>
    576. 

  576.        To manually trigger a zone transfer to retrieve a remote zone,
    577. 

  577.        you may use the <span class="command"><strong>bindctl</strong></span> utility.
    578. 

  578.        For example, at the <span class="command"><strong>bindctl</strong></span> prompt run:
    579. 

  579. 

  580.        </p><pre class="screen">&gt; <strong class="userinput"><code>Xfrin retransfer zone_name="<code class="option">foo.example.org</code>" master=<code class="option">192.0.2.99</code></code></strong></pre><p>
    581. 

  581.     </p></div><div class="chapter" title="Chapter 10. Outbound Zone Transfers"><div class="titlepage"><div><div><h2 class="title"><a name="xfrout"></a>Chapter 10. Outbound Zone Transfers</h2></div></div></div><p>
    582. 

  582.       The <span class="command"><strong>b10-xfrout</strong></span> process is started by
    583. 

  583.       <span class="command"><strong>bind10</strong></span>.
    584. 

  584.       When the <span class="command"><strong>b10-auth</strong></span> authoritative DNS server
    585. 

  585.       receives an AXFR request, <span class="command"><strong>b10-xfrout</strong></span>
    586. 

  586.       sends the zone.
    587. 

  587.       This is used to provide master DNS service to share zones
    588. 

  588.       to secondary name servers.
    589. 

  589.       The <span class="command"><strong>b10-xfrout</strong></span> is also used to send
    590. 

  590.       NOTIFY messages to slaves.
    591. 

  591.     </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    592. 

  592.      The current development release of BIND 10 only supports
    593. 

  593.      AXFR. (IXFR is not supported.) 
    594. 

  594.      Access control is not yet provided.
    595. 

  595.     </p></div></div><div class="chapter" title="Chapter 11. Secondary Manager"><div class="titlepage"><div><div><h2 class="title"><a name="zonemgr"></a>Chapter 11. Secondary Manager</h2></div></div></div><p>
    596. 

  596.       The <span class="command"><strong>b10-zonemgr</strong></span> process is started by
    597. 

  597.       <span class="command"><strong>bind10</strong></span>.
    598. 

  598.       It keeps track of SOA refresh, retry, and expire timers
    599. 

  599.       and other details for BIND 10 to perform as a slave.
    600. 

  600.       When the <span class="command"><strong>b10-auth</strong></span> authoritative DNS server
    601. 

  601.       receives a NOTIFY message, <span class="command"><strong>b10-zonemgr</strong></span>
    602. 

  602.       may tell <span class="command"><strong>b10-xfrin</strong></span> to do a refresh
    603. 

  603.       to start an inbound zone transfer.
    604. 

  604.       The secondary manager resets its counters when a new zone is
    605. 

  605.       transferred in.
    606. 

  606.     </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    607. 

  607.      Access control (such as allowing notifies) is not yet provided.
    608. 

  608.      The primary/secondary service is not yet complete.
    609. 

  609.     </p></div></div><div class="chapter" title="Chapter 12. Recursive Name Server"><div class="titlepage"><div><div><h2 class="title"><a name="resolverserver"></a>Chapter 12. Recursive Name Server</h2></div></div></div><p>
    610. 

  610.       The <span class="command"><strong>b10-resolver</strong></span> process is started by
    611. 

  611.       <span class="command"><strong>bind10</strong></span>.
    612. 

  612. 

  613.     </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    614. 

  614.       The current version only provides a forwarding DNS server.
    615. 

  615.       It does not cache and does not iterate to find answers.
    616. 

  616.       It simply forwards the query on to another full resolver.
    617. 

  617.     </p></div><p>
    618. 

  618.       The main <span class="command"><strong>bind10</strong></span> process can be configured
    619. 

  619.       to select to run either the authoritative or resolver.
    620. 

  620.       By default, it starts the authoritative service.
    621. 

  621. 

  622. 

  623.       You may change this using <span class="command"><strong>bindctl</strong></span>, for example:
    624. 

  624. 

  625.       </p><pre class="screen">
    626. 

  626. &gt; <strong class="userinput"><code>config set Boss/start_auth false</code></strong>
    627. 

  627. &gt; <strong class="userinput"><code>config set Boss/start_resolver true</code></strong>
    628. 

  628. &gt; <strong class="userinput"><code>config commit</code></strong>
    629. 

  629. </pre><p>
    630. 

  630. 

  631.     </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    632. 

  632.        In the current version, the master <span class="command"><strong>bind10</strong></span>
    633. 

  633.        process must be stopped and restarted to start up the resolver.
    634. 

  634.     </p></div><p>
    635. 

  635.       Then the upstream address and port must be configured to
    636. 

  636.       forward queries to, such as:
    637. 

  637. 

  638.       </p><pre class="screen">
    639. 

  639. &gt; <strong class="userinput"><code>config set Resolver/forward_addresses [{ "address": "<em class="replaceable"><code>192.168.1.1</code></em>", "port": 53 }]</code></strong>
    640. 

  640. &gt; <strong class="userinput"><code>config commit</code></strong>
    641. 

  641. </pre><p>
    642. 

  642. 

  643.       (Replace <em class="replaceable"><code>192.168.1.1</code></em> to point to your
    644. 

  644.       full resolver.)
    645. 

  645.     </p><p>
    646. 

  646.       The resolver also needs to be configured to listen on an address
    647. 

  647.       and port:
    648. 

  648. 

  649.       </p><pre class="screen">
    650. 

  650. &gt; <strong class="userinput"><code>config set Resolver/listen_on [{ "address": "127.0.0.1", "port": 53 }]</code></strong>
    651. 

  651. &gt; <strong class="userinput"><code>config commit</code></strong>
    652. 

  652. </pre><p>
    653. 

  653.     </p></div><div class="chapter" title="Chapter 13. Statistics"><div class="titlepage"><div><div><h2 class="title"><a name="statistics"></a>Chapter 13. Statistics</h2></div></div></div><p>
    654. 

  654.       The <span class="command"><strong>b10-stats</strong></span> process is started by
    655. 

  655.       <span class="command"><strong>bind10</strong></span>.
    656. 

  656.       It periodically collects statistics data from various modules
    657. 

  657.       and aggregates it.
    658. 

  658. 

  659.     </p><p>
    660. 

  660. 

  661.        This stats daemon provides commands to identify if it is running,
    662. 

  662.        show specified or all statistics data, set values, remove data,
    663. 

  663.        and reset data.
    664. 

  664. 

  665.        For example, using <span class="command"><strong>bindctl</strong></span>:
    666. 

  666. 

  667.        </p><pre class="screen">
    668. 

  668. &gt; <strong class="userinput"><code>Stats show</code></strong>
    669. 

  669. {
    670. 

  670.     "auth.queries.tcp": 1749,
    671. 

  671.     "auth.queries.udp": 867868,
    672. 

  672.     "bind10.boot_time": "2011-01-20T16:59:03Z",
    673. 

  673.     "report_time": "2011-01-20T17:04:06Z",
    674. 

  674.     "stats.boot_time": "2011-01-20T16:59:05Z",
    675. 

  675.     "stats.last_update_time": "2011-01-20T17:04:05Z",
    676. 

  676.     "stats.lname": "4d3869d9_a@jreed.example.net",
    677. 

  677.     "stats.start_time": "2011-01-20T16:59:05Z",
    678. 

  678.     "stats.timestamp": 1295543046.823504
    679. 

  679. }
    680. 

  680.        </pre><p>
    681. 

  681.     </p></div></div></body></html>
    682.