Accueil Explorer Aide
Connexion
zorun
/
kea
1
0
Fork 0
Fichiers Tickets 0 Pull Requests 0 Wiki
Aborescence: c4412dfaa0
Branches Tags
kea
/
doc
/
guide
/
bind10-guide.html

bind10-guide.html 50 KB
Historique Raw

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683 
  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 20110322. 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.         20110322.</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 20110322.
    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="#id1168230299038">Supported Platforms</a></span></dt><dt><span class="section"><a href="#id1168230299065">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="#id1168230284842">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="#id1168230285021">Download Tar File</a></span></dt><dt><span class="section"><a href="#id1168230285041">Retrieve from Git</a></span></dt><dt><span class="section"><a href="#id1168230285101">Configure before the build</a></span></dt><dt><span class="section"><a href="#id1168230285198">Build</a></span></dt><dt><span class="section"><a href="#id1168230285214">Install</a></span></dt><dt><span class="section"><a href="#id1168230285238">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="#id1168230285812">Server Configurations</a></span></dt><dt><span class="section"><a href="#id1168230285877">Data Source Backends</a></span></dt><dt><span class="section"><a href="#id1168230285908">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><dd><dl><dt><span class="section"><a href="#id1168230286296">Forwarding</a></span></dt></dl></dd><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="#id1168230299038">Supported Platforms</a></span></dt><dt><span class="section"><a href="#id1168230299065">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 20110322.
    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 caching recursive name server
    20. 

  20.         which also provides forwarding.
    21. 

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

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

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

  24.   Linux 5.3.
    25. 

  25. 

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

  27.   platforms.
    28. 

  28. 

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

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

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

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

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

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

  35. 	The authoritative server requires SQLite 3.3.9 or newer.
    36. 

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

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

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

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

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

  41.           in their default installation nor standard packages
    42. 

  42.           collections.
    43. 

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

  44.         </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>
    45. 

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

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

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

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

  49. 	single process.
    50. 

  50.       </p><p>
    51. 

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

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

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

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

  55. 	processes as needed.
    56. 

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

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

  58.       </p><p>
    59. 

  59. 

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

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

  62.               Message bus daemon.
    63. 

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

  64.               BIND 10 processes.
    65. 

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

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

  67.               Authoritative DNS server.
    68. 

  68.               This process serves DNS requests.
    69. 

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

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

  71.               Configuration manager.
    72. 

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

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

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

  75.               Command and control service.
    76. 

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

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

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

  79.               Recursive name server.
    80. 

  80.               This process handles incoming queries.
    81. 

  81. 

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

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

  84.               Statistics collection daemon.
    85. 

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

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

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

  88.               Incoming zone transfer service.
    89. 

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

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

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

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

  93.               Outgoing zone transfer service.
    94. 

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

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

  96. 	      when acting as a master server.
    97. 

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

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

  99.               Secondary manager.
    100. 

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

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

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

  103.       </p><p>
    104. 

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

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

  106.       </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>
    107. 

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

  108. 	directly with the system:
    109. 

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

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

  111.               interactive administration interface.
    112. 

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

  113.               to control BIND 10.
    114. 

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

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

  116.               zone file loader.
    117. 

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

  118.               BIND 10.
    119. 

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

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

  121.               user access control.
    122. 

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

  123.               to manage BIND 10.
    124. 

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

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

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

  127. 

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

  129.     </p><p>
    130. 

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

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

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

  133.       documentation and code examples.
    134. 

  134. 

  135.     </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="#id1168230284842">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="#id1168230285021">Download Tar File</a></span></dt><dt><span class="section"><a href="#id1168230285041">Retrieve from Git</a></span></dt><dt><span class="section"><a href="#id1168230285101">Configure before the build</a></span></dt><dt><span class="section"><a href="#id1168230285198">Build</a></span></dt><dt><span class="section"><a href="#id1168230285214">Install</a></span></dt><dt><span class="section"><a href="#id1168230285238">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="id1168230284842"></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>
    136. 

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

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

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

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

  140.           </p></div><p>
    141. 

  141.           Building from source code requires the Boost
    142. 

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

  143.   
    144. 

  144.   
    145. 

  145.         </p><p>
    146. 

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

  147.           enable the Xfrout and Xfrin support.
    148. 

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

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

  150.           for Python 3.1.
    151. 

  151.         </p></div><p>
    152. 

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

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

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

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

  156.         </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>
    157. 

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

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

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

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

  161.         </p></div><p>
    162. 

  162.         To quickly get started with BIND 10, follow these steps.
    163. 

  163.       </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
    164. 

  164.             Install required build dependencies.
    165. 

  165.           </li><li class="listitem">
    166. 

  166.             Download the BIND 10 source tar file from
    167. 

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

  168.           </li><li class="listitem"><p>Extract the tar file:
    169. 

  169.           </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>
    170. 

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

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

  172.   $ <strong class="userinput"><code>./configure</code></strong></pre><p>
    173. 

  173.           </p></li><li class="listitem"><p>Build it:
    174. 

  174.             </p><pre class="screen">$ <strong class="userinput"><code>make</code></strong></pre><p>
    175. 

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

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

  177.           </p></li><li class="listitem"><p>Start the server:
    178. 

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

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

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

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

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

  183.           </p></li><li class="listitem">
    184. 

  184.             Test the new zone.
    185. 

  185.           </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>
    186. 

  186.         BIND 10 is open source software written in C++ and Python.
    187. 

  187.         It is freely available in source code form from ISC via
    188. 

  188.         the Git code revision control system or as a downloadable
    189. 

  189.         tar file. It may also be available in pre-compiled ready-to-use
    190. 

  190.         packages from operating system vendors.
    191. 

  191.       </p><div class="section" title="Download Tar File"><div class="titlepage"><div><div><h3 class="title"><a name="id1168230285021"></a>Download Tar File</h3></div></div></div><p>
    192. 

  192.           Downloading a release tar file is the recommended method to
    193. 

  193.           obtain the source code.
    194. 

  194.         </p><p>
    195. 

  195.           The BIND 10 releases are available as tar file downloads from
    196. 

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

  197.           Periodic development snapshots may also be available.
    198. 

  198.         </p></div><div class="section" title="Retrieve from Git"><div class="titlepage"><div><div><h3 class="title"><a name="id1168230285041"></a>Retrieve from Git</h3></div></div></div><p>
    199. 

  199.           Downloading this "bleeding edge" code is recommended only for
    200. 

  200.           developers or advanced users.  Using development code in a production
    201. 

  201.           environment is not recommended.
    202. 

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

  203.             When using source code retrieved via Git additional
    204. 

  204.             software will be required:  automake (v1.11 or newer),
    205. 

  205.             libtoolize, and autoconf (2.59 or newer).
    206. 

  206.             These may need to be installed.
    207. 

  207.           </p></div><p>
    208. 

  208.           The latest development code, including temporary experiments
    209. 

  209.           and un-reviewed code, is available via the BIND 10 code revision
    210. 

  210.           control system. This is powered by Git and all the BIND 10
    211. 

  211.           development is public.
    212. 

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

  213.         </p><p>
    214. 

  214.           The code can be checked out from
    215. 

  215.           <code class="filename">git://bind10.isc.org/bind10</code>;
    216. 

  216.           for example:
    217. 

  217. 

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

  219.         </p><p>
    220. 

  220.           When checking out the code from
    221. 

  221.           the code version control system, it doesn't include the
    222. 

  222.           generated configure script, Makefile.in files, nor the
    223. 

  223.           related configure files.
    224. 

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

  225.           with the <code class="option">--install</code> switch.
    226. 

  226.           This will run <span class="command"><strong>autoconf</strong></span>,
    227. 

  227.           <span class="command"><strong>aclocal</strong></span>,
    228. 

  228.           <span class="command"><strong>libtoolize</strong></span>,
    229. 

  229.           <span class="command"><strong>autoheader</strong></span>,
    230. 

  230.           <span class="command"><strong>automake</strong></span>,
    231. 

  231.           and related commands.
    232. 

  232.         </p></div><div class="section" title="Configure before the build"><div class="titlepage"><div><div><h3 class="title"><a name="id1168230285101"></a>Configure before the build</h3></div></div></div><p>
    233. 

  233.           BIND 10 uses the GNU Build System to discover build environment
    234. 

  234.           details.
    235. 

  235.           To generate the makefiles using the defaults, simply run:
    236. 

  236.           </p><pre class="screen">$ <strong class="userinput"><code>./configure</code></strong></pre><p>
    237. 

  237.         </p><p>
    238. 

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

  239.           switch to view the different options. The commonly-used options are:
    240. 

  240. 

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

  242.                 default is <code class="filename">/usr/local/</code>).
    243. 

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

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

  245.                 standard execution path.
    246. 

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

  247.                 Google Tests framework. Optionally this can define the
    248. 

  248.                 path to the gtest header files and library.
    249. 

  249.               </dd></dl></div><p>
    250. 

  250. 

  251.         </p><p>
    252. 

  252.           For example, the following configures it to
    253. 

  253.     find the Boost headers, find the
    254. 

  254.     Python interpreter, and sets the installation location:
    255. 

  255. 

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

  257.       --with-boost-include=/usr/pkg/include \
    258. 

  258.       --with-pythonpath=/usr/pkg/bin/python3.1 \
    259. 

  259.       --prefix=/opt/bind10</code></strong></pre><p>
    260. 

  260.         </p><p>
    261. 

  261.           If the configure fails, it may be due to missing or old
    262. 

  262.           dependencies.
    263. 

  263.         </p></div><div class="section" title="Build"><div class="titlepage"><div><div><h3 class="title"><a name="id1168230285198"></a>Build</h3></div></div></div><p>
    264. 

  264.     After the configure step is complete, to build the executables
    265. 

  265.     from the C++ code and prepare the Python scripts, run:
    266. 

  266. 

  267.           </p><pre class="screen">$ <strong class="userinput"><code>make</code></strong></pre><p>
    268. 

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

  269.           To install the BIND 10 executables, support files,
    270. 

  270.           and documentation, run:
    271. 

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

  272.         </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="id1168230285238"></a>Install Hierarchy</h3></div></div></div><p>
    273. 

  273.           The following is the layout of the complete BIND 10 installation:
    274. 

  274.           </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
    275. 

  275.                 <code class="filename">bin/</code> &#8212;
    276. 

  276.                 general tools and diagnostic clients.
    277. 

  277.               </li><li class="listitem">
    278. 

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

  279.               configuration files.
    280. 

  280.             </li><li class="listitem">
    281. 

  281.                 <code class="filename">lib/</code> &#8212;
    282. 

  282.                 libraries and python modules.
    283. 

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

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

  285.                 executables that a user wouldn't normally run directly and
    286. 

  286.                 are not run independently.
    287. 

  287.                 These are the BIND 10 modules which are daemons started by
    288. 

  288.                 the <span class="command"><strong>bind10</strong></span> tool.
    289. 

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

  290.                 <code class="filename">sbin/</code> &#8212;
    291. 

  291.                 commands used by the system administrator.
    292. 

  292.               </li><li class="listitem">
    293. 

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

  294.                 configuration specifications.
    295. 

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

  296.                 <code class="filename">share/man/</code> &#8212;
    297. 

  297.                 manual pages (online documentation).
    298. 

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

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

  300.                 data source and configuration databases.
    301. 

  301.               </li></ul></div><p>
    302. 

  302.         </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>
    303. 

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

  304.       starts up the required processes.
    305. 

  305.       <span class="command"><strong>bind10</strong></span>
    306. 

  306.       will also restart processes that exit unexpectedly.
    307. 

  307.       This is the only command needed to start the BIND 10 system.
    308. 

  308.     </p><p>
    309. 

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

  310.       <span class="command"><strong>bind10</strong></span> connects to it, 
    311. 

  311.       runs the configuration manager, and reads its own configuration.
    312. 

  312.       Then it starts the other modules.
    313. 

  313.     </p><p>
    314. 

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

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

  316.       provides the communication channel between every part of the system.
    317. 

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

  318.       module, if only to send information about themselves somewhere,
    319. 

  319.       but more importantly to ask about their own settings, and
    320. 

  320.       about other modules.
    321. 

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

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

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

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

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

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

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

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

  329.     </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>
    330. 

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

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

  332.         get additional debugging or diagnostic output.
    333. 

  333.       </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>
    334. 

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

  335.         message routing daemon to communicate with other BIND 10 components.
    336. 

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

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

  338.         Processes intercommunicate by sending messages on the command
    339. 

  339.         channel.
    340. 

  340.         Example messages include shutdown, get configurations, and set
    341. 

  341.         configurations.
    342. 

  342.         This Command Channel is not used for DNS message passing.
    343. 

  343.         It is used only to control and monitor the BIND 10 system.
    344. 

  344.       </p><p>
    345. 

  345.         Administrators do not communicate directly with the
    346. 

  346.         <span class="command"><strong>b10-msgq</strong></span> daemon.
    347. 

  347.         By default, BIND 10 uses port 9912 for the
    348. 

  348.         <span class="command"><strong>b10-msgq</strong></span> service.
    349. 

  349.         It listens on 127.0.0.1.
    350. 

  350.       </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>
    351. 

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

  352.          handles all BIND 10 system configuration.  It provides
    353. 

  353.          persistent storage for configuration, and notifies running
    354. 

  354.          modules of configuration changes.
    355. 

  355.       </p><p>
    356. 

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

  357.         daemons and other components receive their configurations
    358. 

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

  359.         command channel.
    360. 

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

  361.         uses a user interface to communicate with the configuration
    362. 

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

  363.         <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>.
    364. 

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

  365.           The development prototype release only provides the
    366. 

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

  367.           <span class="command"><strong>b10-cmdctl</strong></span>.
    368. 

  368.           Upcoming releases will provide another interactive command-line
    369. 

  369.           interface and a web-based interface.
    370. 

  370.         </p></div><p>
    371. 

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

  372.         specifications and all current settings to the
    373. 

  373.         <span class="command"><strong>bindctl</strong></span> client (via
    374. 

  374.         <span class="command"><strong>b10-cmdctl</strong></span>).
    375. 

  375.       </p><p>
    376. 

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

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

  378.       </p><p>
    379. 

  379.         The stored configuration file is at
    380. 

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

  381.         (The full path is what was defined at build configure time for
    382. 

  382.         <code class="option">--localstatedir</code>.
    383. 

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

  384.         The format is loosely based on JSON and is directly parseable
    385. 

  385.         python, but this may change in a future version.
    386. 

  386.         This configuration data file is not manually edited by the
    387. 

  387.         administrator.
    388. 

  388.       </p><p>
    389. 

  389.       The configuration manager does not have any command line arguments.
    390. 

  390.       Normally it is not started manually, but is automatically
    391. 

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

  392.       (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>).
    393. 

  393.     </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>
    394. 

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

  395.       administrators and the BIND 10 system.
    396. 

  396.       It is a HTTPS server that uses standard HTTP Digest
    397. 

  397.       Authentication for username and password validation.
    398. 

  398.       It provides a REST-ful interface for accessing and controlling
    399. 

  399.       BIND 10.
    400. 

  400.     </p><p>
    401. 

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

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

  403.       running and what their configuration is (over the
    404. 

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

  405.       on HTTPS for clients &#8212; the user interface &#8212; such
    406. 

  406.       as <span class="command"><strong>bindctl</strong></span>.
    407. 

  407.     </p><p>
    408. 

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

  409.       (received from the user interface) to the specified component.
    410. 

  410.       Configuration changes are actually commands to
    411. 

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

  412.     </p><p>The HTTPS server requires a private key,
    413. 

  413.       such as a RSA PRIVATE KEY.
    414. 

  414.       The default location is at
    415. 

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

  416.       (A sample key is at
    417. 

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

  418.       It also uses a certificate located at
    419. 

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

  420.       (A sample certificate is at
    421. 

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

  422.       This may be a self-signed certificate or purchased from a
    423. 

  423.       certification authority.
    424. 

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

  425.       The HTTPS server doesn't support a certificate request from a
    426. 

  426.       client (at this time).
    427. 

  427. 

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

  429.       public service. If any client wants to control BIND 10, then
    430. 

  430.       a certificate needs to be first received from the BIND 10
    431. 

  431.       administrator.
    432. 

  432.       The BIND 10 installation provides a sample PEM bundle that matches
    433. 

  433.       the sample key and certificate.
    434. 

  434.     </p></div><p>
    435. 

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

  436.       the user account file located at
    437. 

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

  438.       This comma-delimited file lists the accounts with a user name,
    439. 

  439.       hashed password, and salt.
    440. 

  440.       (A sample file is at
    441. 

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

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

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

  444.     </p><p>
    445. 

  445.       The administrator may create a user account with the
    446. 

  446.       <span class="command"><strong>b10-cmdctl-usermgr</strong></span> tool.
    447. 

  447.     </p><p>
    448. 

  448.       By default the HTTPS server listens on the localhost port 8080.
    449. 

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

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

  451.       line argument.
    452. 

  452.       Each HTTPS connection is stateless and timesout in 1200 seconds
    453. 

  453.       by default.  This can be
    454. 

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

  455.     </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>
    456. 

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

  457. key_file
    458. 

  458. cert_file
    459. 

  459. accounts_file
    460. 

  460.       </p><p>
    461. 

  461.         The control commands are:
    462. 

  462. print_settings
    463. 

  463. 

  464. 

  465. shutdown
    466. 

  466.       </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>
    467. 

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

  468.       is the only user interface. It is expected that upcoming
    469. 

  469.       releases will provide another interactive command-line
    470. 

  470.       interface and a web-based interface for controlling and
    471. 

  471.       configuring BIND 10.
    472. 

  472.     </p></div><p>
    473. 

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

  474.       prompt for configuring, controlling, and querying the BIND 10
    475. 

  475.       components.
    476. 

  476.       It communicates directly with a REST-ful interface over HTTPS
    477. 

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

  478.       communicate to any other components directly.
    479. 

  479.     </p><p>
    480. 

  480.       Configuration changes are actually commands to
    481. 

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

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

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

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

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

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

  487.       channel) the configuration on to the specified module.
    488. 

  488.     </p><p>
    489. 

  489.     </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="#id1168230285812">Server Configurations</a></span></dt><dt><span class="section"><a href="#id1168230285877">Data Source Backends</a></span></dt><dt><span class="section"><a href="#id1168230285908">Loading Master Zones Files</a></span></dt></dl></div><p>
    490. 

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

  491.       It supports EDNS0 and DNSSEC. It supports IPv6.
    492. 

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

  493.       process.
    494. 

  494.     </p><div class="section" title="Server Configurations"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168230285812"></a>Server Configurations</h2></div></div></div><p>
    495. 

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

  496.         <span class="command"><strong>b10-cfgmgr</strong></span> configuration manager.
    497. 

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

  498.         The configuration data item is:
    499. 

  499. 

  500.         </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
    501. 

  501.                  the SQLite3 database file.
    502. 

  502. 

  503. Note: Later the DNS server will use various data source backends.
    504. 

  504. This may be a temporary setting until then.
    505. 

  505.               </dd></dl></div><p>
    506. 

  506. 

  507.       </p><p>
    508. 

  508. 

  509.         The configuration command is:
    510. 

  510. 

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

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

  513. 

  514.       </p></div><div class="section" title="Data Source Backends"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168230285877"></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>
    515. 

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

  516.         supports a SQLite3 data source backend and in-memory data source
    517. 

  517.         backend.
    518. 

  518.         Upcoming versions will be able to use multiple different
    519. 

  519.         data sources, such as MySQL and Berkeley DB.
    520. 

  520.       </p></div><p>
    521. 

  521.         By default, the SQLite3 backend uses the data file located at
    522. 

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

  523.         (The full path is what was defined at build configure time for
    524. 

  524.         <code class="option">--localstatedir</code>.
    525. 

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

  526.   This data file location may be changed by defining the
    527. 

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

  528.       </p></div><div class="section" title="Loading Master Zones Files"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168230285908"></a>Loading Master Zones Files</h2></div></div></div><p>
    529. 

  529.         RFC 1035 style DNS master zone files may imported
    530. 

  530.         into a BIND 10 data source by using the
    531. 

  531.         <span class="command"><strong>b10-loadzone</strong></span> utility.
    532. 

  532.       </p><p>
    533. 

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

  534.         special directives (control entries):
    535. 

  535. 

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

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

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

  539.                 records that don't include a TTL.
    540. 

  540.               </dd></dl></div><p>
    541. 

  541. 

  542.       </p><p>
    543. 

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

  544.         default origin for loaded zone file records.
    545. 

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

  546.         In the development prototype release, only the SQLite3 back
    547. 

  547.         end is used.
    548. 

  548.         By default, it stores the zone data in
    549. 

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

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

  551.         database filename.
    552. 

  552.         Multiple zones are stored in a single SQLite3 zone database.
    553. 

  553.       </p></div><p>
    554. 

  554.         If you reload a zone already existing in the database,
    555. 

  555.         all records from that prior zone disappear and a whole new set
    556. 

  556.         appears.
    557. 

  557.       </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>
    558. 

  558.       Incoming zones are transferred using the <span class="command"><strong>b10-xfrin</strong></span>
    559. 

  559.       process which is started by <span class="command"><strong>bind10</strong></span>.
    560. 

  560.       When received, the zone is stored in the BIND 10
    561. 

  561.       data store, and its records can be served by
    562. 

  562.       <span class="command"><strong>b10-auth</strong></span>.
    563. 

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

  564.       automated SOA checks), this allows the BIND 10 server to
    565. 

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

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

  567.      The current development release of BIND 10 only supports
    568. 

  568.      AXFR. (IXFR is not supported.) 
    569. 

  569. 

  570. 

  571. 

  572.     </p></div><p>
    573. 

  573.        To manually trigger a zone transfer to retrieve a remote zone,
    574. 

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

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

  576. 

  577.        </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>
    578. 

  578.     </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>
    579. 

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

  580.       <span class="command"><strong>bind10</strong></span>.
    581. 

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

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

  583.       sends the zone.
    584. 

  584.       This is used to provide master DNS service to share zones
    585. 

  585.       to secondary name servers.
    586. 

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

  587.       NOTIFY messages to slaves.
    588. 

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

  589.      The current development release of BIND 10 only supports
    590. 

  590.      AXFR. (IXFR is not supported.) 
    591. 

  591.      Access control is not yet provided.
    592. 

  592.     </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>
    593. 

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

  594.       <span class="command"><strong>bind10</strong></span>.
    595. 

  595.       It keeps track of SOA refresh, retry, and expire timers
    596. 

  596.       and other details for BIND 10 to perform as a slave.
    597. 

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

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

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

  600.       to start an inbound zone transfer.
    601. 

  601.       The secondary manager resets its counters when a new zone is
    602. 

  602.       transferred in.
    603. 

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

  604.      Access control (such as allowing notifies) is not yet provided.
    605. 

  605.      The primary/secondary service is not yet complete.
    606. 

  606.     </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><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id1168230286296">Forwarding</a></span></dt></dl></div><p>
    607. 

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

  608.       <span class="command"><strong>bind10</strong></span>.
    609. 

  609. 

  610.     </p><p>
    611. 

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

  612.       to select to run either the authoritative or resolver.
    613. 

  613.       By default, it starts the authoritative service.
    614. 

  614. 

  615. 

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

  617. 

  618.       </p><pre class="screen">
    619. 

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

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

  621. &gt; <strong class="userinput"><code>config commit</code></strong>
    622. 

  622. </pre><p>
    623. 

  623. 

  624.     </p><p>
    625. 

  625.        The master <span class="command"><strong>bind10</strong></span> will stop and start
    626. 

  626.        the desired services.
    627. 

  627.     </p><p>
    628. 

  628.       The resolver also needs to be configured to listen on an address
    629. 

  629.       and port:
    630. 

  630. 

  631.       </p><pre class="screen">
    632. 

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

  633. &gt; <strong class="userinput"><code>config commit</code></strong>
    634. 

  634. </pre><p>
    635. 

  635.     </p><div class="section" title="Forwarding"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168230286296"></a>Forwarding</h2></div></div></div><p>
    636. 

  636. 

  637.         To enable forwarding, the upstream address and port must be
    638. 

  638.         configured to forward queries to, such as:
    639. 

  639. 

  640.         </p><pre class="screen">
    641. 

  641. &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>
    642. 

  642. &gt; <strong class="userinput"><code>config commit</code></strong>
    643. 

  643. </pre><p>
    644. 

  644. 

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

  646.         full resolver.)
    647. 

  647.       </p><p>
    648. 

  648.         Normal iterative name service can be re-enabled by clearing the
    649. 

  649.         forwarding address(es); for example:
    650. 

  650. 

  651.         </p><pre class="screen">
    652. 

  652. &gt; <strong class="userinput"><code>config set Resolver/forward_addresses []</code></strong>
    653. 

  653. &gt; <strong class="userinput"><code>config commit</code></strong>
    654. 

  654. </pre><p>
    655. 

  655.       </p></div></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>
    656. 

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

  657.       <span class="command"><strong>bind10</strong></span>.
    658. 

  658.       It periodically collects statistics data from various modules
    659. 

  659.       and aggregates it.
    660. 

  660. 

  661.     </p><p>
    662. 

  662. 

  663.        This stats daemon provides commands to identify if it is running,
    664. 

  664.        show specified or all statistics data, set values, remove data,
    665. 

  665.        and reset data.
    666. 

  666. 

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

  668. 

  669.        </p><pre class="screen">
    670. 

  670. &gt; <strong class="userinput"><code>Stats show</code></strong>
    671. 

  671. {
    672. 

  672.     "auth.queries.tcp": 1749,
    673. 

  673.     "auth.queries.udp": 867868,
    674. 

  674.     "bind10.boot_time": "2011-01-20T16:59:03Z",
    675. 

  675.     "report_time": "2011-01-20T17:04:06Z",
    676. 

  676.     "stats.boot_time": "2011-01-20T16:59:05Z",
    677. 

  677.     "stats.last_update_time": "2011-01-20T17:04:05Z",
    678. 

  678.     "stats.lname": "4d3869d9_a@jreed.example.net",
    679. 

  679.     "stats.start_time": "2011-01-20T16:59:05Z",
    680. 

  680.     "stats.timestamp": 1295543046.823504
    681. 

  681. }
    682. 

  682.        </pre><p>
    683. 

  683.     </p></div></div></body></html>
    684.