2
0
mirror of https://gitlab.isc.org/isc-projects/kea synced 2025-09-04 07:55:18 +00:00

Document more about b10-resolver and introduce b10-stats.

Add some bindctl examples for configuring b10-resolver.
And also introduce b10-stats and Stats show.
This commit is contained in:
Jeremy C. Reed
2011-01-20 11:51:51 -06:00
parent cb38a8f920
commit 0e10d2264e
2 changed files with 173 additions and 22 deletions

View File

@@ -6,7 +6,7 @@
</p><p> </p><p>
This is the reference guide for BIND 10 version 20101201. This is the reference guide for BIND 10 version 20101201.
The most up-to-date version of this document, along with The most up-to-date version of this document, along with
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="#id1168230284833">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="#id1168230285018">Download Tar File</a></span></dt><dt><span class="section"><a href="#id1168230285037">Retrieve from Git</a></span></dt><dt><span class="section"><a href="#id1168230285098">Configure before the build</a></span></dt><dt><span class="section"><a href="#id1168230285195">Build</a></span></dt><dt><span class="section"><a href="#id1168230285211">Install</a></span></dt><dt><span class="section"><a href="#id1168230285235">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="#id1168230285808">Server Configurations</a></span></dt><dt><span class="section"><a href="#id1168230285873">Data Source Backends</a></span></dt><dt><span class="section"><a href="#id1168230285904">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></dl></div><div class="chapter" title="Chapter<65>1.<2E>Introduction"><div class="titlepage"><div><div><h2 class="title"><a name="intro"></a>Chapter<EFBFBD>1.<2E>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> 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<65>1.<2E>Introduction"><div class="titlepage"><div><div><h2 class="title"><a name="intro"></a>Chapter<EFBFBD>1.<2E>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>
BIND is the popular implementation of a DNS server, developer BIND is the popular implementation of a DNS server, developer
interfaces, and DNS tools. interfaces, and DNS tools.
BIND 10 is a rewrite of BIND 9. BIND 10 is written in C++ and Python BIND 10 is a rewrite of BIND 9. BIND 10 is written in C++ and Python
@@ -80,6 +80,10 @@
Recursive name server. Recursive name server.
This process handles incoming queries. This process handles incoming queries.
</li><li class="listitem">
<span class="command"><strong>b10-stats</strong></span> &#8212;
Statistics collection daemon.
This process collects and reports statistics data.
</li><li class="listitem"> </li><li class="listitem">
<span class="command"><strong>b10-xfrin</strong></span> &#8212; <span class="command"><strong>b10-xfrin</strong></span> &#8212;
Incoming zone transfer service. Incoming zone transfer service.
@@ -129,7 +133,7 @@
and, of course, DNS. These include detailed developer and, of course, DNS. These include detailed developer
documentation and code examples. documentation and code examples.
</p></div><div class="chapter" title="Chapter<65>2.<2E>Installation"><div class="titlepage"><div><div><h2 class="title"><a name="installation"></a>Chapter<EFBFBD>2.<2E>Installation</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id1168230284833">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="#id1168230285018">Download Tar File</a></span></dt><dt><span class="section"><a href="#id1168230285037">Retrieve from Git</a></span></dt><dt><span class="section"><a href="#id1168230285098">Configure before the build</a></span></dt><dt><span class="section"><a href="#id1168230285195">Build</a></span></dt><dt><span class="section"><a href="#id1168230285211">Install</a></span></dt><dt><span class="section"><a href="#id1168230285235">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="id1168230284833"></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> </p></div><div class="chapter" title="Chapter<65>2.<2E>Installation"><div class="titlepage"><div><div><h2 class="title"><a name="installation"></a>Chapter<EFBFBD>2.<2E>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>
Some operating systems have split their distribution packages into Some operating systems have split their distribution packages into
a run-time and a development package. You will need to install a run-time and a development package. You will need to install
the development package versions, which include header files and the development package versions, which include header files and
@@ -189,14 +193,14 @@
the Git code revision control system or as a downloadable the Git code revision control system or as a downloadable
tar file. It may also be available in pre-compiled ready-to-use tar file. It may also be available in pre-compiled ready-to-use
packages from operating system vendors. packages from operating system vendors.
</p><div class="section" title="Download Tar File"><div class="titlepage"><div><div><h3 class="title"><a name="id1168230285018"></a>Download Tar File</h3></div></div></div><p> </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>
Downloading a release tar file is the recommended method to Downloading a release tar file is the recommended method to
obtain the source code. obtain the source code.
</p><p> </p><p>
The BIND 10 releases are available as tar file downloads from The BIND 10 releases are available as tar file downloads from
<a class="ulink" href="ftp://ftp.isc.org/isc/bind10/" target="_top">ftp://ftp.isc.org/isc/bind10/</a>. <a class="ulink" href="ftp://ftp.isc.org/isc/bind10/" target="_top">ftp://ftp.isc.org/isc/bind10/</a>.
Periodic development snapshots may also be available. Periodic development snapshots may also be available.
</p></div><div class="section" title="Retrieve from Git"><div class="titlepage"><div><div><h3 class="title"><a name="id1168230285037"></a>Retrieve from Git</h3></div></div></div><p> </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>
Downloading this "bleeding edge" code is recommended only for Downloading this "bleeding edge" code is recommended only for
developers or advanced users. Using development code in a production developers or advanced users. Using development code in a production
environment is not recommended. environment is not recommended.
@@ -230,7 +234,7 @@
<span class="command"><strong>autoheader</strong></span>, <span class="command"><strong>autoheader</strong></span>,
<span class="command"><strong>automake</strong></span>, <span class="command"><strong>automake</strong></span>,
and related commands. and related commands.
</p></div><div class="section" title="Configure before the build"><div class="titlepage"><div><div><h3 class="title"><a name="id1168230285098"></a>Configure before the build</h3></div></div></div><p> </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>
BIND 10 uses the GNU Build System to discover build environment BIND 10 uses the GNU Build System to discover build environment
details. details.
To generate the makefiles using the defaults, simply run: To generate the makefiles using the defaults, simply run:
@@ -261,16 +265,16 @@
</p><p> </p><p>
If the configure fails, it may be due to missing or old If the configure fails, it may be due to missing or old
dependencies. dependencies.
</p></div><div class="section" title="Build"><div class="titlepage"><div><div><h3 class="title"><a name="id1168230285195"></a>Build</h3></div></div></div><p> </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>
After the configure step is complete, to build the executables After the configure step is complete, to build the executables
from the C++ code and prepare the Python scripts, run: from the C++ code and prepare the Python scripts, run:
</p><pre class="screen">$ <strong class="userinput"><code>make</code></strong></pre><p> </p><pre class="screen">$ <strong class="userinput"><code>make</code></strong></pre><p>
</p></div><div class="section" title="Install"><div class="titlepage"><div><div><h3 class="title"><a name="id1168230285211"></a>Install</h3></div></div></div><p> </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>
To install the BIND 10 executables, support files, To install the BIND 10 executables, support files,
and documentation, run: and documentation, run:
</p><pre class="screen">$ <strong class="userinput"><code>make install</code></strong></pre><p> </p><pre class="screen">$ <strong class="userinput"><code>make install</code></strong></pre><p>
</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="id1168230285235"></a>Install Hierarchy</h3></div></div></div><p> </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>
The following is the layout of the complete BIND 10 installation: The following is the layout of the complete BIND 10 installation:
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"> </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
<code class="filename">bin/</code> &#8212; <code class="filename">bin/</code> &#8212;
@@ -323,6 +327,7 @@
<span class="command"><strong>b10-cmdctl</strong></span> for admins to communicate with the <span class="command"><strong>b10-cmdctl</strong></span> for admins to communicate with the
system, <span class="command"><strong>b10-auth</strong></span> for authoritative DNS service or system, <span class="command"><strong>b10-auth</strong></span> for authoritative DNS service or
<span class="command"><strong>b10-resolver</strong></span> for recursive name service, <span class="command"><strong>b10-resolver</strong></span> for recursive name service,
<span class="command"><strong>b10-stats</strong></span> for statistics collection,
<span class="command"><strong>b10-xfrin</strong></span> for inbound DNS zone transfers, <span class="command"><strong>b10-xfrin</strong></span> for inbound DNS zone transfers,
<span class="command"><strong>b10-xfrout</strong></span> for outbound DNS zone transfers, <span class="command"><strong>b10-xfrout</strong></span> for outbound DNS zone transfers,
and <span class="command"><strong>b10-zonemgr</strong></span> for secondary service. and <span class="command"><strong>b10-zonemgr</strong></span> for secondary service.
@@ -484,7 +489,7 @@ shutdown
the details and relays (over a <span class="command"><strong>b10-msgq</strong></span> command the details and relays (over a <span class="command"><strong>b10-msgq</strong></span> command
channel) the configuration on to the specified module. channel) the configuration on to the specified module.
</p><p> </p><p>
</p></div><div class="chapter" title="Chapter<65>8.<2E>Authoritative Server"><div class="titlepage"><div><div><h2 class="title"><a name="authserver"></a>Chapter<EFBFBD>8.<2E>Authoritative Server</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id1168230285808">Server Configurations</a></span></dt><dt><span class="section"><a href="#id1168230285873">Data Source Backends</a></span></dt><dt><span class="section"><a href="#id1168230285904">Loading Master Zones Files</a></span></dt></dl></div><p> </p></div><div class="chapter" title="Chapter<65>8.<2E>Authoritative Server"><div class="titlepage"><div><div><h2 class="title"><a name="authserver"></a>Chapter<EFBFBD>8.<2E>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>
The <span class="command"><strong>b10-auth</strong></span> is the authoritative DNS server. The <span class="command"><strong>b10-auth</strong></span> is the authoritative DNS server.
It supports EDNS0 and DNSSEC. It supports IPv6. It supports EDNS0 and DNSSEC. It supports IPv6.
Normally it is started by the <span class="command"><strong>bind10</strong></span> master Normally it is started by the <span class="command"><strong>bind10</strong></span> master
@@ -492,7 +497,7 @@ shutdown
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
This development prototype release listens on all interfaces This development prototype release listens on all interfaces
and the non-standard port 5300. and the non-standard port 5300.
</p></div><div class="section" title="Server Configurations"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168230285808"></a>Server Configurations</h2></div></div></div><p> </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>
<span class="command"><strong>b10-auth</strong></span> is configured via the <span class="command"><strong>b10-auth</strong></span> is configured via the
<span class="command"><strong>b10-cfgmgr</strong></span> configuration manager. <span class="command"><strong>b10-cfgmgr</strong></span> configuration manager.
The module name is <span class="quote">&#8220;<span class="quote">Auth</span>&#8221;</span>. The module name is <span class="quote">&#8220;<span class="quote">Auth</span>&#8221;</span>.
@@ -512,7 +517,7 @@ This may be a temporary setting until then.
</p><div class="variablelist"><dl><dt><span class="term">shutdown</span></dt><dd>Stop the authoritative DNS server. </p><div class="variablelist"><dl><dt><span class="term">shutdown</span></dt><dd>Stop the authoritative DNS server.
</dd></dl></div><p> </dd></dl></div><p>
</p></div><div class="section" title="Data Source Backends"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168230285873"></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> </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>
For the development prototype release, <span class="command"><strong>b10-auth</strong></span> For the development prototype release, <span class="command"><strong>b10-auth</strong></span>
only supports the SQLite3 data source backend. only supports the SQLite3 data source backend.
Upcoming versions will be able to use multiple different Upcoming versions will be able to use multiple different
@@ -525,7 +530,7 @@ This may be a temporary setting until then.
The default is <code class="filename">/usr/local/var/</code>.) The default is <code class="filename">/usr/local/var/</code>.)
This data file location may be changed by defining the This data file location may be changed by defining the
<span class="quote">&#8220;<span class="quote">database_file</span>&#8221;</span> configuration. <span class="quote">&#8220;<span class="quote">database_file</span>&#8221;</span> configuration.
</p></div><div class="section" title="Loading Master Zones Files"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168230285904"></a>Loading Master Zones Files</h2></div></div></div><p> </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>
RFC 1035 style DNS master zone files may imported RFC 1035 style DNS master zone files may imported
into a BIND 10 data source by using the into a BIND 10 data source by using the
<span class="command"><strong>b10-loadzone</strong></span> utility. <span class="command"><strong>b10-loadzone</strong></span> utility.
@@ -609,4 +614,68 @@ This may be a temporary setting until then.
The current version only provides a forwarding DNS server. The current version only provides a forwarding DNS server.
It does not cache and does not iterate to find answers. It does not cache and does not iterate to find answers.
It simply forwards the query on to another full resolver. It simply forwards the query on to another full resolver.
</p></div></div></div></body></html> </p></div><p>
The main <span class="command"><strong>bind10</strong></span> process can be configured
to select to run either the authoritative or resolver.
By default, it starts the authoritative service.
You may change this using <span class="command"><strong>bindctl</strong></span>, for example:
</p><pre class="screen">
&gt; <strong class="userinput"><code>config set Boss/start_auth false</code></strong>
&gt; <strong class="userinput"><code>config set Boss/start_resolver true</code></strong>
&gt; <strong class="userinput"><code>config commit</code></strong>
</pre><p>
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
In the current version, the master <span class="command"><strong>bind10</strong></span>
process must be stopped and restarted to start up the resolver.
</p></div><p>
Then the upstream address and port must be configured to
forward queries to, such as:
</p><pre class="screen">
&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>
&gt; <strong class="userinput"><code>config commit</code></strong>
</pre><p>
(Replace <em class="replaceable"><code>192.168.1.1</code></em> to point to your
full resolver.)
</p><p>
The resolver also needs to be configured to listen on an address
and port:
</p><pre class="screen">
&gt; <strong class="userinput"><code>config set Resolver/listen_on [{ "address": "127.0.0.1", "port": 53 }]</code></strong>
&gt; <strong class="userinput"><code>config commit</code></strong>
</pre><p>
</p></div><div class="chapter" title="Chapter<65>13.<2E>Statistics"><div class="titlepage"><div><div><h2 class="title"><a name="statistics"></a>Chapter<EFBFBD>13.<2E>Statistics</h2></div></div></div><p>
The <span class="command"><strong>b10-stats</strong></span> process is started by
<span class="command"><strong>bind10</strong></span>.
It periodically collects statistics data from various modules
and aggregates it.
</p><p>
This stats daemon provides commands to identify if it is running,
show specified or all statistics data, set values, remove data,
and reset data.
For example, using <span class="command"><strong>bindctl</strong></span>:
</p><pre class="screen">
&gt; <strong class="userinput"><code>Stats show</code></strong>
{
"auth.queries.tcp": 1749,
"auth.queries.udp": 867868,
"bind10.boot_time": "2011-01-20T16:59:03Z",
"report_time": "2011-01-20T17:04:06Z",
"stats.boot_time": "2011-01-20T16:59:05Z",
"stats.last_update_time": "2011-01-20T17:04:05Z",
"stats.lname": "4d3869d9_a@jreed.example.net",
"stats.start_time": "2011-01-20T16:59:05Z",
"stats.timestamp": 1295543046.823504
}
</pre><p>
</p></div></div></body></html>

