mirror of
https://gitlab.isc.org/isc-projects/kea
synced 2025-08-31 14:05:33 +00:00
[master] regenerate HTML, nroff and messages XML.
The content changes were done in the source files previously.
This commit is contained in:
Jeremy C. Reed
@@ -1,24 +1,24 @@
|
||||
<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 20110705. 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="id1168230298906"></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
|
||||
20110705.</p></div><div><p class="copyright">Copyright <20> 2010-2011 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
|
||||
<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 20110809. 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="id1168229460045"></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
|
||||
20110809.</p></div><div><p class="copyright">Copyright <20> 2010-2011 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
|
||||
Internet Systems Consortium (ISC). It includes DNS libraries
|
||||
and modular components for controlling authoritative and
|
||||
recursive DNS servers.
|
||||
</p><p>
|
||||
This is the reference guide for BIND 10 version 20110705.
|
||||
This is the reference guide for BIND 10 version 20110809.
|
||||
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="#id1168230284849">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="#id1168230285038">Download Tar File</a></span></dt><dt><span class="section"><a href="#id1168230285058">Retrieve from Git</a></span></dt><dt><span class="section"><a href="#id1168230285118">Configure before the build</a></span></dt><dt><span class="section"><a href="#id1168230285217">Build</a></span></dt><dt><span class="section"><a href="#id1168230285232">Install</a></span></dt><dt><span class="section"><a href="#id1168230285255">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="#id1168230285830">Server Configurations</a></span></dt><dt><span class="section"><a href="#id1168230285895">Data Source Backends</a></span></dt><dt><span class="section"><a href="#id1168230285925">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="#id1168230286381">Forwarding</a></span></dt></dl></dd><dt><span class="chapter"><a href="#statistics">13. Statistics</a></span></dt><dt><span class="chapter"><a href="#logging">14. Logging</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="#id1168229460181">Supported Platforms</a></span></dt><dt><span class="section"><a href="#id1168229460208">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="#id1168229445988">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="#id1168229446178">Download Tar File</a></span></dt><dt><span class="section"><a href="#id1168229446197">Retrieve from Git</a></span></dt><dt><span class="section"><a href="#id1168229446258">Configure before the build</a></span></dt><dt><span class="section"><a href="#id1168229446356">Build</a></span></dt><dt><span class="section"><a href="#id1168229446371">Install</a></span></dt><dt><span class="section"><a href="#id1168229446394">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="#id1168229446979">Server Configurations</a></span></dt><dt><span class="section"><a href="#id1168229447044">Data Source Backends</a></span></dt><dt><span class="section"><a href="#id1168229447074">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="#id1168229447556">Access Control</a></span></dt><dt><span class="section"><a href="#id1168229447671">Forwarding</a></span></dt></dl></dd><dt><span class="chapter"><a href="#statistics">13. Statistics</a></span></dt><dt><span class="chapter"><a href="#logging">14. Logging</a></span></dt><dd><dl><dt><span class="section"><a href="#id1168229447788">Logging configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#id1168229447799">Loggers</a></span></dt><dt><span class="section"><a href="#id1168229448040">Output Options</a></span></dt><dt><span class="section"><a href="#id1168229448215">Example session</a></span></dt></dl></dd><dt><span class="section"><a href="#id1168229448428">Logging Message Format</a></span></dt></dl></dd></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="#id1168229460181">Supported Platforms</a></span></dt><dt><span class="section"><a href="#id1168229460208">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
|
||||
interfaces, and DNS tools.
|
||||
BIND 10 is a rewrite of BIND 9. BIND 10 is written in C++ and Python
|
||||
and provides a modular environment for serving and maintaining DNS.
|
||||
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
|
||||
This guide covers the experimental prototype of
|
||||
BIND 10 version 20110705.
|
||||
BIND 10 version 20110809.
|
||||
</p></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
|
||||
BIND 10 provides a EDNS0- and DNSSEC-capable
|
||||
authoritative DNS server and a caching recursive name server
|
||||
which also provides forwarding.
|
||||
</p></div><div class="section" title="Supported Platforms"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168230299042"></a>Supported Platforms</h2></div></div></div><p>
|
||||
</p></div><div class="section" title="Supported Platforms"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168229460181"></a>Supported Platforms</h2></div></div></div><p>
|
||||
BIND 10 builds have been tested on Debian GNU/Linux 5,
|
||||
Ubuntu 9.10, NetBSD 5, Solaris 10, FreeBSD 7 and 8, and CentOS
|
||||
Linux 5.3.
|
||||
@@ -28,7 +28,7 @@
|
||||
|
||||
It is planned for BIND 10 to build, install and run on
|
||||
Windows and standard Unix-type platforms.
|
||||
</p></div><div class="section" title="Required Software"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168230299068"></a>Required Software</h2></div></div></div><p>
|
||||
</p></div><div class="section" title="Required Software"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168229460208"></a>Required Software</h2></div></div></div><p>
|
||||
BIND 10 requires Python 3.1. Later versions may work, but Python
|
||||
3.1 is the minimum version which will work.
|
||||
</p><p>
|
||||
@@ -138,7 +138,7 @@
|
||||
and, of course, DNS. These include detailed developer
|
||||
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="#id1168230284849">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="#id1168230285038">Download Tar File</a></span></dt><dt><span class="section"><a href="#id1168230285058">Retrieve from Git</a></span></dt><dt><span class="section"><a href="#id1168230285118">Configure before the build</a></span></dt><dt><span class="section"><a href="#id1168230285217">Build</a></span></dt><dt><span class="section"><a href="#id1168230285232">Install</a></span></dt><dt><span class="section"><a href="#id1168230285255">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="id1168230284849"></a>Building Requirements</h2></div></div></div><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="#id1168229445988">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="#id1168229446178">Download Tar File</a></span></dt><dt><span class="section"><a href="#id1168229446197">Retrieve from Git</a></span></dt><dt><span class="section"><a href="#id1168229446258">Configure before the build</a></span></dt><dt><span class="section"><a href="#id1168229446356">Build</a></span></dt><dt><span class="section"><a href="#id1168229446371">Install</a></span></dt><dt><span class="section"><a href="#id1168229446394">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="id1168229445988"></a>Building Requirements</h2></div></div></div><p>
|
||||
In addition to the run-time requirements, building BIND 10
|
||||
from source code requires various development include headers.
|
||||
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
|
||||
@@ -202,14 +202,14 @@
|
||||
the Git code revision control system or as a downloadable
|
||||
tar file. It may also be available in pre-compiled ready-to-use
|
||||
packages from operating system vendors.
|
||||
</p><div class="section" title="Download Tar File"><div class="titlepage"><div><div><h3 class="title"><a name="id1168230285038"></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="id1168229446178"></a>Download Tar File</h3></div></div></div><p>
|
||||
Downloading a release tar file is the recommended method to
|
||||
obtain the source code.
|
||||
</p><p>
|
||||
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>.
|
||||
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="id1168230285058"></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="id1168229446197"></a>Retrieve from Git</h3></div></div></div><p>
|
||||
Downloading this "bleeding edge" code is recommended only for
|
||||
developers or advanced users. Using development code in a production
|
||||
environment is not recommended.
|
||||
@@ -243,7 +243,7 @@
|
||||
<span class="command"><strong>autoheader</strong></span>,
|
||||
<span class="command"><strong>automake</strong></span>,
|
||||
and related commands.
|
||||
</p></div><div class="section" title="Configure before the build"><div class="titlepage"><div><div><h3 class="title"><a name="id1168230285118"></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="id1168229446258"></a>Configure before the build</h3></div></div></div><p>
|
||||
BIND 10 uses the GNU Build System to discover build environment
|
||||
details.
|
||||
To generate the makefiles using the defaults, simply run:
|
||||
@@ -252,7 +252,7 @@
|
||||
Run <span class="command"><strong>./configure</strong></span> with the <code class="option">--help</code>
|
||||
switch to view the different options. The commonly-used options are:
|
||||
|
||||
</p><div class="variablelist"><dl><dt><span class="term">--prefix</span></dt><dd>Define the the installation location (the
|
||||
</p><div class="variablelist"><dl><dt><span class="term">--prefix</span></dt><dd>Define the installation location (the
|
||||
default is <code class="filename">/usr/local/</code>).
|
||||
</dd><dt><span class="term">--with-boost-include</span></dt><dd>Define the path to find the Boost headers.
|
||||
</dd><dt><span class="term">--with-pythonpath</span></dt><dd>Define the path to Python 3.1 if it is not in the
|
||||
@@ -274,16 +274,16 @@
|
||||
</p><p>
|
||||
If the configure fails, it may be due to missing or old
|
||||
dependencies.
|
||||
</p></div><div class="section" title="Build"><div class="titlepage"><div><div><h3 class="title"><a name="id1168230285217"></a>Build</h3></div></div></div><p>
|
||||
</p></div><div class="section" title="Build"><div class="titlepage"><div><div><h3 class="title"><a name="id1168229446356"></a>Build</h3></div></div></div><p>
|
||||
After the configure step is complete, to build the executables
|
||||
from the C++ code and prepare the Python scripts, run:
|
||||
|
||||
</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="id1168230285232"></a>Install</h3></div></div></div><p>
|
||||
</p></div><div class="section" title="Install"><div class="titlepage"><div><div><h3 class="title"><a name="id1168229446371"></a>Install</h3></div></div></div><p>
|
||||
To install the BIND 10 executables, support files,
|
||||
and documentation, run:
|
||||
</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="id1168230285255"></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="id1168229446394"></a>Install Hierarchy</h3></div></div></div><p>
|
||||
The following is the layout of the complete BIND 10 installation:
|
||||
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
|
||||
<code class="filename">bin/</code> —
|
||||
@@ -314,14 +314,14 @@
|
||||
data source and configuration databases.
|
||||
</li></ul></div><p>
|
||||
</p></div></div></div><div class="chapter" title="Chapter<65>3.<2E>Starting BIND10 with bind10"><div class="titlepage"><div><div><h2 class="title"><a name="bind10"></a>Chapter<EFBFBD>3.<2E>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>
|
||||
BIND 10 provides the <span class="command"><strong>bind10</strong></span> command which
|
||||
BIND 10 provides the <span class="command"><strong>bind10</strong></span> command which
|
||||
starts up the required processes.
|
||||
<span class="command"><strong>bind10</strong></span>
|
||||
will also restart processes that exit unexpectedly.
|
||||
This is the only command needed to start the BIND 10 system.
|
||||
</p><p>
|
||||
After starting the <span class="command"><strong>b10-msgq</strong></span> communications channel,
|
||||
<span class="command"><strong>bind10</strong></span> connects to it,
|
||||
<span class="command"><strong>bind10</strong></span> connects to it,
|
||||
runs the configuration manager, and reads its own configuration.
|
||||
Then it starts the other modules.
|
||||
</p><p>
|
||||
@@ -344,7 +344,12 @@
|
||||
To start the BIND 10 service, simply run <span class="command"><strong>bind10</strong></span>.
|
||||
Run it with the <code class="option">--verbose</code> switch to
|
||||
get additional debugging or diagnostic output.
|
||||
</p></div></div><div class="chapter" title="Chapter<EFBFBD>4.<2E>Command channel"><div class="titlepage"><div><div><h2 class="title"><a name="msgq"></a>Chapter<EFBFBD>4.<2E>Command channel</h2></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>
|
||||
If the setproctitle Python module is detected at start up,
|
||||
the process names for the Python-based daemons will be renamed
|
||||
to better identify them instead of just <span class="quote">“<span class="quote">python</span>”</span>.
|
||||
This is not needed on some operating systems.
|
||||
</p></div></div></div><div class="chapter" title="Chapter<65>4.<2E>Command channel"><div class="titlepage"><div><div><h2 class="title"><a name="msgq"></a>Chapter<EFBFBD>4.<2E>Command channel</h2></div></div></div><p>
|
||||
The BIND 10 components use the <span class="command"><strong>b10-msgq</strong></span>
|
||||
message routing daemon to communicate with other BIND 10 components.
|
||||
The <span class="command"><strong>b10-msgq</strong></span> implements what is called the
|
||||
@@ -500,12 +505,12 @@ shutdown
|
||||
the details and relays (over a <span class="command"><strong>b10-msgq</strong></span> command
|
||||
channel) the configuration on to the specified module.
|
||||
</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="#id1168230285830">Server Configurations</a></span></dt><dt><span class="section"><a href="#id1168230285895">Data Source Backends</a></span></dt><dt><span class="section"><a href="#id1168230285925">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="#id1168229446979">Server Configurations</a></span></dt><dt><span class="section"><a href="#id1168229447044">Data Source Backends</a></span></dt><dt><span class="section"><a href="#id1168229447074">Loading Master Zones Files</a></span></dt></dl></div><p>
|
||||
The <span class="command"><strong>b10-auth</strong></span> is the authoritative DNS server.
|
||||
It supports EDNS0 and DNSSEC. It supports IPv6.
|
||||
Normally it is started by the <span class="command"><strong>bind10</strong></span> master
|
||||
process.
|
||||
</p><div class="section" title="Server Configurations"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168230285830"></a>Server Configurations</h2></div></div></div><p>
|
||||
</p><div class="section" title="Server Configurations"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168229446979"></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-cfgmgr</strong></span> configuration manager.
|
||||
The module name is <span class="quote">“<span class="quote">Auth</span>”</span>.
|
||||
@@ -525,7 +530,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.
|
||||
</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="id1168230285895"></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="id1168229447044"></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>
|
||||
supports a SQLite3 data source backend and in-memory data source
|
||||
backend.
|
||||
@@ -539,7 +544,7 @@ This may be a temporary setting until then.
|
||||
The default is <code class="filename">/usr/local/var/</code>.)
|
||||
This data file location may be changed by defining the
|
||||
<span class="quote">“<span class="quote">database_file</span>”</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="id1168230285925"></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="id1168229447074"></a>Loading Master Zones Files</h2></div></div></div><p>
|
||||
RFC 1035 style DNS master zone files may imported
|
||||
into a BIND 10 data source by using the
|
||||
<span class="command"><strong>b10-loadzone</strong></span> utility.
|
||||
@@ -579,7 +584,7 @@ This may be a temporary setting until then.
|
||||
provide <span class="quote">“<span class="quote">secondary</span>”</span> service.
|
||||
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
|
||||
The current development release of BIND 10 only supports
|
||||
AXFR. (IXFR is not supported.)
|
||||
AXFR. (IXFR is not supported.)
|
||||
|
||||
|
||||
|
||||
@@ -601,7 +606,7 @@ This may be a temporary setting until then.
|
||||
NOTIFY messages to slaves.
|
||||
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
|
||||
The current development release of BIND 10 only supports
|
||||
AXFR. (IXFR is not supported.)
|
||||
AXFR. (IXFR is not supported.)
|
||||
Access control is not yet provided.
|
||||
</p></div></div><div class="chapter" title="Chapter<65>11.<2E>Secondary Manager"><div class="titlepage"><div><div><h2 class="title"><a name="zonemgr"></a>Chapter<EFBFBD>11.<2E>Secondary Manager</h2></div></div></div><p>
|
||||
The <span class="command"><strong>b10-zonemgr</strong></span> process is started by
|
||||
@@ -617,13 +622,13 @@ This may be a temporary setting until then.
|
||||
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
|
||||
Access control (such as allowing notifies) is not yet provided.
|
||||
The primary/secondary service is not yet complete.
|
||||
</p></div></div><div class="chapter" title="Chapter<65>12.<2E>Recursive Name Server"><div class="titlepage"><div><div><h2 class="title"><a name="resolverserver"></a>Chapter<EFBFBD>12.<2E>Recursive Name Server</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id1168230286381">Forwarding</a></span></dt></dl></div><p>
|
||||
</p></div></div><div class="chapter" title="Chapter<65>12.<2E>Recursive Name Server"><div class="titlepage"><div><div><h2 class="title"><a name="resolverserver"></a>Chapter<EFBFBD>12.<2E>Recursive Name Server</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id1168229447556">Access Control</a></span></dt><dt><span class="section"><a href="#id1168229447671">Forwarding</a></span></dt></dl></div><p>
|
||||
The <span class="command"><strong>b10-resolver</strong></span> process is started by
|
||||
<span class="command"><strong>bind10</strong></span>.
|
||||
|
||||
</p><p>
|
||||
The main <span class="command"><strong>bind10</strong></span> process can be configured
|
||||
to select to run either the authoritative or resolver.
|
||||
to select to run either the authoritative or resolver or both.
|
||||
By default, it starts the authoritative service.
|
||||
|
||||
|
||||
@@ -639,14 +644,52 @@ This may be a temporary setting until then.
|
||||
The master <span class="command"><strong>bind10</strong></span> will stop and start
|
||||
the desired services.
|
||||
</p><p>
|
||||
The resolver also needs to be configured to listen on an address
|
||||
and port:
|
||||
By default, the resolver listens on port 53 for 127.0.0.1 and ::1.
|
||||
The following example shows how it can be configured to
|
||||
listen on an additional address (and port):
|
||||
|
||||
</p><pre class="screen">
|
||||
> <strong class="userinput"><code>config set Resolver/listen_on [{ "address": "127.0.0.1", "port": 53 }]</code></strong>
|
||||
> <strong class="userinput"><code>config add Resolver/listen_on</code></strong>
|
||||
> <strong class="userinput"><code>config set Resolver/listen_on[<em class="replaceable"><code>2</code></em>]/address "192.168.1.1"</code></strong>
|
||||
> <strong class="userinput"><code>config set Resolver/listen_on[<em class="replaceable"><code>2</code></em>]/port 53</code></strong>
|
||||
> <strong class="userinput"><code>config commit</code></strong>
|
||||
</pre><p>
|
||||
</p><div class="section" title="Forwarding"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168230286381"></a>Forwarding</h2></div></div></div><p>
|
||||
</p><p>(Replace the <span class="quote">“<span class="quote"><em class="replaceable"><code>2</code></em></span>”</span>
|
||||
as needed; run <span class="quote">“<span class="quote"><strong class="userinput"><code>config show
|
||||
Resolver/listen_on</code></strong></span>”</span> if needed.)</p><div class="section" title="Access Control"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168229447556"></a>Access Control</h2></div></div></div><p>
|
||||
By default, the <span class="command"><strong>b10-resolver</strong></span> daemon only accepts
|
||||
DNS queries from the localhost (127.0.0.1 and ::1).
|
||||
The <code class="option">Resolver/query_acl</code> configuration may
|
||||
be used to reject, drop, or allow specific IPs or networks.
|
||||
This configuration list is first match.
|
||||
</p><p>
|
||||
The configuration's <code class="option">action</code> item may be
|
||||
set to <span class="quote">“<span class="quote">ACCEPT</span>”</span> to allow the incoming query,
|
||||
<span class="quote">“<span class="quote">REJECT</span>”</span> to respond with a DNS REFUSED return
|
||||
code, or <span class="quote">“<span class="quote">DROP</span>”</span> to ignore the query without
|
||||
any response (such as a blackhole). For more information,
|
||||
see the respective debugging messages: <a class="ulink" href="bind10-messages.html#RESOLVER_QUERY_ACCEPTED" target="_top">RESOLVER_QUERY_ACCEPTED</a>,
|
||||
<a class="ulink" href="bind10-messages.html#RESOLVER_QUERY_REJECTED" target="_top">RESOLVER_QUERY_REJECTED</a>,
|
||||
and <a class="ulink" href="bind10-messages.html#RESOLVER_QUERY_DROPPED" target="_top">RESOLVER_QUERY_DROPPED</a>.
|
||||
</p><p>
|
||||
The required configuration's <code class="option">from</code> item is set
|
||||
to an IPv4 or IPv6 address, addresses with an network mask, or to
|
||||
the special lowercase keywords <span class="quote">“<span class="quote">any6</span>”</span> (for
|
||||
any IPv6 address) or <span class="quote">“<span class="quote">any4</span>”</span> (for any IPv4
|
||||
address).
|
||||
</p><p>
|
||||
For example to allow the <em class="replaceable"><code>192.168.1.0/24</code></em>
|
||||
network to use your recursive name server, at the
|
||||
<span class="command"><strong>bindctl</strong></span> prompt run:
|
||||
</p><pre class="screen">
|
||||
> <strong class="userinput"><code>config add Resolver/query_acl</code></strong>
|
||||
> <strong class="userinput"><code>config set Resolver/query_acl[<em class="replaceable"><code>2</code></em>]/action "ACCEPT"</code></strong>
|
||||
> <strong class="userinput"><code>config set Resolver/query_acl[<em class="replaceable"><code>2</code></em>]/from "<em class="replaceable"><code>192.168.1.0/24</code></em>"</code></strong>
|
||||
> <strong class="userinput"><code>config commit</code></strong>
|
||||
</pre><p>(Replace the <span class="quote">“<span class="quote"><em class="replaceable"><code>2</code></em></span>”</span>
|
||||
as needed; run <span class="quote">“<span class="quote"><strong class="userinput"><code>config show
|
||||
Resolver/query_acl</code></strong></span>”</span> if needed.)</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>This prototype access control configuration
|
||||
syntax may be changed.</p></div></div><div class="section" title="Forwarding"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168229447671"></a>Forwarding</h2></div></div></div><p>
|
||||
|
||||
To enable forwarding, the upstream address and port must be
|
||||
configured to forward queries to, such as:
|
||||
@@ -694,48 +737,414 @@ This may be a temporary setting until then.
|
||||
"stats.timestamp": 1295543046.823504
|
||||
}
|
||||
</pre><p>
|
||||
</p></div><div class="chapter" title="Chapter<65>14.<2E>Logging"><div class="titlepage"><div><div><h2 class="title"><a name="logging"></a>Chapter<EFBFBD>14.<2E>Logging</h2></div></div></div><p>
|
||||
Each message written by BIND 10 to the configured logging destinations
|
||||
comprises a number of components that identify the origin of the
|
||||
message and, if the message indicates a problem, information about the
|
||||
problem that may be useful in fixing it.
|
||||
</p><p>
|
||||
Consider the message below logged to a file:
|
||||
</p><pre class="screen">2011-06-15 13:48:22.034 ERROR [b10-resolver.asiolink]
|
||||
ASIODNS_OPENSOCK error 111 opening TCP socket to 127.0.0.1(53)</pre><p>
|
||||
</p><p>
|
||||
Note: the layout of messages written to the system logging
|
||||
file (syslog) may be slightly different. This message has
|
||||
been split across two lines here for display reasons; in the
|
||||
logging file, it will appear on one line.)
|
||||
</p><p>
|
||||
The log message comprises a number of components:
|
||||
</p></div><div class="chapter" title="Chapter<65>14.<2E>Logging"><div class="titlepage"><div><div><h2 class="title"><a name="logging"></a>Chapter<EFBFBD>14.<2E>Logging</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id1168229447788">Logging configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#id1168229447799">Loggers</a></span></dt><dt><span class="section"><a href="#id1168229448040">Output Options</a></span></dt><dt><span class="section"><a href="#id1168229448215">Example session</a></span></dt></dl></dd><dt><span class="section"><a href="#id1168229448428">Logging Message Format</a></span></dt></dl></div><div class="section" title="Logging configuration"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168229447788"></a>Logging configuration</h2></div></div></div><p>
|
||||
|
||||
</p><div class="variablelist"><dl><dt><span class="term">2011-06-15 13:48:22.034</span></dt><dd><p>
|
||||
The date and time at which the message was generated.
|
||||
</p></dd><dt><span class="term">ERROR</span></dt><dd><p>
|
||||
The severity of the message.
|
||||
</p></dd><dt><span class="term">[b10-resolver.asiolink]</span></dt><dd><p>
|
||||
The source of the message. This comprises two components:
|
||||
the BIND 10 process generating the message (in this
|
||||
case, <span class="command"><strong>b10-resolver</strong></span>) and the module
|
||||
within the program from which the message originated
|
||||
(which in the example is the asynchronous I/O link
|
||||
module, asiolink).
|
||||
</p></dd><dt><span class="term">ASIODNS_OPENSOCK</span></dt><dd><p>
|
||||
The logging system in BIND 10 is configured through the
|
||||
Logging module. All BIND 10 modules will look at the
|
||||
configuration in Logging to see what should be logged and
|
||||
to where.
|
||||
|
||||
|
||||
|
||||
</p><div class="section" title="Loggers"><div class="titlepage"><div><div><h3 class="title"><a name="id1168229447799"></a>Loggers</h3></div></div></div><p>
|
||||
|
||||
Within BIND 10, a message is logged through a component
|
||||
called a "logger". Different parts of BIND 10 log messages
|
||||
through different loggers, and each logger can be configured
|
||||
independently of one another.
|
||||
|
||||
</p><p>
|
||||
|
||||
In the Logging module, you can specify the configuration
|
||||
for zero or more loggers; any that are not specified will
|
||||
take appropriate default values..
|
||||
|
||||
</p><p>
|
||||
|
||||
The three most important elements of a logger configuration
|
||||
are the <code class="option">name</code> (the component that is
|
||||
generating the messages), the <code class="option">severity</code>
|
||||
(what to log), and the <code class="option">output_options</code>
|
||||
(where to log).
|
||||
|
||||
</p><div class="section" title="name (string)"><div class="titlepage"><div><div><h4 class="title"><a name="id1168229447824"></a>name (string)</h4></div></div></div><p>
|
||||
Each logger in the system has a name, the name being that
|
||||
of the component using it to log messages. For instance,
|
||||
if you want to configure logging for the resolver module,
|
||||
you add an entry for a logger named <span class="quote">“<span class="quote">Resolver</span>”</span>. This
|
||||
configuration will then be used by the loggers in the
|
||||
Resolver module, and all the libraries used by it.
|
||||
</p><p>
|
||||
|
||||
If you want to specify logging for one specific library
|
||||
within the module, you set the name to
|
||||
<em class="replaceable"><code>module.library</code></em>. For example, the
|
||||
logger used by the nameserver address store component
|
||||
has the full name of <span class="quote">“<span class="quote">Resolver.nsas</span>”</span>. If
|
||||
there is no entry in Logging for a particular library,
|
||||
it will use the configuration given for the module.
|
||||
|
||||
|
||||
|
||||
</p><p>
|
||||
|
||||
|
||||
|
||||
To illustrate this, suppose you want the cache library
|
||||
to log messages of severity DEBUG, and the rest of the
|
||||
resolver code to log messages of severity INFO. To achieve
|
||||
this you specify two loggers, one with the name
|
||||
<span class="quote">“<span class="quote">Resolver</span>”</span> and severity INFO, and one with
|
||||
the name <span class="quote">“<span class="quote">Resolver.cache</span>”</span> with severity
|
||||
DEBUG. As there are no entries for other libraries (e.g.
|
||||
the nsas), they will use the configuration for the module
|
||||
(<span class="quote">“<span class="quote">Resolver</span>”</span>), so giving the desired behavior.
|
||||
|
||||
</p><p>
|
||||
|
||||
One special case is that of a module name of <span class="quote">“<span class="quote">*</span>”</span>
|
||||
(asterisks), which is interpreted as <span class="emphasis"><em>any</em></span>
|
||||
module. You can set global logging options by using this,
|
||||
including setting the logging configuration for a library
|
||||
that is used by multiple modules (e.g. <span class="quote">“<span class="quote">*.config</span>”</span>
|
||||
specifies the configuration library code in whatever
|
||||
module is using it).
|
||||
|
||||
</p><p>
|
||||
|
||||
If there are multiple logger specifications in the
|
||||
configuration that might match a particular logger, the
|
||||
specification with the more specific logger name takes
|
||||
precedence. For example, if there are entries for for
|
||||
both <span class="quote">“<span class="quote">*</span>”</span> and <span class="quote">“<span class="quote">Resolver</span>”</span>, the
|
||||
resolver module — and all libraries it uses —
|
||||
will log messages according to the configuration in the
|
||||
second entry (<span class="quote">“<span class="quote">Resolver</span>”</span>). All other modules
|
||||
will use the configuration of the first entry
|
||||
(<span class="quote">“<span class="quote">*</span>”</span>). If there was also a configuration
|
||||
entry for <span class="quote">“<span class="quote">Resolver.cache</span>”</span>, the cache library
|
||||
within the resolver would use that in preference to the
|
||||
entry for <span class="quote">“<span class="quote">Resolver</span>”</span>.
|
||||
|
||||
</p><p>
|
||||
|
||||
One final note about the naming. When specifying the
|
||||
module name within a logger, use the name of the module
|
||||
as specified in <span class="command"><strong>bindctl</strong></span>, e.g.
|
||||
<span class="quote">“<span class="quote">Resolver</span>”</span> for the resolver module,
|
||||
<span class="quote">“<span class="quote">Xfrout</span>”</span> for the xfrout module, etc. When
|
||||
the message is logged, the message will include the name
|
||||
of the logger generating the message, but with the module
|
||||
name replaced by the name of the process implementing
|
||||
the module (so for example, a message generated by the
|
||||
<span class="quote">“<span class="quote">Auth.cache</span>”</span> logger will appear in the output
|
||||
with a logger name of <span class="quote">“<span class="quote">b10-auth.cache</span>”</span>).
|
||||
|
||||
</p></div><div class="section" title="severity (string)"><div class="titlepage"><div><div><h4 class="title"><a name="id1168229447923"></a>severity (string)</h4></div></div></div><p>
|
||||
|
||||
This specifies the category of messages logged.
|
||||
Each message is logged with an associated severity which
|
||||
may be one of the following (in descending order of
|
||||
severity):
|
||||
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"> FATAL </li><li class="listitem"> ERROR </li><li class="listitem"> WARN </li><li class="listitem"> INFO </li><li class="listitem"> DEBUG </li></ul></div><p>
|
||||
|
||||
When the severity of a logger is set to one of these
|
||||
values, it will only log messages of that severity, and
|
||||
the severities above it. The severity may also be set to
|
||||
NONE, in which case all messages from that logger are
|
||||
inhibited.
|
||||
|
||||
|
||||
|
||||
</p></div><div class="section" title="output_options (list)"><div class="titlepage"><div><div><h4 class="title"><a name="id1168229447973"></a>output_options (list)</h4></div></div></div><p>
|
||||
|
||||
Each logger can have zero or more
|
||||
<code class="option">output_options</code>. These specify where log
|
||||
messages are sent to. These are explained in detail below.
|
||||
|
||||
</p><p>
|
||||
|
||||
The other options for a logger are:
|
||||
|
||||
</p></div><div class="section" title="debuglevel (integer)"><div class="titlepage"><div><div><h4 class="title"><a name="id1168229447990"></a>debuglevel (integer)</h4></div></div></div><p>
|
||||
|
||||
When a logger's severity is set to DEBUG, this value
|
||||
specifies what debug messages should be printed. It ranges
|
||||
from 0 (least verbose) to 99 (most verbose).
|
||||
</p><p>
|
||||
|
||||
If severity for the logger is not DEBUG, this value is ignored.
|
||||
|
||||
</p></div><div class="section" title="additive (true or false)"><div class="titlepage"><div><div><h4 class="title"><a name="id1168229448005"></a>additive (true or false)</h4></div></div></div><p>
|
||||
|
||||
If this is true, the <code class="option">output_options</code> from
|
||||
the parent will be used. For example, if there are two
|
||||
loggers configured; <span class="quote">“<span class="quote">Resolver</span>”</span> and
|
||||
<span class="quote">“<span class="quote">Resolver.cache</span>”</span>, and <code class="option">additive</code>
|
||||
is true in the second, it will write the log messages
|
||||
not only to the destinations specified for
|
||||
<span class="quote">“<span class="quote">Resolver.cache</span>”</span>, but also to the destinations
|
||||
as specified in the <code class="option">output_options</code> in
|
||||
the logger named <span class="quote">“<span class="quote">Resolver</span>”</span>.
|
||||
|
||||
|
||||
|
||||
</p></div></div><div class="section" title="Output Options"><div class="titlepage"><div><div><h3 class="title"><a name="id1168229448040"></a>Output Options</h3></div></div></div><p>
|
||||
|
||||
The main settings for an output option are the
|
||||
<code class="option">destination</code> and a value called
|
||||
<code class="option">output</code>, the meaning of which depends on
|
||||
the destination that is set.
|
||||
|
||||
</p><div class="section" title="destination (string)"><div class="titlepage"><div><div><h4 class="title"><a name="id1168229448056"></a>destination (string)</h4></div></div></div><p>
|
||||
|
||||
The destination is the type of output. It can be one of:
|
||||
|
||||
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"> console </li><li class="listitem"> file </li><li class="listitem"> syslog </li></ul></div></div><div class="section" title="output (string)"><div class="titlepage"><div><div><h4 class="title"><a name="id1168229448088"></a>output (string)</h4></div></div></div><p>
|
||||
|
||||
Depending on what is set as the output destination, this
|
||||
value is interpreted as follows:
|
||||
|
||||
</p><div class="variablelist"><dl><dt><span class="term"><code class="option">destination</code> is <span class="quote">“<span class="quote">console</span>”</span></span></dt><dd>
|
||||
The value of output must be one of <span class="quote">“<span class="quote">stdout</span>”</span>
|
||||
(messages printed to standard output) or
|
||||
<span class="quote">“<span class="quote">stderr</span>”</span> (messages printed to standard
|
||||
error).
|
||||
</dd><dt><span class="term"><code class="option">destination</code> is <span class="quote">“<span class="quote">file</span>”</span></span></dt><dd>
|
||||
The value of output is interpreted as a file name;
|
||||
log messages will be appended to this file.
|
||||
</dd><dt><span class="term"><code class="option">destination</code> is <span class="quote">“<span class="quote">syslog</span>”</span></span></dt><dd>
|
||||
The value of output is interpreted as the
|
||||
<span class="command"><strong>syslog</strong></span> facility (e.g.
|
||||
<span class="emphasis"><em>local0</em></span>) that should be used
|
||||
for log messages.
|
||||
</dd></dl></div><p>
|
||||
|
||||
The other options for <code class="option">output_options</code> are:
|
||||
|
||||
</p><div class="section" title="flush (true of false)"><div class="titlepage"><div><div><h5 class="title"><a name="id1168229448172"></a>flush (true of false)</h5></div></div></div><p>
|
||||
Flush buffers after each log message. Doing this will
|
||||
reduce performance but will ensure that if the program
|
||||
terminates abnormally, all messages up to the point of
|
||||
termination are output.
|
||||
</p></div><div class="section" title="maxsize (integer)"><div class="titlepage"><div><div><h5 class="title"><a name="id1168229448182"></a>maxsize (integer)</h5></div></div></div><p>
|
||||
Only relevant when destination is file, this is maximum
|
||||
file size of output files in bytes. When the maximum
|
||||
size is reached, the file is renamed and a new file opened.
|
||||
(For example, a ".1" is appended to the name —
|
||||
if a ".1" file exists, it is renamed ".2",
|
||||
etc.)
|
||||
</p><p>
|
||||
If this is 0, no maximum file size is used.
|
||||
</p></div><div class="section" title="maxver (integer)"><div class="titlepage"><div><div><h5 class="title"><a name="id1168229448196"></a>maxver (integer)</h5></div></div></div><p>
|
||||
Maximum number of old log files to keep around when
|
||||
rolling the output file. Only relevant when
|
||||
<code class="option">destination</code> is <span class="quote">“<span class="quote">file</span>”</span>.
|
||||
</p></div></div></div><div class="section" title="Example session"><div class="titlepage"><div><div><h3 class="title"><a name="id1168229448215"></a>Example session</h3></div></div></div><p>
|
||||
|
||||
In this example we want to set the global logging to
|
||||
write to the file <code class="filename">/var/log/my_bind10.log</code>,
|
||||
at severity WARN. We want the authoritative server to
|
||||
log at DEBUG with debuglevel 40, to a different file
|
||||
(<code class="filename">/tmp/debug_messages</code>).
|
||||
|
||||
</p><p>
|
||||
|
||||
Start <span class="command"><strong>bindctl</strong></span>.
|
||||
|
||||
</p><p>
|
||||
|
||||
</p><pre class="screen">["login success "]
|
||||
> <strong class="userinput"><code>config show Logging</code></strong>
|
||||
Logging/loggers [] list
|
||||
</pre><p>
|
||||
|
||||
</p><p>
|
||||
|
||||
By default, no specific loggers are configured, in which
|
||||
case the severity defaults to INFO and the output is
|
||||
written to stderr.
|
||||
|
||||
</p><p>
|
||||
|
||||
Let's first add a default logger:
|
||||
|
||||
</p><p>
|
||||
|
||||
</p><pre class="screen"><strong class="userinput"><code>> config add Logging/loggers</code></strong>
|
||||
> <strong class="userinput"><code>config show Logging</code></strong>
|
||||
Logging/loggers/ list (modified)
|
||||
</pre><p>
|
||||
|
||||
</p><p>
|
||||
|
||||
The loggers value line changed to indicate that it is no
|
||||
longer an empty list:
|
||||
|
||||
</p><p>
|
||||
|
||||
</p><pre class="screen">> <strong class="userinput"><code>config show Logging/loggers</code></strong>
|
||||
Logging/loggers[0]/name "" string (default)
|
||||
Logging/loggers[0]/severity "INFO" string (default)
|
||||
Logging/loggers[0]/debuglevel 0 integer (default)
|
||||
Logging/loggers[0]/additive false boolean (default)
|
||||
Logging/loggers[0]/output_options [] list (default)
|
||||
</pre><p>
|
||||
|
||||
</p><p>
|
||||
|
||||
The name is mandatory, so we must set it. We will also
|
||||
change the severity as well. Let's start with the global
|
||||
logger.
|
||||
|
||||
</p><p>
|
||||
|
||||
</p><pre class="screen">> <strong class="userinput"><code>config set Logging/loggers[0]/name *</code></strong>
|
||||
> <strong class="userinput"><code>config set Logging/loggers[0]/severity WARN</code></strong>
|
||||
> <strong class="userinput"><code>config show Logging/loggers</code></strong>
|
||||
Logging/loggers[0]/name "*" string (modified)
|
||||
Logging/loggers[0]/severity "WARN" string (modified)
|
||||
Logging/loggers[0]/debuglevel 0 integer (default)
|
||||
Logging/loggers[0]/additive false boolean (default)
|
||||
Logging/loggers[0]/output_options [] list (default)
|
||||
</pre><p>
|
||||
|
||||
</p><p>
|
||||
|
||||
Of course, we need to specify where we want the log
|
||||
messages to go, so we add an entry for an output option.
|
||||
|
||||
</p><p>
|
||||
|
||||
</p><pre class="screen">> <strong class="userinput"><code> config add Logging/loggers[0]/output_options</code></strong>
|
||||
> <strong class="userinput"><code> config show Logging/loggers[0]/output_options</code></strong>
|
||||
Logging/loggers[0]/output_options[0]/destination "console" string (default)
|
||||
Logging/loggers[0]/output_options[0]/output "stdout" string (default)
|
||||
Logging/loggers[0]/output_options[0]/flush false boolean (default)
|
||||
Logging/loggers[0]/output_options[0]/maxsize 0 integer (default)
|
||||
Logging/loggers[0]/output_options[0]/maxver 0 integer (default)
|
||||
</pre><p>
|
||||
|
||||
|
||||
</p><p>
|
||||
|
||||
These aren't the values we are looking for.
|
||||
|
||||
</p><p>
|
||||
|
||||
</p><pre class="screen">> <strong class="userinput"><code> config set Logging/loggers[0]/output_options[0]/destination file</code></strong>
|
||||
> <strong class="userinput"><code> config set Logging/loggers[0]/output_options[0]/output /var/log/bind10.log</code></strong>
|
||||
> <strong class="userinput"><code> config set Logging/loggers[0]/output_options[0]/maxsize 30000</code></strong>
|
||||
> <strong class="userinput"><code> config set Logging/loggers[0]/output_options[0]/maxver 8</code></strong>
|
||||
</pre><p>
|
||||
|
||||
</p><p>
|
||||
|
||||
Which would make the entire configuration for this logger
|
||||
look like:
|
||||
|
||||
</p><p>
|
||||
|
||||
</p><pre class="screen">> <strong class="userinput"><code> config show all Logging/loggers</code></strong>
|
||||
Logging/loggers[0]/name "*" string (modified)
|
||||
Logging/loggers[0]/severity "WARN" string (modified)
|
||||
Logging/loggers[0]/debuglevel 0 integer (default)
|
||||
Logging/loggers[0]/additive false boolean (default)
|
||||
Logging/loggers[0]/output_options[0]/destination "file" string (modified)
|
||||
Logging/loggers[0]/output_options[0]/output "/var/log/bind10.log" string (modified)
|
||||
Logging/loggers[0]/output_options[0]/flush false boolean (default)
|
||||
Logging/loggers[0]/output_options[0]/maxsize 30000 integer (modified)
|
||||
Logging/loggers[0]/output_options[0]/maxver 8 integer (modified)
|
||||
</pre><p>
|
||||
|
||||
</p><p>
|
||||
|
||||
That looks OK, so let's commit it before we add the
|
||||
configuration for the authoritative server's logger.
|
||||
|
||||
</p><p>
|
||||
|
||||
</p><pre class="screen">> <strong class="userinput"><code> config commit</code></strong></pre><p>
|
||||
|
||||
</p><p>
|
||||
|
||||
Now that we have set it, and checked each value along
|
||||
the way, adding a second entry is quite similar.
|
||||
|
||||
</p><p>
|
||||
|
||||
</p><pre class="screen">> <strong class="userinput"><code> config add Logging/loggers</code></strong>
|
||||
> <strong class="userinput"><code> config set Logging/loggers[1]/name Auth</code></strong>
|
||||
> <strong class="userinput"><code> config set Logging/loggers[1]/severity DEBUG</code></strong>
|
||||
> <strong class="userinput"><code> config set Logging/loggers[1]/debuglevel 40</code></strong>
|
||||
> <strong class="userinput"><code> config add Logging/loggers[1]/output_options</code></strong>
|
||||
> <strong class="userinput"><code> config set Logging/loggers[1]/output_options[0]/destination file</code></strong>
|
||||
> <strong class="userinput"><code> config set Logging/loggers[1]/output_options[0]/output /tmp/auth_debug.log</code></strong>
|
||||
> <strong class="userinput"><code> config commit</code></strong>
|
||||
</pre><p>
|
||||
|
||||
</p><p>
|
||||
|
||||
And that's it. Once we have found whatever it was we
|
||||
needed the debug messages for, we can simply remove the
|
||||
second logger to let the authoritative server use the
|
||||
same settings as the rest.
|
||||
|
||||
</p><p>
|
||||
|
||||
</p><pre class="screen">> <strong class="userinput"><code> config remove Logging/loggers[1]</code></strong>
|
||||
> <strong class="userinput"><code> config commit</code></strong>
|
||||
</pre><p>
|
||||
|
||||
</p><p>
|
||||
|
||||
And every module will now be using the values from the
|
||||
logger named <span class="quote">“<span class="quote">*</span>”</span>.
|
||||
|
||||
</p></div></div><div class="section" title="Logging Message Format"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168229448428"></a>Logging Message Format</h2></div></div></div><p>
|
||||
Each message written by BIND 10 to the configured logging
|
||||
destinations comprises a number of components that identify
|
||||
the origin of the message and, if the message indicates
|
||||
a problem, information about the problem that may be
|
||||
useful in fixing it.
|
||||
</p><p>
|
||||
Consider the message below logged to a file:
|
||||
</p><pre class="screen">2011-06-15 13:48:22.034 ERROR [b10-resolver.asiolink]
|
||||
ASIODNS_OPENSOCK error 111 opening TCP socket to 127.0.0.1(53)</pre><p>
|
||||
</p><p>
|
||||
Note: the layout of messages written to the system logging
|
||||
file (syslog) may be slightly different. This message has
|
||||
been split across two lines here for display reasons; in the
|
||||
logging file, it will appear on one line.)
|
||||
</p><p>
|
||||
The log message comprises a number of components:
|
||||
|
||||
</p><div class="variablelist"><dl><dt><span class="term">2011-06-15 13:48:22.034</span></dt><dd><p>
|
||||
The date and time at which the message was generated.
|
||||
</p></dd><dt><span class="term">ERROR</span></dt><dd><p>
|
||||
The severity of the message.
|
||||
</p></dd><dt><span class="term">[b10-resolver.asiolink]</span></dt><dd><p>
|
||||
The source of the message. This comprises two components:
|
||||
the BIND 10 process generating the message (in this
|
||||
case, <span class="command"><strong>b10-resolver</strong></span>) and the module
|
||||
within the program from which the message originated
|
||||
(which in the example is the asynchronous I/O link
|
||||
module, asiolink).
|
||||
</p></dd><dt><span class="term">ASIODNS_OPENSOCK</span></dt><dd><p>
|
||||
The message identification. Every message in BIND 10
|
||||
has a unique identification, which can be used as an
|
||||
index into the <a class="ulink" href="bind10-messages.html" target="_top"><em class="citetitle">BIND 10 Messages
|
||||
Manual</em></a> (<a class="ulink" href="http://bind10.isc.org/docs/bind10-messages.html" target="_top">http://bind10.isc.org/docs/bind10-messages.html</a>) from which more information can be obtained.
|
||||
</p></dd><dt><span class="term">error 111 opening TCP socket to 127.0.0.1(53)</span></dt><dd><p>
|
||||
A brief description of the cause of the problem. Within this text,
|
||||
information relating to the condition that caused the message to
|
||||
be logged will be included. In this example, error number 111
|
||||
(an operating system-specific error number) was encountered when
|
||||
trying to open a TCP connection to port 53 on the local system
|
||||
(address 127.0.0.1). The next step would be to find out the reason
|
||||
for the failure by consulting your system's documentation to
|
||||
identify what error number 111 means.
|
||||
</p></dd></dl></div><p>
|
||||
|
||||
</p></div></div></body></html>
|
||||
</p></dd><dt><span class="term">error 111 opening TCP socket to 127.0.0.1(53)</span></dt><dd><p>
|
||||
A brief description of the cause of the problem.
|
||||
Within this text, information relating to the condition
|
||||
that caused the message to be logged will be included.
|
||||
In this example, error number 111 (an operating
|
||||
system-specific error number) was encountered when
|
||||
trying to open a TCP connection to port 53 on the
|
||||
local system (address 127.0.0.1). The next step
|
||||
would be to find out the reason for the failure by
|
||||
consulting your system's documentation to identify
|
||||
what error number 111 means.
|
||||
</p></dd></dl></div><p>
|
||||
</p></div></div></div></body></html>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@@ -2,12 +2,12 @@
|
||||
.\" Title: bind10
|
||||
.\" Author: [see the "AUTHORS" section]
|
||||
.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
|
||||
.\" Date: March 31, 2011
|
||||
.\" Date: August 11, 2011
|
||||
.\" Manual: BIND10
|
||||
.\" Source: BIND10
|
||||
.\" Language: English
|
||||
.\"
|
||||
.TH "BIND10" "8" "March 31, 2011" "BIND10" "BIND10"
|
||||
.TH "BIND10" "8" "August 11, 2011" "BIND10" "BIND10"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * set default formatting
|
||||
.\" -----------------------------------------------------------------
|
||||
@@ -107,6 +107,18 @@ Display more about what is going on for
|
||||
\fBbind10\fR
|
||||
and its child processes\&.
|
||||
.RE
|
||||
.SH "STATISTICS DATA"
|
||||
.PP
|
||||
The statistics data collected by the
|
||||
\fBb10\-stats\fR
|
||||
daemon include:
|
||||
.PP
|
||||
bind10\&.boot_time
|
||||
.RS 4
|
||||
The date and time that the
|
||||
\fBbind10\fR
|
||||
process started\&. This is represented in ISO 8601 format\&.
|
||||
.RE
|
||||
.SH "SEE ALSO"
|
||||
.PP
|
||||
|
||||
|
||||
@@ -2,12 +2,12 @@
|
||||
.\" Title: b10-resolver
|
||||
.\" Author: [FIXME: author] [see http://docbook.sf.net/el/author]
|
||||
.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
|
||||
.\" Date: February 17, 2011
|
||||
.\" Date: August 17, 2011
|
||||
.\" Manual: BIND10
|
||||
.\" Source: BIND10
|
||||
.\" Language: English
|
||||
.\"
|
||||
.TH "B10\-RESOLVER" "8" "February 17, 2011" "BIND10" "BIND10"
|
||||
.TH "B10\-RESOLVER" "8" "August 17, 2011" "BIND10" "BIND10"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * set default formatting
|
||||
.\" -----------------------------------------------------------------
|
||||
@@ -54,7 +54,7 @@ must be either a valid numeric user ID or a valid user name\&. By default the da
|
||||
.PP
|
||||
\fB\-v\fR
|
||||
.RS 4
|
||||
Enabled verbose mode\&. This enables diagnostic messages to STDERR\&.
|
||||
Enable verbose mode\&. This sets logging to the maximum debugging level\&.
|
||||
.RE
|
||||
.SH "CONFIGURATION AND COMMANDS"
|
||||
.PP
|
||||
@@ -77,6 +77,25 @@ string and
|
||||
number\&. The defaults are address ::1 port 53 and address 127\&.0\&.0\&.1 port 53\&.
|
||||
.PP
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
\fIquery_acl\fR
|
||||
is a list of query access control rules\&. The list items are the
|
||||
\fIaction\fR
|
||||
string and the
|
||||
\fIfrom\fR
|
||||
or
|
||||
\fIkey\fR
|
||||
strings\&. The possible actions are ACCEPT, REJECT and DROP\&. The
|
||||
\fIfrom\fR
|
||||
is a remote (source) IPv4 or IPv6 address or special keyword\&. The
|
||||
\fIkey\fR
|
||||
is a TSIG key name\&. The default configuration accepts queries from 127\&.0\&.0\&.1 and ::1\&.
|
||||
.PP
|
||||
|
||||
\fIretries\fR
|
||||
is the number of times to retry (resend query) after a query timeout (\fItimeout_query\fR)\&. The default is 3\&.
|
||||
.PP
|
||||
@@ -88,7 +107,7 @@ to use directly as root servers to start resolving\&. The list items are the
|
||||
\fIaddress\fR
|
||||
string and
|
||||
\fIport\fR
|
||||
number\&. If empty, a hardcoded address for F\-root (192\&.5\&.5\&.241) is used\&.
|
||||
number\&. By default, a hardcoded address for l\&.root\-servers\&.net (199\&.7\&.83\&.42 or 2001:500:3::42) is used\&.
|
||||
.PP
|
||||
|
||||
\fItimeout_client\fR
|
||||
@@ -121,8 +140,7 @@ BIND 10 Guide\&.
|
||||
.PP
|
||||
The
|
||||
\fBb10\-resolver\fR
|
||||
daemon was first coded in September 2010\&. The initial implementation only provided forwarding\&. Iteration was introduced in January 2011\&.
|
||||
|
||||
daemon was first coded in September 2010\&. The initial implementation only provided forwarding\&. Iteration was introduced in January 2011\&. Caching was implemented in February 2011\&. Access control was introduced in June 2011\&.
|
||||
.SH "COPYRIGHT"
|
||||
.br
|
||||
Copyright \(co 2010 Internet Systems Consortium, Inc. ("ISC")
|
||||
|
||||
@@ -1,22 +1,13 @@
|
||||
'\" t
|
||||
.\" Title: b10-stats
|
||||
.\" Author: [FIXME: author] [see http://docbook.sf.net/el/author]
|
||||
.\" Generator: DocBook XSL Stylesheets v1.76.1 <http://docbook.sf.net/>
|
||||
.\" Date: Oct 15, 2010
|
||||
.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
|
||||
.\" Date: August 11, 2011
|
||||
.\" Manual: BIND10
|
||||
.\" Source: BIND10
|
||||
.\" Language: English
|
||||
.\"
|
||||
.TH "B10\-STATS" "8" "Oct 15, 2010" "BIND10" "BIND10"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * Define some portability stuff
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
.\" http://bugs.debian.org/507673
|
||||
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
|
||||
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
.ie \n(.g .ds Aq \(aq
|
||||
.el .ds Aq '
|
||||
.TH "B10\-STATS" "8" "August 11, 2011" "BIND10" "BIND10"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * set default formatting
|
||||
.\" -----------------------------------------------------------------
|
||||
@@ -47,7 +38,7 @@ and so on\&. It waits for coming data from other modules, then other modules sen
|
||||
\fBb10\-stats\fR
|
||||
invokes "sendstats" command for
|
||||
\fBbind10\fR
|
||||
after its initial starting because it\*(Aqs sure to collect statistics data from
|
||||
after its initial starting because it\'s sure to collect statistics data from
|
||||
\fBbind10\fR\&.
|
||||
.SH "OPTIONS"
|
||||
.PP
|
||||
@@ -59,6 +50,84 @@ This
|
||||
\fBb10\-stats\fR
|
||||
switches to verbose mode\&. It sends verbose messages to STDOUT\&.
|
||||
.RE
|
||||
.SH "CONFIGURATION AND COMMANDS"
|
||||
.PP
|
||||
The
|
||||
\fBb10\-stats\fR
|
||||
command does not have any configurable settings\&.
|
||||
.PP
|
||||
The configuration commands are:
|
||||
.PP
|
||||
|
||||
|
||||
\fBremove\fR
|
||||
removes the named statistics name and data\&.
|
||||
.PP
|
||||
|
||||
|
||||
\fBreset\fR
|
||||
will reset all statistics data to default values except for constant names\&. This may re\-add previously removed statistics names\&.
|
||||
.PP
|
||||
|
||||
\fBset\fR
|
||||
.PP
|
||||
|
||||
\fBshow\fR
|
||||
will send the statistics data in JSON format\&. By default, it outputs all the statistics data it has collected\&. An optional item name may be specified to receive individual output\&.
|
||||
.PP
|
||||
|
||||
\fBshutdown\fR
|
||||
will shutdown the
|
||||
\fBb10\-stats\fR
|
||||
process\&. (Note that the
|
||||
\fBbind10\fR
|
||||
parent may restart it\&.)
|
||||
.PP
|
||||
|
||||
\fBstatus\fR
|
||||
simply indicates that the daemon is running\&.
|
||||
.SH "STATISTICS DATA"
|
||||
.PP
|
||||
The
|
||||
\fBb10\-stats\fR
|
||||
daemon contains these statistics:
|
||||
.PP
|
||||
report_time
|
||||
.RS 4
|
||||
The latest report date and time in ISO 8601 format\&.
|
||||
.RE
|
||||
.PP
|
||||
stats\&.boot_time
|
||||
.RS 4
|
||||
The date and time when this daemon was started in ISO 8601 format\&. This is a constant which can\'t be reset except by restarting
|
||||
\fBb10\-stats\fR\&.
|
||||
.RE
|
||||
.PP
|
||||
stats\&.last_update_time
|
||||
.RS 4
|
||||
The date and time (in ISO 8601 format) when this daemon last received data from another component\&.
|
||||
.RE
|
||||
.PP
|
||||
stats\&.lname
|
||||
.RS 4
|
||||
This is the name used for the
|
||||
\fBb10\-msgq\fR
|
||||
command\-control channel\&. (This is a constant which can\'t be reset except by restarting
|
||||
\fBb10\-stats\fR\&.)
|
||||
.RE
|
||||
.PP
|
||||
stats\&.start_time
|
||||
.RS 4
|
||||
This is the date and time (in ISO 8601 format) when this daemon started collecting data\&.
|
||||
.RE
|
||||
.PP
|
||||
stats\&.timestamp
|
||||
.RS 4
|
||||
The current date and time represented in seconds since UNIX epoch (1970\-01\-01T0 0:00:00Z) with precision (delimited with a period) up to one hundred thousandth of second\&.
|
||||
.RE
|
||||
.PP
|
||||
See other manual pages for explanations for their statistics that are kept track by
|
||||
\fBb10\-stats\fR\&.
|
||||
.SH "FILES"
|
||||
.PP
|
||||
/usr/local/share/bind10\-devel/stats\&.spec
|
||||
@@ -82,7 +151,7 @@ BIND 10 Guide\&.
|
||||
.PP
|
||||
The
|
||||
\fBb10\-stats\fR
|
||||
daemon was initially designed and implemented by Naoki Kambe of JPRS in Oct 2010\&.
|
||||
daemon was initially designed and implemented by Naoki Kambe of JPRS in October 2010\&.
|
||||
.SH "COPYRIGHT"
|
||||
.br
|
||||
Copyright \(co 2010 Internet Systems Consortium, Inc. ("ISC")
|
||||
|
||||
@@ -71,6 +71,9 @@ is a list of zones known to the
|
||||
daemon\&. The list items are:
|
||||
\fIname\fR
|
||||
(the zone name),
|
||||
\fIclass\fR
|
||||
(defaults to
|
||||
\(lqIN\(rq),
|
||||
\fImaster_addr\fR
|
||||
(the zone master to transfer from),
|
||||
\fImaster_port\fR
|
||||
@@ -125,7 +128,7 @@ to define the class (defaults to
|
||||
\fImaster\fR
|
||||
to define the IP address of the authoritative server to transfer from, and
|
||||
\fIport\fR
|
||||
to define the port number on the authoritative server (defaults to 53)\&. If the address or port is not specified, it will use the values previously defined in the
|
||||
to define the port number on the authoritative server (defaults to 53)\&. If the address or port is not specified, it will use the value previously defined in the
|
||||
\fIzones\fR
|
||||
configuration\&.
|
||||
.PP
|
||||
|
||||
Reference in New Issue
Block a user