View File

@@ -167,6 +167,14 @@
</simpara> </simpara>
</listitem> </listitem>
<listitem>
<simpara>
<command>b10-stats</command> &mdash;
Statistics collection daemon.
This process collects and reports statistics data.
</simpara>
</listitem>
<listitem> <listitem>
<simpara> <simpara>
<command>b10-xfrin</command> &mdash; <command>b10-xfrin</command> &mdash;
@@ -683,6 +691,7 @@ var/
<command>b10-cmdctl</command> for admins to communicate with the <command>b10-cmdctl</command> for admins to communicate with the
system, <command>b10-auth</command> for authoritative DNS service or system, <command>b10-auth</command> for authoritative DNS service or
<command>b10-resolver</command> for recursive name service, <command>b10-resolver</command> for recursive name service,
<command>b10-stats</command> for statistics collection,
<command>b10-xfrin</command> for inbound DNS zone transfers, <command>b10-xfrin</command> for inbound DNS zone transfers,
<command>b10-xfrout</command> for outbound DNS zone transfers, <command>b10-xfrout</command> for outbound DNS zone transfers,
and <command>b10-zonemgr</command> for secondary service. and <command>b10-zonemgr</command> for secondary service.
@@ -1304,27 +1313,100 @@ what is XfroutClient xfr_client??
It simply forwards the query on to another full resolver. It simply forwards the query on to another full resolver.
</simpara></note> </simpara></note>
<!-- TODO: <para>
The main <command>bind10</command> process can be configured
to select to run either the authoritative or resolver.
By default, it starts the authoritative service.
<!-- TODO: later both -->
By default, bind10 starts the authoritative service. You may change this using <command>bindctl</command>, for example:
> config set Boss/start_auth false <screen>
> config set Boss/start_resolver true &gt; <userinput>config set Boss/start_auth false</userinput>
&gt; <userinput>config set Boss/start_resolver true</userinput>
&gt; <userinput>config commit</userinput>
</screen>
config commit </para>
Boss shutdown
restart Boss <!-- TODO: -->
<note><simpara>
In the current version, the master <command>bind10</command>
process must be stopped and restarted to start up the resolver.
</simpara></note>
then next set forward_addresses as needed <para>
Then the upstream address and port must be configured to
forward queries to, such as:
{"version": 2, "Resolver": {"forward_addresses": [{"port": 5302, "address": "127.0.0.1"}], "listen_on": [{"port": 53, "address": "192.168.1.2"}, {"port": 53, "address": "127.0.0.1"}]}, "Boss": {"start_auth": false, "start_resolver": true}} <screen>
&gt; <userinput>config set Resolver/forward_addresses [{ "address": "<replaceable>192.168.1.1</replaceable>", "port": 53 }]</userinput>
&gt; <userinput>config commit</userinput>
</screen>
(Replace <replaceable>192.168.1.1</replaceable> to point to your
full resolver.)
</para>
<para>
The resolver also needs to be configured to listen on an address
and port:
<screen>
&gt; <userinput>config set Resolver/listen_on [{ "address": "127.0.0.1", "port": 53 }]</userinput>
&gt; <userinput>config commit</userinput>
</screen>
</para>
<!-- TODO: later the above will have some defaults -->
<!-- TODO: later try this
> config set Resolver/forward_addresses[0]/address "192.168.8.8"
> config set Resolver/forward_addresses[0]/port 53
then change those defaults with config set Resolver/forward_addresses[0]/address "1.2.3.4"
> config set Resolver/forward_addresses[0]/address "1.2.3.4"
--> -->
</chapter> </chapter>
<chapter id="statistics">
<title>Statistics</title>
<para>
The <command>b10-stats</command> process is started by
<command>bind10</command>.
It periodically collects statistics data from various modules
and aggregates it.
<!-- TODO -->
</para>
<para>
This stats daemon provides commands to identify if it is running,
show specified or all statistics data, set values, remove data,
and reset data.
For example, using <command>bindctl</command>:
<screen>
&gt; <userinput>Stats show</userinput>
{
"auth.queries.tcp": 1749,
"auth.queries.udp": 867868,
"bind10.boot_time": "2011-01-20T16:59:03Z",
"report_time": "2011-01-20T17:04:06Z",
"stats.boot_time": "2011-01-20T16:59:05Z",
"stats.last_update_time": "2011-01-20T17:04:05Z",
"stats.lname": "4d3869d9_a@jreed.example.net",
"stats.start_time": "2011-01-20T16:59:05Z",
"stats.timestamp": 1295543046.823504
}
</screen>
</para>
</chapter>
<!-- TODO: how to help: run unit tests, join lists, review trac tickets --> <!-- TODO: how to help: run unit tests, join lists, review trac tickets -->
<!-- <index> <title>Index</title> </index> --> <!-- <index> <title>Index</title> </index> -->