BIND 10 master, updated. 7c3157f20008eead9731a9193b39e5775d3e44d5 [master]Merge branch 'master' of ssh://git.bind10.isc.org//var/bind10/git/bind10
BIND 10 source code commits
bind10-changes at lists.isc.org
Tue Jan 17 18:02:58 UTC 2012
The branch, master has been updated
via 7c3157f20008eead9731a9193b39e5775d3e44d5 (commit)
via 90b9fb73e2b1ce8f0b4e0b8597e4705e6f540920 (commit)
from 5589ea8da0a906e66eed1d85b26da4e75e3902a2 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 7c3157f20008eead9731a9193b39e5775d3e44d5
Merge: 90b9fb73e2b1ce8f0b4e0b8597e4705e6f540920 5589ea8da0a906e66eed1d85b26da4e75e3902a2
Author: Jeremy C. Reed <jreed at ISC.org>
Date: Tue Jan 17 12:02:50 2012 -0600
[master]Merge branch 'master' of ssh://git.bind10.isc.org//var/bind10/git/bind10
commit 90b9fb73e2b1ce8f0b4e0b8597e4705e6f540920
Author: Jeremy C. Reed <jreed at ISC.org>
Date: Tue Jan 17 12:02:17 2012 -0600
[master] regenerate log messages and guide documents
-----------------------------------------------------------------------
Summary of changes:
doc/guide/bind10-guide.html | 251 +++++++--------
doc/guide/bind10-guide.txt | 695 ++++++++++++++++++++++++++++++----------
doc/guide/bind10-messages.html | 355 ++++++++++++++++++---
doc/guide/bind10-messages.xml | 621 ++++++++++++++++++++++++++++++++----
4 files changed, 1517 insertions(+), 405 deletions(-)
-----------------------------------------------------------------------
diff --git a/doc/guide/bind10-guide.html b/doc/guide/bind10-guide.html
index f6206a5..ef47c65 100644
--- a/doc/guide/bind10-guide.html
+++ b/doc/guide/bind10-guide.html
@@ -1,4 +1,4 @@
-<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 framework that features Domain Name System (DNS) suite and Dynamic Host Configuration Protocol (DHCP) servers managed by Internet Systems Consortium (ISC). It includes DNS libraries, modular components for controlling authoritative and recursive DNS servers, and experimental DHCPv4 and DHCPv6 servers. This is the reference guide for BIND 10 version 20111129. The most up-to-date version of this document (in PDF, HTML, and plain text formats), 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="id2479
03"></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
+<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 framework that features Domain Name System (DNS) suite and Dynamic Host Configuration Protocol (DHCP) servers managed by Internet Systems Consortium (ISC). It includes DNS libraries, modular components for controlling authoritative and recursive DNS servers, and experimental DHCPv4 and DHCPv6 servers. This is the reference guide for BIND 10 version 20111129. The most up-to-date version of this document (in PDF, HTML, and plain text formats), 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="id1168
229451102"></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
20111129.</p></div><div><p class="copyright">Copyright © 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 framework that features Domain Name System
(DNS) suite and Dynamic Host Configuration Protocol (DHCP)
servers managed by Internet Systems Consortium (ISC). It
@@ -10,42 +10,52 @@
The most up-to-date version of this document (in PDF, HTML,
and plain text formats), 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="#id457902">1.1. Supported Platforms</a></span></dt><dt><span class="section"><a href="#id457914">1.2. Required Software</a></span></dt><dt><span class="section"><a href="#starting_stopping">1.3. Starting and Stopping the Server</a></span></dt><dt><span class="section"><a href="#managing_once_running">1.4. 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="#id458364">2.1. Building Requirements</a></span></dt><dt><span class="section"><a href="#quickstart">2.2. Quick start</a></span></dt><dt><span class="section"><a href="#install">2.3. Installation from source</a></span></dt><dd><dl><dt><span class="section"><a href="#id458582">2.3.1. Download Tar File</a></
span></dt><dt><span class="section"><a href="#id458605">2.3.2. Retrieve from Git</a></span></dt><dt><span class="section"><a href="#id458679">2.3.3. Configure before the build</a></span></dt><dt><span class="section"><a href="#id458789">2.3.4. Build</a></span></dt><dt><span class="section"><a href="#id458806">2.3.5. Install</a></span></dt><dt><span class="section"><a href="#id458832">2.3.6. 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">3.1. Starting BIND 10</a></span></dt><dt><span class="section"><a href="#bind10.config">3.2. Configuration of started processes</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">6.1. 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="#id459869">8.1. Server Configurations</a></span></dt><dt><span class="section"><a href="#id459942">8.2. Data Source Backends</a></span></dt><dt><span class="section"><a href="#id459978">8.3. Loading Master Zones Files</a></span></dt></dl></dd><dt><span class="chapter"><a href="#xfrin">9. Incoming Zone Transfers</a></span></dt><dd><dl><dt><span class="section"><a href="#id460133">9.1. Configuration for Incoming Zone Transfers</a></span></dt><dt><span class="section"><a href="#id460177">9.2. Enabling IXFR</a></span></dt><dt><span class="section"><a href="#zonemgr">9.3. Secondary Man
ager</a></span></dt><dt><span class="section"><a href="#id460320">9.4. Trigger an Incoming Zone Transfer Manually</a></span></dt></dl></dd><dt><span class="chapter"><a href="#xfrout">10. Outbound Zone Transfers</a></span></dt><dt><span class="chapter"><a href="#resolverserver">11. Recursive Name Server</a></span></dt><dd><dl><dt><span class="section"><a href="#id460633">11.1. Access Control</a></span></dt><dt><span class="section"><a href="#id460772">11.2. Forwarding</a></span></dt></dl></dd><dt><span class="chapter"><a href="#dhcp4">12. DHCPv4 Server</a></span></dt><dd><dl><dt><span class="section"><a href="#dhcp4-usage">12.1. DHCPv4 Server Usage</a></span></dt><dt><span class="section"><a href="#dhcp4-config">12.2. DHCPv4 Server Configuration</a></span></dt><dt><span class="section"><a href="#dhcp4-std">12.3. Supported standards</a></span></dt><dt><span class="section"><a href="#dhcp4-limit">12.4. DHCPv4 Server Limitations</a></span></dt></dl></dd><dt><span class="chapter"
><a href="#dhcp6">13. DHCPv6 Server</a></span></dt><dd><dl><dt><span class="section"><a href="#dhcp6-usage">13.1. DHCPv6 Server Usage</a></span></dt><dt><span class="section"><a href="#dhcp6-config">13.2. DHCPv6 Server Configuration</a></span></dt><dt><span class="section"><a href="#dhcp6-std">13.3. Supported DHCPv6 Standards</a></span></dt><dt><span class="section"><a href="#dhcp6-limit">13.4. DHCPv6 Server Limitations</a></span></dt></dl></dd><dt><span class="chapter"><a href="#libdhcp">14. libdhcp++ library</a></span></dt><dd><dl><dt><span class="section"><a href="#iface-detect">14.1. Interface detection</a></span></dt><dt><span class="section"><a href="#packet-handling">14.2. DHCPv4/DHCPv6 packet handling</a></span></dt></dl></dd><dt><span class="chapter"><a href="#statistics">15. Statistics</a></span></dt><dt><span class="chapter"><a href="#logging">16. Logging</a></span></dt><dd><dl><dt><span class="section"><a href="#id461660">16.1. Logging configuration</a></span></d
t><dd><dl><dt><span class="section"><a href="#id461675">16.1.1. Loggers</a></span></dt><dt><span class="section"><a href="#id461978">16.1.2. Output Options</a></span></dt><dt><span class="section"><a href="#id462172">16.1.3. Example session</a></span></dt></dl></dd><dt><span class="section"><a href="#id462428">16.2. Logging Message Format</a></span></dt></dl></dd><dt><span class="chapter"><a href="#id462551">17. Acknowledgements</a></span></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>3.1. <a href="#id459146"></a></dt></dl></div><div class="chapter" title="Chapter 1. Introduction"><div class="titlepage"><div><div><h2 class="title"><a name="intro"></a>Chapter 1. Introduction</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id457902">1.1. Supported Platforms</a></span></dt><dt><span class="section"><a href="#id457914">1.2. Required Software</a></span></dt><dt><span class="section"><a
href="#starting_stopping">1.3. Starting and Stopping the Server</a></span></dt><dt><span class="section"><a href="#managing_once_running">1.4. Managing BIND 10</a></span></dt></dl></div><p>
+ </p></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="preface"><a href="#id1168229451188">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="#acknowledgements">1. Acknowledgements</a></span></dt></dl></dd><dt><span class="chapter"><a href="#intro">1. Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="#id1168229451269">1.1. Supported Platforms</a></span></dt><dt><span class="section"><a href="#required-software">1.2. Required Software</a></span></dt><dt><span class="section"><a href="#starting_stopping">1.3. Starting and Stopping the Server</a></span></dt><dt><span class="section"><a href="#managing_once_running">1.4. 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="#build-requirements">2.1. Building Requirements</a></span></dt><dt><span class="section"><a href="#quickstar
t">2.2. Quick start</a></span></dt><dt><span class="section"><a href="#install">2.3. Installation from source</a></span></dt><dd><dl><dt><span class="section"><a href="#id1168229436789">2.3.1. Download Tar File</a></span></dt><dt><span class="section"><a href="#id1168229436809">2.3.2. Retrieve from Git</a></span></dt><dt><span class="section"><a href="#id1168229436870">2.3.3. Configure before the build</a></span></dt><dt><span class="section"><a href="#id1168229436967">2.3.4. Build</a></span></dt><dt><span class="section"><a href="#id1168229436982">2.3.5. Install</a></span></dt><dt><span class="section"><a href="#id1168229437006">2.3.6. 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">3.1. Starting BIND 10</a></span></dt><dt><span class="section"><a href="#bind10.config">3.2. Configurati
on of started processes</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">6.1. 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="#id1168229437939">8.1. Server Configurations</a></span></dt><dt><span class="section"><a href="#id1168229438004">8.2. Data Source Backends</a></span></dt><dt><span class="section"><a href="#id1168229438035">8.3. Loading Master Zones Files</a></span></dt></dl></dd><dt><span class="chapter"><a href="#xfrin">9. Incoming Zone Transfers</a
></span></dt><dd><dl><dt><span class="section"><a href="#id1168229438166">9.1. Configuration for Incoming Zone Transfers</a></span></dt><dt><span class="section"><a href="#id1168229438203">9.2. Enabling IXFR</a></span></dt><dt><span class="section"><a href="#zonemgr">9.3. Secondary Manager</a></span></dt><dt><span class="section"><a href="#id1168229438317">9.4. Trigger an Incoming Zone Transfer Manually</a></span></dt></dl></dd><dt><span class="chapter"><a href="#xfrout">10. Outbound Zone Transfers</a></span></dt><dt><span class="chapter"><a href="#resolverserver">11. Recursive Name Server</a></span></dt><dd><dl><dt><span class="section"><a href="#id1168229438745">11.1. Access Control</a></span></dt><dt><span class="section"><a href="#id1168229438860">11.2. Forwarding</a></span></dt></dl></dd><dt><span class="chapter"><a href="#dhcp4">12. DHCPv4 Server</a></span></dt><dd><dl><dt><span class="section"><a href="#dhcp4-usage">12.1. DHCPv4 Server Usage</a></span></dt><dt><span c
lass="section"><a href="#dhcp4-config">12.2. DHCPv4 Server Configuration</a></span></dt><dt><span class="section"><a href="#dhcp4-std">12.3. Supported standards</a></span></dt><dt><span class="section"><a href="#dhcp4-limit">12.4. DHCPv4 Server Limitations</a></span></dt></dl></dd><dt><span class="chapter"><a href="#dhcp6">13. DHCPv6 Server</a></span></dt><dd><dl><dt><span class="section"><a href="#dhcp6-usage">13.1. DHCPv6 Server Usage</a></span></dt><dt><span class="section"><a href="#dhcp6-config">13.2. DHCPv6 Server Configuration</a></span></dt><dt><span class="section"><a href="#dhcp6-std">13.3. Supported DHCPv6 Standards</a></span></dt><dt><span class="section"><a href="#dhcp6-limit">13.4. DHCPv6 Server Limitations</a></span></dt></dl></dd><dt><span class="chapter"><a href="#libdhcp">14. libdhcp++ library</a></span></dt><dd><dl><dt><span class="section"><a href="#iface-detect">14.1. Interface detection</a></span></dt><dt><span class="section"><a href="#packet-handling"
>14.2. DHCPv4/DHCPv6 packet handling</a></span></dt></dl></dd><dt><span class="chapter"><a href="#statistics">15. Statistics</a></span></dt><dt><span class="chapter"><a href="#logging">16. Logging</a></span></dt><dd><dl><dt><span class="section"><a href="#id1168229439976">16.1. Logging configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#id1168229439987">16.1.1. Loggers</a></span></dt><dt><span class="section"><a href="#id1168229440229">16.1.2. Output Options</a></span></dt><dt><span class="section"><a href="#id1168229440471">16.1.3. Example session</a></span></dt></dl></dd><dt><span class="section"><a href="#id1168229440680">16.2. Logging Message Format</a></span></dt></dl></dd></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>3.1. <a href="#id1168229437268"></a></dt></dl></div><div class="preface" title="Preface"><div class="titlepage"><div><div><h2 class="title"><a name="id1168229451188"></a>Preface</h2></div></div></div><div c
lass="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#acknowledgements">1. Acknowledgements</a></span></dt></dl></div><div class="section" title="1. Acknowledgements"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="acknowledgements"></a>1. Acknowledgements</h2></div></div></div><p>ISC would like to acknowledge generous support for
+ BIND 10 development of DHCPv4 and DHCPv6 components provided
+ by <a class="ulink" href="http://www.comcast.com/" target="_top">Comcast</a>.</p></div></div><div class="chapter" title="Chapter 1. Introduction"><div class="titlepage"><div><div><h2 class="title"><a name="intro"></a>Chapter 1. Introduction</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id1168229451269">1.1. Supported Platforms</a></span></dt><dt><span class="section"><a href="#required-software">1.2. Required Software</a></span></dt><dt><span class="section"><a href="#starting_stopping">1.3. Starting and Stopping the Server</a></span></dt><dt><span class="section"><a href="#managing_once_running">1.4. 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 20111129.
- </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="1.1. Supported Platforms"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id457902"></a>1.1. 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.
+ BIND 10 provides a EDNS0- and DNSSEC-capable authoritative
+ DNS server and a caching recursive name server which also
+ provides forwarding.
+ </p><p>
+ This guide covers the experimental prototype of
+ BIND 10 version 20111129.
+ </p><div class="section" title="1.1. Supported Platforms"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168229451269"></a>1.1. Supported Platforms</h2></div></div></div><p>
+ BIND 10 builds have been tested on Debian GNU/Linux 5 and unstable,
+ Ubuntu 9.10, NetBSD 5, Solaris 10, FreeBSD 7 and 8, CentOS
+ Linux 5.3, and MacOS 10.6.
It has been tested on Sparc, i386, and amd64 hardware
platforms.
It is planned for BIND 10 to build, install and run on
Windows and standard Unix-type platforms.
- </p></div><div class="section" title="1.2. Required Software"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id457914"></a>1.2. 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></div><div class="section" title="1.2. Required Software"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="required-software"></a>1.2. Required Software</h2></div></div></div><p>
+ BIND 10 requires at least Python 3.1
+ (<a class="ulink" href="http://www.python.org/" target="_top">http://www.python.org/</a>).
+ It has also been tested with Python 3.2.
+ </p><p>
+ BIND 10 uses the Botan crypto library for C++
+ (<a class="ulink" href="http://botan.randombit.net/" target="_top">http://botan.randombit.net/</a>).
+ It requires at least Botan version 1.8.
</p><p>
- BIND 10 uses the Botan crypto library for C++. It requires
- at least Botan version 1.8.
+ BIND 10 uses the log4cplus C++ logging library
+ (<a class="ulink" href="http://log4cplus.sourceforge.net/" target="_top">http://log4cplus.sourceforge.net/</a>).
+ It requires at least log4cplus version 1.0.3.
</p><p>
- BIND 10 uses the log4cplus C++ logging library. It requires
- at least log4cplus version 1.0.3.
+ The authoritative DNS server uses SQLite3
+ (<a class="ulink" href="http://www.sqlite.org/" target="_top">http://www.sqlite.org/</a>).
+
+ It needs at least SQLite version 3.3.9.
</p><p>
- The authoritative server requires SQLite 3.3.9 or newer.
The <span class="command"><strong>b10-xfrin</strong></span>, <span class="command"><strong>b10-xfrout</strong></span>,
- and <span class="command"><strong>b10-zonemgr</strong></span> modules require the
- libpython3 library and the Python _sqlite3.so module.
+ and <span class="command"><strong>b10-zonemgr</strong></span> components require the
+ libpython3 library and the Python _sqlite3.so module
+ (which is included with Python).
+ The Python module needs to be built for the corresponding Python 3.
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
Some operating systems do not provide these dependencies
in their default installation nor standard packages
@@ -142,7 +152,7 @@
and, of course, DNS. These include detailed developer
documentation and code examples.
- </p></div><div class="chapter" title="Chapter 2. Installation"><div class="titlepage"><div><div><h2 class="title"><a name="installation"></a>Chapter 2. Installation</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id458364">2.1. Building Requirements</a></span></dt><dt><span class="section"><a href="#quickstart">2.2. Quick start</a></span></dt><dt><span class="section"><a href="#install">2.3. Installation from source</a></span></dt><dd><dl><dt><span class="section"><a href="#id458582">2.3.1. Download Tar File</a></span></dt><dt><span class="section"><a href="#id458605">2.3.2. Retrieve from Git</a></span></dt><dt><span class="section"><a href="#id458679">2.3.3. Configure before the build</a></span></dt><dt><span class="section"><a href="#id458789">2.3.4. Build</a></span></dt><dt><span class="section"><a href="#id458806">2.3.5. Install</a></span></dt><dt><span class="section"><a href="#id458832">2.3.6. Install Hi
erarchy</a></span></dt></dl></dd></dl></div><div class="section" title="2.1. Building Requirements"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id458364"></a>2.1. Building Requirements</h2></div></div></div><p>
+ </p></div><div class="chapter" title="Chapter 2. Installation"><div class="titlepage"><div><div><h2 class="title"><a name="installation"></a>Chapter 2. Installation</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#build-requirements">2.1. Building Requirements</a></span></dt><dt><span class="section"><a href="#quickstart">2.2. Quick start</a></span></dt><dt><span class="section"><a href="#install">2.3. Installation from source</a></span></dt><dd><dl><dt><span class="section"><a href="#id1168229436789">2.3.1. Download Tar File</a></span></dt><dt><span class="section"><a href="#id1168229436809">2.3.2. Retrieve from Git</a></span></dt><dt><span class="section"><a href="#id1168229436870">2.3.3. Configure before the build</a></span></dt><dt><span class="section"><a href="#id1168229436967">2.3.4. Build</a></span></dt><dt><span class="section"><a href="#id1168229436982">2.3.5. Install</a></span></dt><dt><span class="s
ection"><a href="#id1168229437006">2.3.6. Install Hierarchy</a></span></dt></dl></dd></dl></div><div class="section" title="2.1. Building Requirements"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="build-requirements"></a>2.1. 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>
@@ -152,7 +162,9 @@
libraries, to build BIND 10 from source code.
</p></div><p>
Building from source code requires the Boost
- build-time headers. At least Boost version 1.35 is required.
+ build-time headers
+ (<a class="ulink" href="http://www.boost.org/" target="_top">http://www.boost.org/</a>).
+ At least Boost version 1.35 is required.
</p><p>
@@ -160,17 +172,13 @@
1.8) and the log4cplus (at least version 1.0.3)
development include headers.
</p><p>
-
- The Python Library and Python _sqlite3 module are required to
- enable the Xfrout and Xfrin support.
- </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- The Python related libraries and modules need to be built
- for Python 3.1.
- </p></div><p>
Building BIND 10 also requires a C++ compiler and
standard development headers, make, and pkg-config.
BIND 10 builds have been tested with GCC g++ 3.4.3, 4.1.2,
4.1.3, 4.2.1, 4.3.2, and 4.4.1; Clang++ 2.8; and Sun C++ 5.10.
+ </p><p>
+ Visit the wiki at <a class="ulink" href="http://bind10.isc.org/wiki/SystemSpecificNotes" target="_top">http://bind10.isc.org/wiki/SystemSpecificNotes</a>
+ for system-specific installation tips.
</p></div><div class="section" title="2.2. Quick start"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="quickstart"></a>2.2. Quick start</h2></div></div></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
This quickly covers the standard steps for installing
and deploying BIND 10 as an authoritative name server using
@@ -179,7 +187,7 @@
</p></div><p>
To quickly get started with BIND 10, follow these steps.
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
- Install required build dependencies.
+ Install required run-time and build dependencies.
</li><li class="listitem">
Download the BIND 10 source tar file from
<a class="ulink" href="ftp://ftp.isc.org/isc/bind10/" target="_top">ftp://ftp.isc.org/isc/bind10/</a>.
@@ -206,14 +214,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="2.3.1. Download Tar File"><div class="titlepage"><div><div><h3 class="title"><a name="id458582"></a>2.3.1. Download Tar File</h3></div></div></div><p>
+ </p><div class="section" title="2.3.1. Download Tar File"><div class="titlepage"><div><div><h3 class="title"><a name="id1168229436789"></a>2.3.1. 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="2.3.2. Retrieve from Git"><div class="titlepage"><div><div><h3 class="title"><a name="id458605"></a>2.3.2. Retrieve from Git</h3></div></div></div><p>
+ </p></div><div class="section" title="2.3.2. Retrieve from Git"><div class="titlepage"><div><div><h3 class="title"><a name="id1168229436809"></a>2.3.2. 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.
@@ -247,7 +255,7 @@
<span class="command"><strong>autoheader</strong></span>,
<span class="command"><strong>automake</strong></span>,
and related commands.
- </p></div><div class="section" title="2.3.3. Configure before the build"><div class="titlepage"><div><div><h3 class="title"><a name="id458679"></a>2.3.3. Configure before the build</h3></div></div></div><p>
+ </p></div><div class="section" title="2.3.3. Configure before the build"><div class="titlepage"><div><div><h3 class="title"><a name="id1168229436870"></a>2.3.3. 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:
@@ -278,16 +286,16 @@
</p><p>
If the configure fails, it may be due to missing or old
dependencies.
- </p></div><div class="section" title="2.3.4. Build"><div class="titlepage"><div><div><h3 class="title"><a name="id458789"></a>2.3.4. Build</h3></div></div></div><p>
+ </p></div><div class="section" title="2.3.4. Build"><div class="titlepage"><div><div><h3 class="title"><a name="id1168229436967"></a>2.3.4. 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="2.3.5. Install"><div class="titlepage"><div><div><h3 class="title"><a name="id458806"></a>2.3.5. Install</h3></div></div></div><p>
+ </p></div><div class="section" title="2.3.5. Install"><div class="titlepage"><div><div><h3 class="title"><a name="id1168229436982"></a>2.3.5. 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="2.3.6. Install Hierarchy"><div class="titlepage"><div><div><h3 class="title"><a name="id458832"></a>2.3.6. 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="2.3.6. Install Hierarchy"><div class="titlepage"><div><div><h3 class="title"><a name="id1168229437006"></a>2.3.6. 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> —
@@ -387,7 +395,7 @@
during startup or shutdown. Unless specified, the component is started
in usual way. This is the list of components that need to be started
in a special way, with the value of special used for them:
- </p><div class="table"><a name="id459146"></a><p class="title"><b>Table 3.1. </b></p><div class="table-contents"><table border="1"><colgroup><col align="left"><col align="left"><col align="left"></colgroup><thead><tr><th align="left">Component</th><th align="left">Special</th><th align="left">Description</th></tr></thead><tbody><tr><td align="left">b10-auth</td><td align="left">auth</td><td align="left">Authoritative server</td></tr><tr><td align="left">b10-resolver</td><td align="left">resolver</td><td align="left">The resolver</td></tr><tr><td align="left">b10-cmdctl</td><td align="left">cmdctl</td><td align="left">The command control (remote control interface)</td></tr><tr><td align="left">setuid</td><td align="left">setuid</td><td align="left">Virtual component, see below</td></tr></tbody></table></div></div><p><br class="table-break">
+ </p><div class="table"><a name="id1168229437268"></a><p class="title"><b>Table 3.1. </b></p><div class="table-contents"><table border="1"><colgroup><col align="left"><col align="left"><col align="left"></colgroup><thead><tr><th align="left">Component</th><th align="left">Special</th><th align="left">Description</th></tr></thead><tbody><tr><td align="left">b10-auth</td><td align="left">auth</td><td align="left">Authoritative server</td></tr><tr><td align="left">b10-resolver</td><td align="left">resolver</td><td align="left">The resolver</td></tr><tr><td align="left">b10-cmdctl</td><td align="left">cmdctl</td><td align="left">The command control (remote control interface)</td></tr></tbody></table></div></div><p><br class="table-break">
</p><p>
The kind specifies how a failure of the component should
be handled. If it is set to <span class="quote">“<span class="quote">dispensable</span>”</span>
@@ -407,6 +415,7 @@
The priority defines order in which the components should start.
The ones with higher number are started sooner than the ones with
lower ones. If you don't set it, 0 (zero) is used as the priority.
+ Usually, leaving it at the default is enough.
</p><p>
There are other parameters we didn't use in our example.
One of them is <span class="quote">“<span class="quote">address</span>”</span>. It is the address
@@ -442,21 +451,7 @@
</p><p>
In short, you should think twice before disabling something here.
- </p></div><p>
- Now, to the mysterious setuid virtual component. If you
- use the <span class="command"><strong>-u</strong></span> option to start the
- <span class="command"><strong>bind10</strong></span> as root, but change the user
- later, we need to start the <span class="command"><strong>b10-auth</strong></span> or
- <span class="command"><strong>b10-resolver</strong></span> as root (until the socket
- creator is finished). So we need to specify
- the time when the switch from root do the given user happens
- and that's what the setuid component is for. The switch is
- done at the time the setuid component would be started, if
- it was a process. The default configuration contains the
- setuid component with priority 5, <span class="command"><strong>b10-auth</strong></span>
- has 10 to be started before the switch and everything else
- is without priority, so it is started after the switch.
- </p></div></div><div class="chapter" title="Chapter 4. Command channel"><div class="titlepage"><div><div><h2 class="title"><a name="msgq"></a>Chapter 4. Command channel</h2></div></div></div><p>
+ </p></div></div></div><div class="chapter" title="Chapter 4. Command channel"><div class="titlepage"><div><div><h2 class="title"><a name="msgq"></a>Chapter 4. Command channel</h2></div></div></div><p>
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
@@ -612,12 +607,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 8. Authoritative Server"><div class="titlepage"><div><div><h2 class="title"><a name="authserver"></a>Chapter 8. Authoritative Server</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id459869">8.1. Server Configurations</a></span></dt><dt><span class="section"><a href="#id459942">8.2. Data Source Backends</a></span></dt><dt><span class="section"><a href="#id459978">8.3. Loading Master Zones Files</a></span></dt></dl></div><p>
+ </p></div><div class="chapter" title="Chapter 8. Authoritative Server"><div class="titlepage"><div><div><h2 class="title"><a name="authserver"></a>Chapter 8. Authoritative Server</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id1168229437939">8.1. Server Configurations</a></span></dt><dt><span class="section"><a href="#id1168229438004">8.2. Data Source Backends</a></span></dt><dt><span class="section"><a href="#id1168229438035">8.3. 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="8.1. Server Configurations"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id459869"></a>8.1. Server Configurations</h2></div></div></div><p>
+ </p><div class="section" title="8.1. Server Configurations"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168229437939"></a>8.1. 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>.
@@ -637,7 +632,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="8.2. Data Source Backends"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id459942"></a>8.2. 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="8.2. Data Source Backends"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168229438004"></a>8.2. 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.
@@ -651,7 +646,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="8.3. Loading Master Zones Files"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id459978"></a>8.3. Loading Master Zones Files</h2></div></div></div><p>
+ </p></div><div class="section" title="8.3. Loading Master Zones Files"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168229438035"></a>8.3. 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.
@@ -680,7 +675,7 @@ This may be a temporary setting until then.
If you reload a zone already existing in the database,
all records from that prior zone disappear and a whole new set
appears.
- </p></div></div><div class="chapter" title="Chapter 9. Incoming Zone Transfers"><div class="titlepage"><div><div><h2 class="title"><a name="xfrin"></a>Chapter 9. Incoming Zone Transfers</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id460133">9.1. Configuration for Incoming Zone Transfers</a></span></dt><dt><span class="section"><a href="#id460177">9.2. Enabling IXFR</a></span></dt><dt><span class="section"><a href="#zonemgr">9.3. Secondary Manager</a></span></dt><dt><span class="section"><a href="#id460320">9.4. Trigger an Incoming Zone Transfer Manually</a></span></dt></dl></div><p>
+ </p></div></div><div class="chapter" title="Chapter 9. Incoming Zone Transfers"><div class="titlepage"><div><div><h2 class="title"><a name="xfrin"></a>Chapter 9. Incoming Zone Transfers</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id1168229438166">9.1. Configuration for Incoming Zone Transfers</a></span></dt><dt><span class="section"><a href="#id1168229438203">9.2. Enabling IXFR</a></span></dt><dt><span class="section"><a href="#zonemgr">9.3. Secondary Manager</a></span></dt><dt><span class="section"><a href="#id1168229438317">9.4. Trigger an Incoming Zone Transfer Manually</a></span></dt></dl></div><p>
Incoming zones are transferred using the <span class="command"><strong>b10-xfrin</strong></span>
process which is started by <span class="command"><strong>bind10</strong></span>.
When received, the zone is stored in the corresponding BIND 10
@@ -698,7 +693,7 @@ This may be a temporary setting until then.
In the current development release of BIND 10, incoming zone
transfers are only available for SQLite3-based data sources,
that is, they don't work for an in-memory data source.
- </p></div><div class="section" title="9.1. Configuration for Incoming Zone Transfers"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id460133"></a>9.1. Configuration for Incoming Zone Transfers</h2></div></div></div><p>
+ </p></div><div class="section" title="9.1. Configuration for Incoming Zone Transfers"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168229438166"></a>9.1. Configuration for Incoming Zone Transfers</h2></div></div></div><p>
In practice, you need to specify a list of secondary zones to
enable incoming zone transfers for these zones (you can still
trigger a zone transfer manually, without a prior configuration
@@ -714,7 +709,7 @@ This may be a temporary setting until then.
> <strong class="userinput"><code>config commit</code></strong></pre><p>
(We assume there has been no zone configuration before).
- </p></div><div class="section" title="9.2. Enabling IXFR"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id460177"></a>9.2. Enabling IXFR</h2></div></div></div><p>
+ </p></div><div class="section" title="9.2. Enabling IXFR"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168229438203"></a>9.2. Enabling IXFR</h2></div></div></div><p>
As noted above, <span class="command"><strong>b10-xfrin</strong></span> uses AXFR for
zone transfers by default. To enable IXFR for zone transfers
for a particular zone, set the <strong class="userinput"><code>use_ixfr</code></strong>
@@ -766,7 +761,7 @@ This may be a temporary setting until then.
(i.e. no SOA record for it), <span class="command"><strong>b10-zonemgr</strong></span>
will automatically tell <span class="command"><strong>b10-xfrin</strong></span>
to transfer the zone in.
- </p></div><div class="section" title="9.4. Trigger an Incoming Zone Transfer Manually"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id460320"></a>9.4. Trigger an Incoming Zone Transfer Manually</h2></div></div></div><p>
+ </p></div><div class="section" title="9.4. Trigger an Incoming Zone Transfer Manually"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168229438317"></a>9.4. Trigger an Incoming Zone Transfer Manually</h2></div></div></div><p>
To manually trigger a zone transfer to retrieve a remote zone,
you may use the <span class="command"><strong>bindctl</strong></span> utility.
For example, at the <span class="command"><strong>bindctl</strong></span> prompt run:
@@ -823,7 +818,7 @@ Xfrout/transfer_acl[0] {"action": "ACCEPT"} any (default)</pre><p>
use the system wide TSIG configuration.
The way to specify zone specific configuration (ACLs, etc) is
likely to be changed, too.
- </p></div></div><div class="chapter" title="Chapter 11. Recursive Name Server"><div class="titlepage"><div><div><h2 class="title"><a name="resolverserver"></a>Chapter 11. Recursive Name Server</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id460633">11.1. Access Control</a></span></dt><dt><span class="section"><a href="#id460772">11.2. Forwarding</a></span></dt></dl></div><p>
+ </p></div></div><div class="chapter" title="Chapter 11. Recursive Name Server"><div class="titlepage"><div><div><h2 class="title"><a name="resolverserver"></a>Chapter 11. Recursive Name Server</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id1168229438745">11.1. Access Control</a></span></dt><dt><span class="section"><a href="#id1168229438860">11.2. 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>.
@@ -862,7 +857,7 @@ Xfrout/transfer_acl[0] {"action": "ACCEPT"} any (default)</pre><p>
</pre><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="11.1. Access Control"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id460633"></a>11.1. Access Control</h2></div></div></div><p>
+ Resolver/listen_on</code></strong></span>”</span> if needed.)</p><div class="section" title="11.1. Access Control"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168229438745"></a>11.1. 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
@@ -895,7 +890,7 @@ Xfrout/transfer_acl[0] {"action": "ACCEPT"} any (default)</pre><p>
</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="11.2. Forwarding"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id460772"></a>11.2. Forwarding</h2></div></div></div><p>
+ syntax may be changed.</p></div></div><div class="section" title="11.2. Forwarding"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168229438860"></a>11.2. Forwarding</h2></div></div></div><p>
To enable forwarding, the upstream address and port must be
configured to forward queries to, such as:
@@ -924,29 +919,29 @@ Xfrout/transfer_acl[0] {"action": "ACCEPT"} any (default)</pre><p>
clients. Even though principles of both DHCPv4 and DHCPv6 are
somewhat similar, these are two radically different
protocols. BIND10 offers server implementations for both DHCPv4
- and DHCPv6. This chapter is about DHCP for IPv4. For description of
- DHCPv6 server, see <a class="xref" href="#dhcp6" title="Chapter 13. DHCPv6 Server">Chapter 13, <i>DHCPv6 Server</i></a>.</p><p>DHCPv6 server component is currently under intense
+ and DHCPv6. This chapter is about DHCP for IPv4. For a description
+ of the DHCPv6 server, see <a class="xref" href="#dhcp6" title="Chapter 13. DHCPv6 Server">Chapter 13, <i>DHCPv6 Server</i></a>.</p><p>The DHCPv4 server component is currently under intense
development. You may want to check out <a class="ulink" href="http://bind10.isc.org/wiki/Kea" target="_top">BIND10 DHCP (Kea) wiki</a>
and recent posts on <a class="ulink" href="https://lists.isc.org/mailman/listinfo/bind10-dev" target="_top">BIND10
- developers mailing list</a>.</p><p>DHCPv4 and DHCPv6 components in BIND10 architecture are
+ developers mailing list</a>.</p><p>The DHCPv4 and DHCPv6 components in BIND10 architecture are
internally code named <span class="quote">“<span class="quote">Kea</span>”</span>.</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
As of December 2011, both DHCPv4 and DHCPv6 components are
skeleton servers. That means that while they are capable of
performing DHCP configuration, they are not fully functional
- yet. In particular, both do not have functional lease
+ yet. In particular, neither has functional lease
databases. This means that they will assign the same, fixed,
hardcoded addresses to any client that will ask. See <a class="xref" href="#dhcp4-limit" title="12.4. DHCPv4 Server Limitations">Section 12.4, “DHCPv4 Server Limitations”</a> and <a class="xref" href="#dhcp6-limit" title="13.4. DHCPv6 Server Limitations">Section 13.4, “DHCPv6 Server Limitations”</a> for
detailed description.
- </p></div><div class="section" title="12.1. DHCPv4 Server Usage"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dhcp4-usage"></a>12.1. DHCPv4 Server Usage</h2></div></div></div><p>BIND10 provides DHCPv4 server component since December
+ </p></div><div class="section" title="12.1. DHCPv4 Server Usage"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dhcp4-usage"></a>12.1. DHCPv4 Server Usage</h2></div></div></div><p>BIND10 provides the DHCPv4 server component since December
2011. It is a skeleton server and can be described as an early
prototype that is not fully functional yet. It is mature enough
to conduct first tests in lab environment, but it has
significant limitations. See <a class="xref" href="#dhcp4-limit" title="12.4. DHCPv4 Server Limitations">Section 12.4, “DHCPv4 Server Limitations”</a> for
details.
</p><p>
- DHCPv4 server is implemented as <span class="command"><strong>b10-dhcp4</strong></span>
+ The DHCPv4 server is implemented as <span class="command"><strong>b10-dhcp4</strong></span>
daemon. As it is not configurable yet, it is fully autonomous,
- i.e. it does not interact with <span class="command"><strong>b10-cfgmgr</strong></span>.
+ that is it does not interact with <span class="command"><strong>b10-cfgmgr</strong></span>.
To start DHCPv4 server, simply input:
</p><pre class="screen">
@@ -959,16 +954,16 @@ Xfrout/transfer_acl[0] {"action": "ACCEPT"} any (default)</pre><p>
directory, in /usr/local/bin/b10-dhcp4 or other directory
you specified during compilation.
- After start, server will detect available network interfaces
+ At start, the server will detect available network interfaces
and will attempt to open UDP sockets on all interfaces that
- are up, running, are not loopback and have IPv4 address
+ are up, running, are not loopback, and have IPv4 address
assigned.
- Server will then listen to incoming traffic. Currently
- supported client messages are DISCOVER and REQUEST. Server
+ The server will then listen to incoming traffic. Currently
+ supported client messages are DISCOVER and REQUEST. The server
will respond to them with OFFER and ACK, respectively.
- As DHCPv4 server opens privileged ports, it requires root
+ Since the DHCPv4 server opens privileged ports, it requires root
access. Make sure you run this daemon as root.</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
Integration with <span class="command"><strong>bind10</strong></span> is
planned. Ultimately, <span class="command"><strong>b10-dhcp4</strong></span> will not
@@ -976,12 +971,12 @@ Xfrout/transfer_acl[0] {"action": "ACCEPT"} any (default)</pre><p>
<span class="command"><strong>bind10</strong></span>. Please be aware of this planned
change.
</p></div></div><div class="section" title="12.2. DHCPv4 Server Configuration"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dhcp4-config"></a>12.2. DHCPv4 Server Configuration</h2></div></div></div><p>
- DHCPv4 server does not have lease database implemented yet
- or any support for configuration, so every time the same set
+ The DHCPv4 server does not have a lease database implemented yet
+ nor any support for configuration, so every time the same set
of configuration options (including the same fixed address)
will be assigned every time.
</p><p>
- At this stage of development, the only way to alter server
+ At this stage of development, the only way to alter the server
configuration is to tweak its source code. To do so, please
edit src/bin/dhcp4/dhcp4_srv.cc file and modify following
parameters and recompile:
@@ -1000,22 +995,23 @@ const std::string HARDCODED_SERVER_ID = "192.0.2.1";</pre><p>
REQUEST, and ACK.</li><li class="listitem">RFC2132: Supported options are: PAD (0),
END(255), Message Type(53), DHCP Server Identifier (54),
Domain Name (15), DNS Servers (6), IP Address Lease Time
- (51), Subnet mask (1), and Routers (3).</li></ul></div></div><div class="section" title="12.4. DHCPv4 Server Limitations"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dhcp4-limit"></a>12.4. DHCPv4 Server Limitations</h2></div></div></div><p> These are the current limitations of DHCPv4 server
+ (51), Subnet mask (1), and Routers (3).</li></ul></div></div><div class="section" title="12.4. DHCPv4 Server Limitations"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dhcp4-limit"></a>12.4. DHCPv4 Server Limitations</h2></div></div></div><p>These are the current limitations of the DHCPv4 server
software. Most of them are reflections of the early stage of
development and should be treated as <span class="quote">“<span class="quote">not implemented
- yet</span>”</span>, rather than actual limitations.</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">During initial IPv4 node configuration, server is
- expected to send packets to a node that does not have IPv4
- address assigned yet. Server requires certain tricks (or
- hacks) to transmit such packets. This is not implemented
- yet, therefore DHCPv4 server supports relayed traffic only
- (that is normal point to point communication).</li><li class="listitem"><span class="command"><strong>b10-dhcp4</strong></span> provides a single,
+ yet</span>”</span>, rather than actual limitations.</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">During initial IPv4 node configuration, the
+ server is expected to send packets to a node that does not
+ have IPv4 address assigned yet. The server requires
+ certain tricks (or hacks) to transmit such packets. This
+ is not implemented yet, therefore DHCPv4 server supports
+ relayed traffic only (that is, normal point to point
+ communication).</li><li class="listitem"><span class="command"><strong>b10-dhcp4</strong></span> provides a single,
fixed, hardcoded lease to any client that asks. There is
no lease manager implemented. If two clients request
addresses, they will both get the same fixed
address.</li><li class="listitem"><span class="command"><strong>b10-dhcp4</strong></span> does not support any
configuration mechanisms yet. The whole configuration is
currently hardcoded. The only way to tweak configuration
- is to directly modify source code. See see <a class="xref" href="#dhcp4-config" title="12.2. DHCPv4 Server Configuration">Section 12.2, “DHCPv4 Server Configuration”</a> for details.</li><li class="listitem">Upon start, server will open sockets on all
+ is to directly modify source code. See see <a class="xref" href="#dhcp4-config" title="12.2. DHCPv4 Server Configuration">Section 12.2, “DHCPv4 Server Configuration”</a> for details.</li><li class="listitem">Upon start, the server will open sockets on all
interfaces that are not loopback, are up and running and
have IPv4 address. Support for multiple interfaces is not
coded in reception routines yet, so if you are running
@@ -1036,33 +1032,33 @@ const std::string HARDCODED_SERVER_ID = "192.0.2.1";</pre><p>
sending ICMP echo request.</li><li class="listitem">Address renewal (RENEW), rebinding (REBIND),
confirmation (CONFIRM), duplication report (DECLINE) and
release (RELEASE) are not supported yet.</li><li class="listitem">DNS Update is not supported yet.</li><li class="listitem">-v (verbose) command line option is currently
- permanently enabled.</li></ul></div></div></div><div class="chapter" title="Chapter 13. DHCPv6 Server"><div class="titlepage"><div><div><h2 class="title"><a name="dhcp6"></a>Chapter 13. DHCPv6 Server</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#dhcp6-usage">13.1. DHCPv6 Server Usage</a></span></dt><dt><span class="section"><a href="#dhcp6-config">13.2. DHCPv6 Server Configuration</a></span></dt><dt><span class="section"><a href="#dhcp6-std">13.3. Supported DHCPv6 Standards</a></span></dt><dt><span class="section"><a href="#dhcp6-limit">13.4. DHCPv6 Server Limitations</a></span></dt></dl></div><p>Dynamic Host Configuration Protocol for IPv6 (DHCPv6) is
+ the default, and cannot be disabled.</li></ul></div></div></div><div class="chapter" title="Chapter 13. DHCPv6 Server"><div class="titlepage"><div><div><h2 class="title"><a name="dhcp6"></a>Chapter 13. DHCPv6 Server</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#dhcp6-usage">13.1. DHCPv6 Server Usage</a></span></dt><dt><span class="section"><a href="#dhcp6-config">13.2. DHCPv6 Server Configuration</a></span></dt><dt><span class="section"><a href="#dhcp6-std">13.3. Supported DHCPv6 Standards</a></span></dt><dt><span class="section"><a href="#dhcp6-limit">13.4. DHCPv6 Server Limitations</a></span></dt></dl></div><p>Dynamic Host Configuration Protocol for IPv6 (DHCPv6) is
specified in RFC3315. BIND10 provides DHCPv6 server implementation
- that is described in this chapter. For DHCPv4 server
- implementation, see <a class="xref" href="#dhcp4" title="Chapter 12. DHCPv4 Server">Chapter 12, <i>DHCPv4 Server</i></a>.
- </p><p>DHCPv6 server component is currently under intense
+ that is described in this chapter. For a description of the DHCPv4
+ server implementation, see <a class="xref" href="#dhcp4" title="Chapter 12. DHCPv4 Server">Chapter 12, <i>DHCPv4 Server</i></a>.
+ </p><p>The DHCPv6 server component is currently under intense
development. You may want to check out <a class="ulink" href="http://bind10.isc.org/wiki/Kea" target="_top">BIND10 DHCP (Kea) wiki</a>
and recent posts on <a class="ulink" href="https://lists.isc.org/mailman/listinfo/bind10-dev" target="_top">BIND10
- developers mailing list</a>.</p><p>DHCPv4 and DHCPv6 components in BIND10 architecture are
+ developers mailing list</a>.</p><p>The DHCPv4 and DHCPv6 components in BIND10 architecture are
internally code named <span class="quote">“<span class="quote">Kea</span>”</span>.</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
As of December 2011, both DHCPv4 and DHCPv6 components are
skeleton servers. That means that while they are capable of
performing DHCP configuration, they are not fully functional
- yet. In particular, both do not have functional lease
+ yet. In particular, neither has functional lease
databases. This means that they will assign the same, fixed,
hardcoded addresses to any client that will ask. See <a class="xref" href="#dhcp4-limit" title="12.4. DHCPv4 Server Limitations">Section 12.4, “DHCPv4 Server Limitations”</a> and <a class="xref" href="#dhcp6-limit" title="13.4. DHCPv6 Server Limitations">Section 13.4, “DHCPv6 Server Limitations”</a> for
detailed description.
</p></div><div class="section" title="13.1. DHCPv6 Server Usage"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dhcp6-usage"></a>13.1. DHCPv6 Server Usage</h2></div></div></div><p>
- BIND10 provides DHCPv6 server component since September
+ BIND10 provides the DHCPv6 server component since September
2011. It is a skeleton server and can be described as an early
prototype that is not fully functional yet. It is mature
enough to conduct first tests in lab environment, but it has
significant limitations. See <a class="xref" href="#dhcp6-limit" title="13.4. DHCPv6 Server Limitations">Section 13.4, “DHCPv6 Server Limitations”</a> for
details.
</p><p>
- DHCPv6 server is implemented as <span class="command"><strong>b10-dhcp6</strong></span>
+ The DHCPv6 server is implemented as <span class="command"><strong>b10-dhcp6</strong></span>
daemon. As it is not configurable yet, it is fully autonomous,
- i.e. it does not interact with <span class="command"><strong>b10-cfgmgr</strong></span>.
+ that is it does not interact with <span class="command"><strong>b10-cfgmgr</strong></span>.
To start DHCPv6 server, simply input:
</p><pre class="screen">
@@ -1075,16 +1071,16 @@ const std::string HARDCODED_SERVER_ID = "192.0.2.1";</pre><p>
directory, in /usr/local/bin/b10-dhcp6 or other directory
you specified during compilation.
- After start, server will detect available network interfaces
+ At start, server will detect available network interfaces
and will attempt to open UDP sockets on all interfaces that
- are up, running, are not loopback, are multicast-capable and
+ are up, running, are not loopback, are multicast-capable, and
have IPv6 address assigned.
- Server will then listen to incoming traffic. Currently
- supported client messages are SOLICIT and REQUEST. Server
+ The server will then listen to incoming traffic. Currently
+ supported client messages are SOLICIT and REQUEST. The server
will respond to them with ADVERTISE and REPLY, respectively.
- As DHCPv6 server opens privileged ports, it requires root
+ Since the DHCPv6 server opens privileged ports, it requires root
access. Make sure you run this daemon as root.
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
Integration with <span class="command"><strong>bind10</strong></span> is
@@ -1093,7 +1089,7 @@ const std::string HARDCODED_SERVER_ID = "192.0.2.1";</pre><p>
<span class="command"><strong>bind10</strong></span>. Please be aware of this planned
change.
</p></div></div><div class="section" title="13.2. DHCPv6 Server Configuration"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dhcp6-config"></a>13.2. DHCPv6 Server Configuration</h2></div></div></div><p>
- DHCPv4 server does not have lease database implemented yet
+ The DHCPv6 server does not have lease database implemented yet
or any support for configuration, so every time the same set
of configuration options (including the same fixed address)
will be assigned every time.
@@ -1114,7 +1110,7 @@ const std::string HARDCODED_DNS_SERVER = "2001:db8:1::1";</pre><p>
</p></div><div class="section" title="13.3. Supported DHCPv6 Standards"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dhcp6-std"></a>13.3. Supported DHCPv6 Standards</h2></div></div></div><p>The following standards and draft standards are currently
supported:</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">RFC3315: Supported messages are SOLICIT,
ADVERTISE, REQUEST, and REPLY. Supported options are
- SERVER_ID, CLIENT_ID, IA_NA, and IAADDRESS.</li><li class="listitem">RFC3646: Supported option is DNS_SERVERS.</li></ul></div></div><div class="section" title="13.4. DHCPv6 Server Limitations"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dhcp6-limit"></a>13.4. DHCPv6 Server Limitations</h2></div></div></div><p> These are the current limitations of DHCPv6 server
+ SERVER_ID, CLIENT_ID, IA_NA, and IAADDRESS.</li><li class="listitem">RFC3646: Supported option is DNS_SERVERS.</li></ul></div></div><div class="section" title="13.4. DHCPv6 Server Limitations"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="dhcp6-limit"></a>13.4. DHCPv6 Server Limitations</h2></div></div></div><p> These are the current limitations of the DHCPv6 server
software. Most of them are reflections of the early stage of
development and should be treated as <span class="quote">“<span class="quote">not implemented
yet</span>”</span>, rather than actual limitations.</p><p>
@@ -1124,7 +1120,7 @@ const std::string HARDCODED_DNS_SERVER = "2001:db8:1::1";</pre><p>
they will both get the same fixed address.</li><li class="listitem"><span class="command"><strong>b10-dhcp6</strong></span> does not support any
configuration mechanisms yet. The whole configuration is
currently hardcoded. The only way to tweak configuration
- is to directly modify source code. See see <a class="xref" href="#dhcp6-config" title="13.2. DHCPv6 Server Configuration">Section 13.2, “DHCPv6 Server Configuration”</a> for details.</li><li class="listitem">Upon start, server will open sockets on all
+ is to directly modify source code. See see <a class="xref" href="#dhcp6-config" title="13.2. DHCPv6 Server Configuration">Section 13.2, “DHCPv6 Server Configuration”</a> for details.</li><li class="listitem">Upon start, the server will open sockets on all
interfaces that are not loopback, are up, running and are
multicast capable and have IPv6 address. Support for
multiple interfaces is not coded in reception routines yet,
@@ -1137,8 +1133,8 @@ const std::string HARDCODED_DNS_SERVER = "2001:db8:1::1";</pre><p>
assigns DNS SERVER option.</li><li class="listitem">Temporary addresses are not supported yet.</li><li class="listitem">Prefix delegation is not supported yet.</li><li class="listitem">Address renewal (RENEW), rebinding (REBIND),
confirmation (CONFIRM), duplication report (DECLINE) and
release (RELEASE) are not supported yet.</li><li class="listitem">DNS Update is not supported yet.</li><li class="listitem">Interface detection is currently working on Linux
- only. See <a class="xref" href="#iface-detect" title="14.1. Interface detection">Section 14.1, “Interface detection”</a> for details.</li><li class="listitem">-v (verbose) command line option is currently permanently
- enabled.</li></ul></div><p>
+ only. See <a class="xref" href="#iface-detect" title="14.1. Interface detection">Section 14.1, “Interface detection”</a> for details.</li><li class="listitem">-v (verbose) command line option is currently the
+ default, and cannot be disabled.</li></ul></div><p>
</p></div></div><div class="chapter" title="Chapter 14. libdhcp++ library"><div class="titlepage"><div><div><h2 class="title"><a name="libdhcp"></a>Chapter 14. libdhcp++ library</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#iface-detect">14.1. Interface detection</a></span></dt><dt><span class="section"><a href="#packet-handling">14.2. DHCPv4/DHCPv6 packet handling</a></span></dt></dl></div><p>libdhcp++ is a common library written in C++ that handles
many DHCP-related tasks, like DHCPv4 and DHCPv6 packets parsing,
manipulation and assembly, option parsing, manipulation and
@@ -1152,15 +1148,15 @@ const std::string HARDCODED_DNS_SERVER = "2001:db8:1::1";</pre><p>
any kind of DHCP-related software.
</p><div class="section" title="14.1. Interface detection"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="iface-detect"></a>14.1. Interface detection</h2></div></div></div><p>Both DHCPv4 and DHCPv6 components share network
interface detection routines. Interface detection is
- currently only supported on Linux systems.</p><p>For non-linux systems, there is currently stub
+ currently only supported on Linux systems.</p><p>For non-Linux systems, there is currently stub
implementation provided. As DHCP servers need to know available
addresses, there is a simple mechanism implemented to provide
that information. User is expected to create interfaces.txt
file. Format of this file is simple. It contains list of
interfaces along with available address on each interface. This
mechanism is temporary and is going to be removed as soon as
- interface detection becomes available on non-linux
- systems. Example of interfaces.txt file looks as follows:
+ interface detection becomes available on non-Linux
+ systems. Here is an example of the interfaces.txt file:
</p><pre class="screen">
# For DHCPv6, please specify link-local address (starts with fe80::)
# If in doubt, check output of 'ifconfig -a' command.
@@ -1202,7 +1198,7 @@ eth0 fe80::21e:8cff:fe9b:7349
}
}
</pre><p>
- </p></div><div class="chapter" title="Chapter 16. Logging"><div class="titlepage"><div><div><h2 class="title"><a name="logging"></a>Chapter 16. Logging</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id461660">16.1. Logging configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#id461675">16.1.1. Loggers</a></span></dt><dt><span class="section"><a href="#id461978">16.1.2. Output Options</a></span></dt><dt><span class="section"><a href="#id462172">16.1.3. Example session</a></span></dt></dl></dd><dt><span class="section"><a href="#id462428">16.2. Logging Message Format</a></span></dt></dl></div><div class="section" title="16.1. Logging configuration"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id461660"></a>16.1. Logging configuration</h2></div></div></div><p>
+ </p></div><div class="chapter" title="Chapter 16. Logging"><div class="titlepage"><div><div><h2 class="title"><a name="logging"></a>Chapter 16. Logging</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id1168229439976">16.1. Logging configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#id1168229439987">16.1.1. Loggers</a></span></dt><dt><span class="section"><a href="#id1168229440229">16.1.2. Output Options</a></span></dt><dt><span class="section"><a href="#id1168229440471">16.1.3. Example session</a></span></dt></dl></dd><dt><span class="section"><a href="#id1168229440680">16.2. Logging Message Format</a></span></dt></dl></div><div class="section" title="16.1. Logging configuration"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168229439976"></a>16.1. Logging configuration</h2></div></div></div><p>
The logging system in BIND 10 is configured through the
Logging module. All BIND 10 modules will look at the
@@ -1211,7 +1207,7 @@ eth0 fe80::21e:8cff:fe9b:7349
- </p><div class="section" title="16.1.1. Loggers"><div class="titlepage"><div><div><h3 class="title"><a name="id461675"></a>16.1.1. Loggers</h3></div></div></div><p>
+ </p><div class="section" title="16.1.1. Loggers"><div class="titlepage"><div><div><h3 class="title"><a name="id1168229439987"></a>16.1.1. 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
@@ -1232,7 +1228,7 @@ eth0 fe80::21e:8cff:fe9b:7349
(what to log), and the <code class="option">output_options</code>
(where to log).
- </p><div class="section" title="16.1.1.1. name (string)"><div class="titlepage"><div><div><h4 class="title"><a name="id461706"></a>16.1.1.1. name (string)</h4></div></div></div><p>
+ </p><div class="section" title="16.1.1.1. name (string)"><div class="titlepage"><div><div><h4 class="title"><a name="id1168229440011"></a>16.1.1.1. 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,
@@ -1305,7 +1301,7 @@ eth0 fe80::21e:8cff:fe9b:7349
<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="16.1.1.2. severity (string)"><div class="titlepage"><div><div><h4 class="title"><a name="id461840"></a>16.1.1.2. severity (string)</h4></div></div></div><p>
+ </p></div><div class="section" title="16.1.1.2. severity (string)"><div class="titlepage"><div><div><h4 class="title"><a name="id1168229440112"></a>16.1.1.2. severity (string)</h4></div></div></div><p>
This specifies the category of messages logged.
Each message is logged with an associated severity which
@@ -1321,7 +1317,7 @@ eth0 fe80::21e:8cff:fe9b:7349
- </p></div><div class="section" title="16.1.1.3. output_options (list)"><div class="titlepage"><div><div><h4 class="title"><a name="id461898"></a>16.1.1.3. output_options (list)</h4></div></div></div><p>
+ </p></div><div class="section" title="16.1.1.3. output_options (list)"><div class="titlepage"><div><div><h4 class="title"><a name="id1168229440162"></a>16.1.1.3. 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
@@ -1331,7 +1327,7 @@ eth0 fe80::21e:8cff:fe9b:7349
The other options for a logger are:
- </p></div><div class="section" title="16.1.1.4. debuglevel (integer)"><div class="titlepage"><div><div><h4 class="title"><a name="id461917"></a>16.1.1.4. debuglevel (integer)</h4></div></div></div><p>
+ </p></div><div class="section" title="16.1.1.4. debuglevel (integer)"><div class="titlepage"><div><div><h4 class="title"><a name="id1168229440179"></a>16.1.1.4. 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
@@ -1340,7 +1336,7 @@ eth0 fe80::21e:8cff:fe9b:7349
If severity for the logger is not DEBUG, this value is ignored.
- </p></div><div class="section" title="16.1.1.5. additive (true or false)"><div class="titlepage"><div><div><h4 class="title"><a name="id461937"></a>16.1.1.5. additive (true or false)</h4></div></div></div><p>
+ </p></div><div class="section" title="16.1.1.5. additive (true or false)"><div class="titlepage"><div><div><h4 class="title"><a name="id1168229440194"></a>16.1.1.5. 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
@@ -1354,18 +1350,18 @@ eth0 fe80::21e:8cff:fe9b:7349
- </p></div></div><div class="section" title="16.1.2. Output Options"><div class="titlepage"><div><div><h3 class="title"><a name="id461978"></a>16.1.2. Output Options</h3></div></div></div><p>
+ </p></div></div><div class="section" title="16.1.2. Output Options"><div class="titlepage"><div><div><h3 class="title"><a name="id1168229440229"></a>16.1.2. 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="16.1.2.1. destination (string)"><div class="titlepage"><div><div><h4 class="title"><a name="id461995"></a>16.1.2.1. destination (string)</h4></div></div></div><p>
+ </p><div class="section" title="16.1.2.1. destination (string)"><div class="titlepage"><div><div><h4 class="title"><a name="id1168229440245"></a>16.1.2.1. 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="16.1.2.2. output (string)"><div class="titlepage"><div><div><h4 class="title"><a name="id462029"></a>16.1.2.2. output (string)</h4></div></div></div><p>
+ </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="16.1.2.2. output (string)"><div class="titlepage"><div><div><h4 class="title"><a name="id1168229440277"></a>16.1.2.2. output (string)</h4></div></div></div><p>
Depending on what is set as the output destination, this
value is interpreted as follows:
@@ -1387,12 +1383,12 @@ eth0 fe80::21e:8cff:fe9b:7349
The other options for <code class="option">output_options</code> are:
- </p><div class="section" title="16.1.2.2.1. flush (true of false)"><div class="titlepage"><div><div><h5 class="title"><a name="id462122"></a>16.1.2.2.1. flush (true of false)</h5></div></div></div><p>
+ </p><div class="section" title="16.1.2.2.1. flush (true of false)"><div class="titlepage"><div><div><h5 class="title"><a name="id1168229440361"></a>16.1.2.2.1. 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="16.1.2.2.2. maxsize (integer)"><div class="titlepage"><div><div><h5 class="title"><a name="id462134"></a>16.1.2.2.2. maxsize (integer)</h5></div></div></div><p>
+ </p></div><div class="section" title="16.1.2.2.2. maxsize (integer)"><div class="titlepage"><div><div><h5 class="title"><a name="id1168229440371"></a>16.1.2.2.2. 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.
@@ -1401,11 +1397,11 @@ eth0 fe80::21e:8cff:fe9b:7349
etc.)
</p><p>
If this is 0, no maximum file size is used.
- </p></div><div class="section" title="16.1.2.2.3. maxver (integer)"><div class="titlepage"><div><div><h5 class="title"><a name="id462151"></a>16.1.2.2.3. maxver (integer)</h5></div></div></div><p>
+ </p></div><div class="section" title="16.1.2.2.3. maxver (integer)"><div class="titlepage"><div><div><h5 class="title"><a name="id1168229440453"></a>16.1.2.2.3. 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="16.1.3. Example session"><div class="titlepage"><div><div><h3 class="title"><a name="id462172"></a>16.1.3. Example session</h3></div></div></div><p>
+ </p></div></div></div><div class="section" title="16.1.3. Example session"><div class="titlepage"><div><div><h3 class="title"><a name="id1168229440471"></a>16.1.3. 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>,
@@ -1566,7 +1562,7 @@ Logging/loggers[0]/output_options[0]/maxver 8 integer (modified)
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="16.2. Logging Message Format"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id462428"></a>16.2. Logging Message Format</h2></div></div></div><p>
+ </p></div></div><div class="section" title="16.2. Logging Message Format"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1168229440680"></a>16.2. 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
@@ -1612,5 +1608,4 @@ Logging/loggers[0]/output_options[0]/maxver 8 integer (modified)
consulting your system's documentation to identify
what error number 111 means.
</p></dd></dl></div><p>
- </p></div></div><div class="chapter" title="Chapter 17. Acknowledgements"><div class="titlepage"><div><div><h2 class="title"><a name="id462551"></a>Chapter 17. Acknowledgements</h2></div></div></div><p>ISC would like to acknowledge generous support for
- development of DHCPv4 and DHCPv6 components provided by <a class="ulink" href="http://www.comcast.com" target="_top">Comcast</a>.</p></div></div></body></html>
+ </p></div></div></div></body></html>
diff --git a/doc/guide/bind10-guide.txt b/doc/guide/bind10-guide.txt
index 9c8ffbe..52e7b0f 100644
--- a/doc/guide/bind10-guide.txt
+++ b/doc/guide/bind10-guide.txt
@@ -2,17 +2,19 @@
Administrator Reference for BIND 10
- This is the reference guide for BIND 10 version 20111021.
+ This is the reference guide for BIND 10 version 20111129.
Copyright (c) 2010-2011 Internet Systems Consortium, Inc.
Abstract
- 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.
+ BIND 10 is a framework that features Domain Name System (DNS) suite and
+ Dynamic Host Configuration Protocol (DHCP) servers managed by Internet
+ Systems Consortium (ISC). It includes DNS libraries, modular components
+ for controlling authoritative and recursive DNS servers, and experimental
+ DHCPv4 and DHCPv6 servers.
- This is the reference guide for BIND 10 version 20111021. The most
+ This is the reference guide for BIND 10 version 20111129. The most
up-to-date version of this document (in PDF, HTML, and plain text
formats), along with other documents for BIND 10, can be found at
http://bind10.isc.org/docs.
@@ -21,41 +23,45 @@ Administrator Reference for BIND 10
Table of Contents
+ Preface
+
+ 1. Acknowledgements
+
1. Introduction
- Supported Platforms
+ 1.1. Supported Platforms
- Required Software
+ 1.2. Required Software
- Starting and Stopping the Server
+ 1.3. Starting and Stopping the Server
- Managing BIND 10
+ 1.4. Managing BIND 10
2. Installation
- Building Requirements
+ 2.1. Building Requirements
- Quick start
+ 2.2. Quick start
- Installation from source
+ 2.3. Installation from source
- Download Tar File
+ 2.3.1. Download Tar File
- Retrieve from Git
+ 2.3.2. Retrieve from Git
- Configure before the build
+ 2.3.3. Configure before the build
- Build
+ 2.3.4. Build
- Install
+ 2.3.5. Install
- Install Hierarchy
+ 2.3.6. Install Hierarchy
3. Starting BIND10 with bind10
- Starting BIND 10
+ 3.1. Starting BIND 10
- Configuration of started processes
+ 3.2. Configuration of started processes
4. Command channel
@@ -63,101 +69,138 @@ Administrator Reference for BIND 10
6. Remote control daemon
- Configuration specification for b10-cmdctl
+ 6.1. Configuration specification for b10-cmdctl
7. Control and configure user interface
8. Authoritative Server
- Server Configurations
+ 8.1. Server Configurations
- Data Source Backends
+ 8.2. Data Source Backends
- Loading Master Zones Files
+ 8.3. Loading Master Zones Files
9. Incoming Zone Transfers
- Configuration for Incoming Zone Transfers
+ 9.1. Configuration for Incoming Zone Transfers
- Enabling IXFR
+ 9.2. Enabling IXFR
- Trigger an Incoming Zone Transfer Manually
+ 9.3. Secondary Manager
+
+ 9.4. Trigger an Incoming Zone Transfer Manually
10. Outbound Zone Transfers
- 11. Secondary Manager
+ 11. Recursive Name Server
+
+ 11.1. Access Control
+
+ 11.2. Forwarding
+
+ 12. DHCPv4 Server
+
+ 12.1. DHCPv4 Server Usage
+
+ 12.2. DHCPv4 Server Configuration
+
+ 12.3. Supported standards
+
+ 12.4. DHCPv4 Server Limitations
+
+ 13. DHCPv6 Server
+
+ 13.1. DHCPv6 Server Usage
+
+ 13.2. DHCPv6 Server Configuration
+
+ 13.3. Supported DHCPv6 Standards
- 12. Recursive Name Server
+ 13.4. DHCPv6 Server Limitations
- Access Control
+ 14. libdhcp++ library
- Forwarding
+ 14.1. Interface detection
- 13. Statistics
+ 14.2. DHCPv4/DHCPv6 packet handling
- 14. Logging
+ 15. Statistics
- Logging configuration
+ 16. Logging
- Loggers
+ 16.1. Logging configuration
- Output Options
+ 16.1.1. Loggers
- Example session
+ 16.1.2. Output Options
- Logging Message Format
+ 16.1.3. Example session
+
+ 16.2. Logging Message Format
List of Tables
3.1.
+Preface
+
+ Table of Contents
+
+ 1. Acknowledgements
+
+1. Acknowledgements
+
+ ISC would like to acknowledge generous support for BIND 10 development of
+ DHCPv4 and DHCPv6 components provided by Comcast.
+
Chapter 1. Introduction
Table of Contents
- Supported Platforms
+ 1.1. Supported Platforms
- Required Software
+ 1.2. Required Software
- Starting and Stopping the Server
+ 1.3. Starting and Stopping the Server
- Managing BIND 10
+ 1.4. Managing BIND 10
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.
+ DNS. BIND 10 provides a EDNS0- and DNSSEC-capable authoritative DNS server
+ and a caching recursive name server which also provides forwarding.
- Note
-
- This guide covers the experimental prototype of BIND 10 version 20111021.
-
- Note
+ This guide covers the experimental prototype of BIND 10 version 20111129.
- BIND 10 provides a EDNS0- and DNSSEC-capable authoritative DNS server and
- a caching recursive name server which also provides forwarding.
+1.1. Supported Platforms
-Supported Platforms
+ BIND 10 builds have been tested on Debian GNU/Linux 5 and unstable, Ubuntu
+ 9.10, NetBSD 5, Solaris 10, FreeBSD 7 and 8, CentOS Linux 5.3, and MacOS
+ 10.6. It has been tested on Sparc, i386, and amd64 hardware platforms. It
+ is planned for BIND 10 to build, install and run on Windows and standard
+ Unix-type platforms.
- 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. It has been tested
- on Sparc, i386, and amd64 hardware platforms. It is planned for BIND 10 to
- build, install and run on Windows and standard Unix-type platforms.
+1.2. Required Software
-Required Software
+ BIND 10 requires at least Python 3.1 (http://www.python.org/). It has also
+ been tested with Python 3.2.
- BIND 10 requires Python 3.1. Later versions may work, but Python 3.1 is
- the minimum version which will work.
+ BIND 10 uses the Botan crypto library for C++
+ (http://botan.randombit.net/). It requires at least Botan version 1.8.
- BIND 10 uses the Botan crypto library for C++. It requires at least Botan
- version 1.8.
+ BIND 10 uses the log4cplus C++ logging library
+ (http://log4cplus.sourceforge.net/). It requires at least log4cplus
+ version 1.0.3.
- BIND 10 uses the log4cplus C++ logging library. It requires at least
- log4cplus version 1.0.3.
+ The authoritative DNS server uses SQLite3 (http://www.sqlite.org/). It
+ needs at least SQLite version 3.3.9.
- The authoritative server requires SQLite 3.3.9 or newer. The b10-xfrin,
- b10-xfrout, and b10-zonemgr modules require the libpython3 library and the
- Python _sqlite3.so module.
+ The b10-xfrin, b10-xfrout, and b10-zonemgr components require the
+ libpython3 library and the Python _sqlite3.so module (which is included
+ with Python). The Python module needs to be built for the corresponding
+ Python 3.
Note
@@ -165,7 +208,7 @@ Required Software
installation nor standard packages collections. You may need to install
them separately.
-Starting and Stopping the Server
+1.3. Starting and Stopping the Server
BIND 10 is modular. Part of this modularity is accomplished using multiple
cooperating processes which, together, provide the server functionality.
@@ -201,7 +244,7 @@ Starting and Stopping the Server
These are ran automatically by bind10 and do not need to be run manually.
-Managing BIND 10
+1.4. Managing BIND 10
Once BIND 10 is running, a few commands are used to interact directly with
the system:
@@ -224,25 +267,25 @@ Chapter 2. Installation
Table of Contents
- Building Requirements
+ 2.1. Building Requirements
- Quick start
+ 2.2. Quick start
- Installation from source
+ 2.3. Installation from source
- Download Tar File
+ 2.3.1. Download Tar File
- Retrieve from Git
+ 2.3.2. Retrieve from Git
- Configure before the build
+ 2.3.3. Configure before the build
- Build
+ 2.3.4. Build
- Install
+ 2.3.5. Install
- Install Hierarchy
+ 2.3.6. Install Hierarchy
-Building Requirements
+2.1. Building Requirements
In addition to the run-time requirements, building BIND 10 from source
code requires various development include headers.
@@ -254,25 +297,21 @@ Building Requirements
development package versions, which include header files and libraries, to
build BIND 10 from source code.
- Building from source code requires the Boost build-time headers. At least
- Boost version 1.35 is required.
+ Building from source code requires the Boost build-time headers
+ (http://www.boost.org/). At least Boost version 1.35 is required.
To build BIND 10, also install the Botan (at least version 1.8) and the
log4cplus (at least version 1.0.3) development include headers.
- The Python Library and Python _sqlite3 module are required to enable the
- Xfrout and Xfrin support.
-
- Note
-
- The Python related libraries and modules need to be built for Python 3.1.
-
Building BIND 10 also requires a C++ compiler and standard development
headers, make, and pkg-config. BIND 10 builds have been tested with GCC
g++ 3.4.3, 4.1.2, 4.1.3, 4.2.1, 4.3.2, and 4.4.1; Clang++ 2.8; and Sun C++
5.10.
-Quick start
+ Visit the wiki at http://bind10.isc.org/wiki/SystemSpecificNotes for
+ system-specific installation tips.
+
+2.2. Quick start
Note
@@ -283,7 +322,7 @@ Quick start
To quickly get started with BIND 10, follow these steps.
- 1. Install required build dependencies.
+ 1. Install required run-time and build dependencies.
2. Download the BIND 10 source tar file from
ftp://ftp.isc.org/isc/bind10/.
3. Extract the tar file:
@@ -317,14 +356,14 @@ Quick start
10. Test the new zone.
-Installation from source
+2.3. Installation from source
BIND 10 is open source software written in C++ and Python. It is freely
available in source code form from ISC via 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.
- Download Tar File
+ 2.3.1. Download Tar File
Downloading a release tar file is the recommended method to obtain the
source code.
@@ -333,7 +372,7 @@ Installation from source
ftp://ftp.isc.org/isc/bind10/. Periodic development snapshots may also be
available.
- Retrieve from Git
+ 2.3.2. Retrieve from Git
Downloading this "bleeding edge" code is recommended only for developers
or advanced users. Using development code in a production environment is
@@ -360,7 +399,7 @@ Installation from source
the --install switch. This will run autoconf, aclocal, libtoolize,
autoheader, automake, and related commands.
- Configure before the build
+ 2.3.3. Configure before the build
BIND 10 uses the GNU Build System to discover build environment details.
To generate the makefiles using the defaults, simply run:
@@ -395,14 +434,14 @@ Installation from source
If the configure fails, it may be due to missing or old dependencies.
- Build
+ 2.3.4. Build
After the configure step is complete, to build the executables from the
C++ code and prepare the Python scripts, run:
$ make
- Install
+ 2.3.5. Install
To install the BIND 10 executables, support files, and documentation, run:
@@ -412,7 +451,7 @@ Installation from source
The install step may require superuser privileges.
- Install Hierarchy
+ 2.3.6. Install Hierarchy
The following is the layout of the complete BIND 10 installation:
@@ -431,9 +470,9 @@ Chapter 3. Starting BIND10 with bind10
Table of Contents
- Starting BIND 10
+ 3.1. Starting BIND 10
- Configuration of started processes
+ 3.2. Configuration of started processes
BIND 10 provides the bind10 command which starts up the required
processes. bind10 will also restart some processes that exit unexpectedly.
@@ -456,7 +495,7 @@ Chapter 3. Starting BIND10 with bind10
for inbound DNS zone transfers, b10-xfrout for outbound DNS zone
transfers, and b10-zonemgr for secondary service.
-Starting BIND 10
+3.1. Starting BIND 10
To start the BIND 10 service, simply run bind10. Run it with the --verbose
switch to get additional debugging or diagnostic output.
@@ -467,7 +506,7 @@ Starting BIND 10
names for the Python-based daemons will be renamed to better identify them
instead of just "python". This is not needed on some operating systems.
-Configuration of started processes
+3.2. Configuration of started processes
The processes to be started can be configured, with the exception of the
b10-sockcreator, b10-msgq and b10-cfgmgr.
@@ -512,8 +551,6 @@ Configuration of started processes
|--------------+----------+----------------------------------------------|
| b10-cmdctl | cmdctl | The command control (remote control |
| | | interface) |
- |--------------+----------+----------------------------------------------|
- | setuid | setuid | Virtual component, see below |
+------------------------------------------------------------------------+
The kind specifies how a failure of the component should be handled. If it
@@ -530,7 +567,8 @@ Configuration of started processes
The priority defines order in which the components should start. The ones
with higher number are started sooner than the ones with lower ones. If
- you don't set it, 0 (zero) is used as the priority.
+ you don't set it, 0 (zero) is used as the priority. Usually, leaving it at
+ the default is enough.
There are other parameters we didn't use in our example. One of them is
"address". It is the address used by the component on the b10-msgq message
@@ -561,16 +599,6 @@ Configuration of started processes
In short, you should think twice before disabling something here.
- Now, to the mysterious setuid virtual component. If you use the -u option
- to start the bind10 as root, but change the user later, we need to start
- the b10-auth or b10-resolver as root (until the socket creator is
- finished). So we need to specify the time when the switch from root do the
- given user happens and that's what the setuid component is for. The switch
- is done at the time the setuid component would be started, if it was a
- process. The default configuration contains the setuid component with
- priority 5, b10-auth has 10 to be started before the switch and everything
- else is without priority, so it is started after the switch.
-
Chapter 4. Command channel
The BIND 10 components use the b10-msgq message routing daemon to
@@ -628,7 +656,7 @@ Chapter 6. Remote control daemon
Table of Contents
- Configuration specification for b10-cmdctl
+ 6.1. Configuration specification for b10-cmdctl
b10-cmdctl is the gateway between administrators and the BIND 10 system.
It is a HTTPS server that uses standard HTTP Digest Authentication for
@@ -675,7 +703,7 @@ Chapter 6. Remote control daemon
connection is stateless and timesout in 1200 seconds by default. This can
be redefined by using the --idle-timeout command line argument.
-Configuration specification for b10-cmdctl
+6.1. Configuration specification for b10-cmdctl
The configuration items for b10-cmdctl are: key_file cert_file
accounts_file
@@ -706,17 +734,17 @@ Chapter 8. Authoritative Server
Table of Contents
- Server Configurations
+ 8.1. Server Configurations
- Data Source Backends
+ 8.2. Data Source Backends
- Loading Master Zones Files
+ 8.3. Loading Master Zones Files
The b10-auth is the authoritative DNS server. It supports EDNS0 and
DNSSEC. It supports IPv6. Normally it is started by the bind10 master
process.
-Server Configurations
+8.1. Server Configurations
b10-auth is configured via the b10-cfgmgr configuration manager. The
module name is "Auth". The configuration data item is:
@@ -731,7 +759,7 @@ Server Configurations
shutdown
Stop the authoritative DNS server.
-Data Source Backends
+8.2. Data Source Backends
Note
@@ -746,7 +774,7 @@ Data Source Backends
/usr/local/var/.) This data file location may be changed by defining the
"database_file" configuration.
-Loading Master Zones Files
+8.3. Loading Master Zones Files
RFC 1035 style DNS master zone files may imported into a BIND 10 data
source by using the b10-loadzone utility.
@@ -781,11 +809,13 @@ Chapter 9. Incoming Zone Transfers
Table of Contents
- Configuration for Incoming Zone Transfers
+ 9.1. Configuration for Incoming Zone Transfers
+
+ 9.2. Enabling IXFR
- Enabling IXFR
+ 9.3. Secondary Manager
- Trigger an Incoming Zone Transfer Manually
+ 9.4. Trigger an Incoming Zone Transfer Manually
Incoming zones are transferred using the b10-xfrin process which is
started by bind10. When received, the zone is stored in the corresponding
@@ -803,7 +833,7 @@ Chapter 9. Incoming Zone Transfers
only available for SQLite3-based data sources, that is, they don't work
for an in-memory data source.
-Configuration for Incoming Zone Transfers
+9.1. Configuration for Incoming Zone Transfers
In practice, you need to specify a list of secondary zones to enable
incoming zone transfers for these zones (you can still trigger a zone
@@ -820,7 +850,7 @@ Configuration for Incoming Zone Transfers
(We assume there has been no zone configuration before).
-Enabling IXFR
+9.2. Enabling IXFR
As noted above, b10-xfrin uses AXFR for zone transfers by default. To
enable IXFR for zone transfers for a particular zone, set the use_ixfr
@@ -843,7 +873,33 @@ Enabling IXFR
be implemented in a near future version, at which point we will enable
IXFR by default.
-Trigger an Incoming Zone Transfer Manually
+9.3. Secondary Manager
+
+ The b10-zonemgr process is started by bind10. It keeps track of SOA
+ refresh, retry, and expire timers and other details for BIND 10 to perform
+ as a slave. When the b10-auth authoritative DNS server receives a NOTIFY
+ message, b10-zonemgr may tell b10-xfrin to do a refresh to start an
+ inbound zone transfer. The secondary manager resets its counters when a
+ new zone is transferred in.
+
+ Note
+
+ Access control (such as allowing notifies) is not yet provided. The
+ primary/secondary service is not yet complete.
+
+ The following example shows using bindctl to configure the server to be a
+ secondary for the example zone:
+
+ > config add Zonemgr/secondary_zones
+ > config set Zonemgr/secondary_zones[0]/name "example.com"
+ > config set Zonemgr/secondary_zones[0]/class "IN"
+ > config commit
+
+ If the zone does not exist in the data source already (i.e. no SOA record
+ for it), b10-zonemgr will automatically tell b10-xfrin to transfer the
+ zone in.
+
+9.4. Trigger an Incoming Zone Transfer Manually
To manually trigger a zone transfer to retrieve a remote zone, you may use
the bindctl utility. For example, at the bindctl prompt run:
@@ -903,27 +959,13 @@ Chapter 10. Outbound Zone Transfers
configuration. The way to specify zone specific configuration (ACLs, etc)
is likely to be changed, too.
-Chapter 11. Secondary Manager
-
- The b10-zonemgr process is started by bind10. It keeps track of SOA
- refresh, retry, and expire timers and other details for BIND 10 to perform
- as a slave. When the b10-auth authoritative DNS server receives a NOTIFY
- message, b10-zonemgr may tell b10-xfrin to do a refresh to start an
- inbound zone transfer. The secondary manager resets its counters when a
- new zone is transferred in.
-
- Note
-
- Access control (such as allowing notifies) is not yet provided. The
- primary/secondary service is not yet complete.
-
-Chapter 12. Recursive Name Server
+Chapter 11. Recursive Name Server
Table of Contents
- Access Control
+ 11.1. Access Control
- Forwarding
+ 11.2. Forwarding
The b10-resolver process is started by bind10.
@@ -954,7 +996,7 @@ Chapter 12. Recursive Name Server
(Replace the "2" as needed; run "config show Resolver/listen_on" if
needed.)
-Access Control
+11.1. Access Control
By default, the b10-resolver daemon only accepts DNS queries from the
localhost (127.0.0.1 and ::1). The Resolver/query_acl configuration may be
@@ -987,7 +1029,7 @@ Access Control
This prototype access control configuration syntax may be changed.
-Forwarding
+11.2. Forwarding
To enable forwarding, the upstream address and port must be configured to
forward queries to, such as:
@@ -1003,7 +1045,326 @@ Forwarding
> config set Resolver/forward_addresses []
> config commit
-Chapter 13. Statistics
+Chapter 12. DHCPv4 Server
+
+ Table of Contents
+
+ 12.1. DHCPv4 Server Usage
+
+ 12.2. DHCPv4 Server Configuration
+
+ 12.3. Supported standards
+
+ 12.4. DHCPv4 Server Limitations
+
+ Dynamic Host Configuration Protocol for IPv4 (DHCP or DHCPv4) and Dynamic
+ Host Configuration Protocol for IPv6 (DHCPv6) are protocols that allow one
+ node (server) to provision configuration parameters to many hosts and
+ devices (clients). To ease deployment in larger networks, additional nodes
+ (relays) may be deployed that facilitate communication between servers and
+ clients. Even though principles of both DHCPv4 and DHCPv6 are somewhat
+ similar, these are two radically different protocols. BIND10 offers server
+ implementations for both DHCPv4 and DHCPv6. This chapter is about DHCP for
+ IPv4. For a description of the DHCPv6 server, see Chapter 13, DHCPv6
+ Server.
+
+ The DHCPv4 server component is currently under intense development. You
+ may want to check out BIND10 DHCP (Kea) wiki and recent posts on BIND10
+ developers mailing list.
+
+ The DHCPv4 and DHCPv6 components in BIND10 architecture are internally
+ code named "Kea".
+
+ Note
+
+ As of December 2011, both DHCPv4 and DHCPv6 components are skeleton
+ servers. That means that while they are capable of performing DHCP
+ configuration, they are not fully functional yet. In particular, neither
+ has functional lease databases. This means that they will assign the same,
+ fixed, hardcoded addresses to any client that will ask. See Section 12.4,
+ "DHCPv4 Server Limitations" and Section 13.4, "DHCPv6 Server Limitations"
+ for detailed description.
+
+12.1. DHCPv4 Server Usage
+
+ BIND10 provides the DHCPv4 server component since December 2011. It is a
+ skeleton server and can be described as an early prototype that is not
+ fully functional yet. It is mature enough to conduct first tests in lab
+ environment, but it has significant limitations. See Section 12.4, "DHCPv4
+ Server Limitations" for details.
+
+ The DHCPv4 server is implemented as b10-dhcp4 daemon. As it is not
+ configurable yet, it is fully autonomous, that is it does not interact
+ with b10-cfgmgr. To start DHCPv4 server, simply input:
+
+ #cd src/bin/dhcp4
+ #./b10-dhcp4
+
+ Depending on your installation, b10-dhcp4 binary may reside in
+ src/bin/dhcp4 in your source code directory, in /usr/local/bin/b10-dhcp4
+ or other directory you specified during compilation. At start, the server
+ will detect available network interfaces and will attempt to open UDP
+ sockets on all interfaces that are up, running, are not loopback, and have
+ IPv4 address assigned. The server will then listen to incoming traffic.
+ Currently supported client messages are DISCOVER and REQUEST. The server
+ will respond to them with OFFER and ACK, respectively. Since the DHCPv4
+ server opens privileged ports, it requires root access. Make sure you run
+ this daemon as root.
+
+ Note
+
+ Integration with bind10 is planned. Ultimately, b10-dhcp4 will not be
+ started directly, but rather via bind10. Please be aware of this planned
+ change.
+
+12.2. DHCPv4 Server Configuration
+
+ The DHCPv4 server does not have a lease database implemented yet nor any
+ support for configuration, so every time the same set of configuration
+ options (including the same fixed address) will be assigned every time.
+
+ At this stage of development, the only way to alter the server
+ configuration is to tweak its source code. To do so, please edit
+ src/bin/dhcp4/dhcp4_srv.cc file and modify following parameters and
+ recompile:
+
+ const std::string HARDCODED_LEASE = "192.0.2.222"; // assigned lease
+ const std::string HARDCODED_NETMASK = "255.255.255.0";
+ const uint32_t HARDCODED_LEASE_TIME = 60; // in seconds
+ const std::string HARDCODED_GATEWAY = "192.0.2.1";
+ const std::string HARDCODED_DNS_SERVER = "192.0.2.2";
+ const std::string HARDCODED_DOMAIN_NAME = "isc.example.com";
+ const std::string HARDCODED_SERVER_ID = "192.0.2.1";
+
+ Lease database and configuration support is planned for 2012.
+
+12.3. Supported standards
+
+ The following standards and draft standards are currently supported:
+
+ o RFC2131: Supported messages are DISCOVER, OFFER, REQUEST, and ACK.
+ o RFC2132: Supported options are: PAD (0), END(255), Message Type(53),
+ DHCP Server Identifier (54), Domain Name (15), DNS Servers (6), IP
+ Address Lease Time (51), Subnet mask (1), and Routers (3).
+
+12.4. DHCPv4 Server Limitations
+
+ These are the current limitations of the DHCPv4 server software. Most of
+ them are reflections of the early stage of development and should be
+ treated as "not implemented yet", rather than actual limitations.
+
+ o During initial IPv4 node configuration, the server is expected to send
+ packets to a node that does not have IPv4 address assigned yet. The
+ server requires certain tricks (or hacks) to transmit such packets.
+ This is not implemented yet, therefore DHCPv4 server supports relayed
+ traffic only (that is, normal point to point communication).
+ o b10-dhcp4 provides a single, fixed, hardcoded lease to any client that
+ asks. There is no lease manager implemented. If two clients request
+ addresses, they will both get the same fixed address.
+ o b10-dhcp4 does not support any configuration mechanisms yet. The whole
+ configuration is currently hardcoded. The only way to tweak
+ configuration is to directly modify source code. See see Section 12.2,
+ "DHCPv4 Server Configuration" for details.
+ o Upon start, the server will open sockets on all interfaces that are
+ not loopback, are up and running and have IPv4 address. Support for
+ multiple interfaces is not coded in reception routines yet, so if you
+ are running this code on a machine that has many interfaces and
+ b10-dhcp4 happens to listen on wrong interface, the easiest way to
+ work around this problem is to turn down other interfaces. This
+ limitation will be fixed shortly.
+ o PRL (Parameter Request List, a list of options requested by a client)
+ is currently ignored and server assigns DNS SERVER and DOMAIN NAME
+ options.
+ o b10-dhcp4 does not support BOOTP. That is a design choice. This
+ limitation is permanent. If you have legacy nodes that can't use DHCP
+ and require BOOTP support, please use latest version of ISC DHCP
+ http://www.isc.org/software/dhcp.
+ o Interface detection is currently working on Linux only. See
+ Section 14.1, "Interface detection" for details.
+ o b10-dhcp4 does not verify that assigned address is unused. According
+ to RFC2131, the allocating server should verify that address is no
+ used by sending ICMP echo request.
+ o Address renewal (RENEW), rebinding (REBIND), confirmation (CONFIRM),
+ duplication report (DECLINE) and release (RELEASE) are not supported
+ yet.
+ o DNS Update is not supported yet.
+ o -v (verbose) command line option is currently the default, and cannot
+ be disabled.
+
+Chapter 13. DHCPv6 Server
+
+ Table of Contents
+
+ 13.1. DHCPv6 Server Usage
+
+ 13.2. DHCPv6 Server Configuration
+
+ 13.3. Supported DHCPv6 Standards
+
+ 13.4. DHCPv6 Server Limitations
+
+ Dynamic Host Configuration Protocol for IPv6 (DHCPv6) is specified in
+ RFC3315. BIND10 provides DHCPv6 server implementation that is described in
+ this chapter. For a description of the DHCPv4 server implementation, see
+ Chapter 12, DHCPv4 Server.
+
+ The DHCPv6 server component is currently under intense development. You
+ may want to check out BIND10 DHCP (Kea) wiki and recent posts on BIND10
+ developers mailing list.
+
+ The DHCPv4 and DHCPv6 components in BIND10 architecture are internally
+ code named "Kea".
+
+ Note
+
+ As of December 2011, both DHCPv4 and DHCPv6 components are skeleton
+ servers. That means that while they are capable of performing DHCP
+ configuration, they are not fully functional yet. In particular, neither
+ has functional lease databases. This means that they will assign the same,
+ fixed, hardcoded addresses to any client that will ask. See Section 12.4,
+ "DHCPv4 Server Limitations" and Section 13.4, "DHCPv6 Server Limitations"
+ for detailed description.
+
+13.1. DHCPv6 Server Usage
+
+ BIND10 provides the DHCPv6 server component since September 2011. It is a
+ skeleton server and can be described as an early prototype that is not
+ fully functional yet. It is mature enough to conduct first tests in lab
+ environment, but it has significant limitations. See Section 13.4, "DHCPv6
+ Server Limitations" for details.
+
+ The DHCPv6 server is implemented as b10-dhcp6 daemon. As it is not
+ configurable yet, it is fully autonomous, that is it does not interact
+ with b10-cfgmgr. To start DHCPv6 server, simply input:
+
+ #cd src/bin/dhcp6
+ #./b10-dhcp6
+
+ Depending on your installation, b10-dhcp6 binary may reside in
+ src/bin/dhcp6 in your source code directory, in /usr/local/bin/b10-dhcp6
+ or other directory you specified during compilation. At start, server will
+ detect available network interfaces and will attempt to open UDP sockets
+ on all interfaces that are up, running, are not loopback, are
+ multicast-capable, and have IPv6 address assigned. The server will then
+ listen to incoming traffic. Currently supported client messages are
+ SOLICIT and REQUEST. The server will respond to them with ADVERTISE and
+ REPLY, respectively. Since the DHCPv6 server opens privileged ports, it
+ requires root access. Make sure you run this daemon as root.
+
+ Note
+
+ Integration with bind10 is planned. Ultimately, b10-dhcp6 will not be
+ started directly, but rather via bind10. Please be aware of this planned
+ change.
+
+13.2. DHCPv6 Server Configuration
+
+ The DHCPv6 server does not have lease database implemented yet or any
+ support for configuration, so every time the same set of configuration
+ options (including the same fixed address) will be assigned every time.
+
+ At this stage of development, the only way to alter server configuration
+ is to tweak its source code. To do so, please edit
+ src/bin/dhcp6/dhcp6_srv.cc file and modify following parameters and
+ recompile:
+
+ const std::string HARDCODED_LEASE = "2001:db8:1::1234:abcd";
+ const uint32_t HARDCODED_T1 = 1500; // in seconds
+ const uint32_t HARDCODED_T2 = 2600; // in seconds
+ const uint32_t HARDCODED_PREFERRED_LIFETIME = 3600; // in seconds
+ const uint32_t HARDCODED_VALID_LIFETIME = 7200; // in seconds
+ const std::string HARDCODED_DNS_SERVER = "2001:db8:1::1";
+
+ Lease database and configuration support is planned for 2012.
+
+13.3. Supported DHCPv6 Standards
+
+ The following standards and draft standards are currently supported:
+
+ o RFC3315: Supported messages are SOLICIT, ADVERTISE, REQUEST, and
+ REPLY. Supported options are SERVER_ID, CLIENT_ID, IA_NA, and
+ IAADDRESS.
+ o RFC3646: Supported option is DNS_SERVERS.
+
+13.4. DHCPv6 Server Limitations
+
+ These are the current limitations of the DHCPv6 server software. Most of
+ them are reflections of the early stage of development and should be
+ treated as "not implemented yet", rather than actual limitations.
+
+ o Relayed traffic is not supported.
+ o b10-dhcp6 provides a single, fixed, hardcoded lease to any client that
+ asks. There is no lease manager implemented. If two clients request
+ addresses, they will both get the same fixed address.
+ o b10-dhcp6 does not support any configuration mechanisms yet. The whole
+ configuration is currently hardcoded. The only way to tweak
+ configuration is to directly modify source code. See see Section 13.2,
+ "DHCPv6 Server Configuration" for details.
+ o Upon start, the server will open sockets on all interfaces that are
+ not loopback, are up, running and are multicast capable and have IPv6
+ address. Support for multiple interfaces is not coded in reception
+ routines yet, so if you are running this code on a machine that has
+ many interfaces and b10-dhcp6 happens to listen on wrong interface,
+ the easiest way to work around this problem is to turn down other
+ interfaces. This limitation will be fixed shortly.
+ o ORO (Option Request Option, a list of options requested by a client)
+ is currently ignored and server assigns DNS SERVER option.
+ o Temporary addresses are not supported yet.
+ o Prefix delegation is not supported yet.
+ o Address renewal (RENEW), rebinding (REBIND), confirmation (CONFIRM),
+ duplication report (DECLINE) and release (RELEASE) are not supported
+ yet.
+ o DNS Update is not supported yet.
+ o Interface detection is currently working on Linux only. See
+ Section 14.1, "Interface detection" for details.
+ o -v (verbose) command line option is currently the default, and cannot
+ be disabled.
+
+Chapter 14. libdhcp++ library
+
+ Table of Contents
+
+ 14.1. Interface detection
+
+ 14.2. DHCPv4/DHCPv6 packet handling
+
+ libdhcp++ is a common library written in C++ that handles many
+ DHCP-related tasks, like DHCPv4 and DHCPv6 packets parsing, manipulation
+ and assembly, option parsing, manipulation and assembly, network interface
+ detection and socket operations, like socket creations, data transmission
+ and reception and socket closing.
+
+ While this library is currently used by b10-dhcp4 and b10-dhcp6 only, it
+ is designed to be portable, universal library useful for any kind of
+ DHCP-related software.
+
+14.1. Interface detection
+
+ Both DHCPv4 and DHCPv6 components share network interface detection
+ routines. Interface detection is currently only supported on Linux
+ systems.
+
+ For non-Linux systems, there is currently stub implementation provided. As
+ DHCP servers need to know available addresses, there is a simple mechanism
+ implemented to provide that information. User is expected to create
+ interfaces.txt file. Format of this file is simple. It contains list of
+ interfaces along with available address on each interface. This mechanism
+ is temporary and is going to be removed as soon as interface detection
+ becomes available on non-Linux systems. Here is an example of the
+ interfaces.txt file:
+
+ # For DHCPv6, please specify link-local address (starts with fe80::)
+ # If in doubt, check output of 'ifconfig -a' command.
+ eth0 fe80::21e:8cff:fe9b:7349
+
+ # For DHCPv4, please use following format:
+ #eth0 192.0.2.5
+
+14.2. DHCPv4/DHCPv6 packet handling
+
+ TODO: Describe packet handling here, with pointers to wiki
+
+Chapter 15. Statistics
The b10-stats process is started by bind10. It periodically collects
statistics data from various modules and aggregates it.
@@ -1031,27 +1392,27 @@ Chapter 13. Statistics
}
-Chapter 14. Logging
+Chapter 16. Logging
Table of Contents
- Logging configuration
+ 16.1. Logging configuration
- Loggers
+ 16.1.1. Loggers
- Output Options
+ 16.1.2. Output Options
- Example session
+ 16.1.3. Example session
- Logging Message Format
+ 16.2. Logging Message Format
-Logging configuration
+16.1. Logging configuration
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.
- Loggers
+ 16.1.1. Loggers
Within BIND 10, a message is logged through a component called a "logger".
Different parts of BIND 10 log messages through different loggers, and
@@ -1064,7 +1425,7 @@ Logging configuration
(the component that is generating the messages), the severity (what to
log), and the output_options (where to log).
- name (string)
+ 16.1.1.1. name (string)
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
@@ -1111,7 +1472,7 @@ Logging configuration
generated by the "Auth.cache" logger will appear in the output with a
logger name of "b10-auth.cache").
- severity (string)
+ 16.1.1.2. severity (string)
This specifies the category of messages logged. Each message is logged
with an associated severity which may be one of the following (in
@@ -1128,14 +1489,14 @@ Logging configuration
may also be set to NONE, in which case all messages from that logger are
inhibited.
- output_options (list)
+ 16.1.1.3. output_options (list)
Each logger can have zero or more output_options. These specify where log
messages are sent to. These are explained in detail below.
The other options for a logger are:
- debuglevel (integer)
+ 16.1.1.4. debuglevel (integer)
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
@@ -1143,7 +1504,7 @@ Logging configuration
If severity for the logger is not DEBUG, this value is ignored.
- additive (true or false)
+ 16.1.1.5. additive (true or false)
If this is true, the output_options from the parent will be used. For
example, if there are two loggers configured; "Resolver" and
@@ -1152,13 +1513,13 @@ Logging configuration
but also to the destinations as specified in the output_options in the
logger named "Resolver".
- Output Options
+ 16.1.2. Output Options
The main settings for an output option are the destination and a value
called output, the meaning of which depends on the destination that is
set.
- destination (string)
+ 16.1.2.1. destination (string)
The destination is the type of output. It can be one of:
@@ -1166,7 +1527,7 @@ Logging configuration
o file
o syslog
- output (string)
+ 16.1.2.2. output (string)
Depending on what is set as the output destination, this value is
interpreted as follows:
@@ -1185,13 +1546,13 @@ Logging configuration
The other options for output_options are:
- flush (true of false)
+ 16.1.2.2.1. flush (true of false)
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.
- maxsize (integer)
+ 16.1.2.2.2. maxsize (integer)
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
@@ -1200,12 +1561,12 @@ Logging configuration
If this is 0, no maximum file size is used.
- maxver (integer)
+ 16.1.2.2.3. maxver (integer)
Maximum number of old log files to keep around when rolling the output
file. Only relevant when destination is "file".
- Example session
+ 16.1.3. Example session
In this example we want to set the global logging to write to the file
/var/log/my_bind10.log, at severity WARN. We want the authoritative server
@@ -1306,7 +1667,7 @@ Logging configuration
And every module will now be using the values from the logger named "*".
-Logging Message Format
+16.2. Logging Message Format
Each message written by BIND 10 to the configured logging destinations
comprises a number of components that identify the origin of the message
diff --git a/doc/guide/bind10-messages.html b/doc/guide/bind10-messages.html
index f2f57f1..596cb53 100644
--- a/doc/guide/bind10-messages.html
+++ b/doc/guide/bind10-messages.html
@@ -1,10 +1,10 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>BIND 10 Messages Manual</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 messages manual for BIND 10 version 20111021. 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 Messages Manual"><div class="titlepage"><div><div><h1 class="title"><a name="id1168229451102"></a>BIND 10 Messages Manual</h1></div><div><p class="releaseinfo">This is the messages manual for BIND 10 version
- 20111021.</p></div><div><p class="copyright">Copyright © 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 Messages Manual</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 messages manual for BIND 10 version 20111129. 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 Messages Manual"><div class="titlepage"><div><div><h1 class="title"><a name="id1168229451102"></a>BIND 10 Messages Manual</h1></div><div><p class="releaseinfo">This is the messages manual for BIND 10 version
+ 20111129.</p></div><div><p class="copyright">Copyright © 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 messages manual for BIND 10 version 20111021.
+ This is the messages manual for BIND 10 version 20111129.
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>.
@@ -26,7 +26,13 @@
For information on configuring and using BIND 10 logging,
refer to the <a class="ulink" href="bind10-guide.html" target="_top">BIND 10 Guide</a>.
</p></div><div class="chapter" title="Chapter 2. BIND 10 Messages"><div class="titlepage"><div><div><h2 class="title"><a name="messages"></a>Chapter 2. BIND 10 Messages</h2></div></div></div><p>
- </p><div class="variablelist"><dl><dt><a name="ASIODNS_FETCH_COMPLETED"></a><span class="term">ASIODNS_FETCH_COMPLETED upstream fetch to %1(%2) has now completed</span></dt><dd><p>
+ </p><div class="variablelist"><dl><dt><a name="ASIODNS_FD_ADD_TCP"></a><span class="term">ASIODNS_FD_ADD_TCP adding a new TCP server by opened fd %1</span></dt><dd><p>
+A debug message informing about installing a file descriptor as a server.
+The file descriptor number is noted.
+</p></dd><dt><a name="ASIODNS_FD_ADD_UDP"></a><span class="term">ASIODNS_FD_ADD_UDP adding a new UDP server by opened fd %1</span></dt><dd><p>
+A debug message informing about installing a file descriptor as a server.
+The file descriptor number is noted.
+</p></dd><dt><a name="ASIODNS_FETCH_COMPLETED"></a><span class="term">ASIODNS_FETCH_COMPLETED upstream fetch to %1(%2) has now completed</span></dt><dd><p>
A debug message, this records that the upstream fetch (a query made by the
resolver on behalf of its client) to the specified address has completed.
</p></dd><dt><a name="ASIODNS_FETCH_STOPPED"></a><span class="term">ASIODNS_FETCH_STOPPED upstream fetch to %1(%2) has been stopped</span></dt><dd><p>
@@ -328,6 +334,11 @@ during startup, and will now kill the processes that did get started.
The boss module is sending a kill signal to process with the given name,
as part of the process of killing all started processes during a failed
startup, as described for BIND10_KILLING_ALL_PROCESSES
+</p></dd><dt><a name="BIND10_LOST_SOCKET_CONSUMER"></a><span class="term">BIND10_LOST_SOCKET_CONSUMER consumer %1 of sockets disconnected, considering all its sockets closed</span></dt><dd><p>
+A connection from one of the applications which requested a socket was
+closed. This means the application has terminated, so all the sockets it was
+using are now closed and bind10 process can release them as well, unless the
+same sockets are used by yet another application.
</p></dd><dt><a name="BIND10_MSGQ_ALREADY_RUNNING"></a><span class="term">BIND10_MSGQ_ALREADY_RUNNING msgq daemon already running, cannot start</span></dt><dd><p>
There already appears to be a message bus daemon running. Either an
old process was not shut down correctly, and needs to be killed, or
@@ -337,6 +348,10 @@ running, which needs to be stopped.
While listening on the message bus channel for messages, it suddenly
disappeared. The msgq daemon may have died. This might lead to an
inconsistent state of the system, and BIND 10 will now shut down.
+</p></dd><dt><a name="BIND10_NO_SOCKET"></a><span class="term">BIND10_NO_SOCKET couldn't send a socket for token %1 because of error: %2</span></dt><dd><p>
+An error occurred when the bind10 process was asked to send a socket file
+descriptor. The error is mentioned, most common reason is that the request
+is invalid and may not come from bind10 process at all.
</p></dd><dt><a name="BIND10_PROCESS_ENDED"></a><span class="term">BIND10_PROCESS_ENDED process %2 of %1 ended with status %3</span></dt><dd><p>
This indicates a process started previously terminated. The process id
and component owning the process are indicated, as well as the exit code.
@@ -830,7 +845,7 @@ means no limit.
The datasource tried to provide an NSEC proof that the named domain does not
exist, but the database backend doesn't support DNSSEC. No proof is included
in the answer as a result.
-</p></dd><dt><a name="DATASRC_DATABASE_FIND_RECORDS"></a><span class="term">DATASRC_DATABASE_FIND_RECORDS looking in datasource %1 for record %2/%3</span></dt><dd><p>
+</p></dd><dt><a name="DATASRC_DATABASE_FIND_RECORDS"></a><span class="term">DATASRC_DATABASE_FIND_RECORDS looking in datasource %1 for record %2/%3/%4</span></dt><dd><p>
Debug information. The database data source is looking up records with the given
name and type in the database.
</p></dd><dt><a name="DATASRC_DATABASE_FIND_TTL_MISMATCH"></a><span class="term">DATASRC_DATABASE_FIND_TTL_MISMATCH TTL values differ in %1 for elements of %2/%3/%4, setting to %5</span></dt><dd><p>
@@ -838,10 +853,18 @@ The datasource backend provided resource records for the given RRset with
different TTL values. This isn't allowed on the wire and is considered
an error, so we set it to the lowest value we found (but we don't modify the
database). The data in database should be checked and fixed.
+</p></dd><dt><a name="DATASRC_DATABASE_FOUND_ANY"></a><span class="term">DATASRC_DATABASE_FOUND_ANY search in datasource %1 resulted in returning all records of %2</span></dt><dd><p>
+The data returned by the database backend contained data for the given domain
+name, so all the RRsets of the domain are returned.
+</p></dd><dt><a name="DATASRC_DATABASE_FOUND_CNAME"></a><span class="term">DATASRC_DATABASE_FOUND_CNAME search in datasource %1 for %2/%3/%4 found CNAME, resulting in %5</span></dt><dd><p>
+When searching the domain for a name a CNAME was found at that name.
+Even though it was not the RR type being sought, it is returned. (The
+caller may want to continue the lookup by replacing the query name with
+the canonical name and restarting the query with the original RR type.)
</p></dd><dt><a name="DATASRC_DATABASE_FOUND_DELEGATION"></a><span class="term">DATASRC_DATABASE_FOUND_DELEGATION Found delegation at %2 in %1</span></dt><dd><p>
When searching for a domain, the program met a delegation to a different zone
at the given domain name. It will return that one instead.
-</p></dd><dt><a name="DATASRC_DATABASE_FOUND_DELEGATION_EXACT"></a><span class="term">DATASRC_DATABASE_FOUND_DELEGATION_EXACT Found delegation at %2 (exact match) in %1</span></dt><dd><p>
+</p></dd><dt><a name="DATASRC_DATABASE_FOUND_DELEGATION_EXACT"></a><span class="term">DATASRC_DATABASE_FOUND_DELEGATION_EXACT search in datasource %1 for %2/%3/%4 found delegation at %5</span></dt><dd><p>
The program found the domain requested, but it is a delegation point to a
different zone, therefore it is not authoritative for this domain name.
It will return the NS record instead.
@@ -850,16 +873,21 @@ When searching for a domain, the program met a DNAME redirection to a different
place in the domain space at the given domain name. It will return that one
instead.
</p></dd><dt><a name="DATASRC_DATABASE_FOUND_EMPTY_NONTERMINAL"></a><span class="term">DATASRC_DATABASE_FOUND_EMPTY_NONTERMINAL empty non-terminal %2 in %1</span></dt><dd><p>
-The domain name doesn't have any RRs, so it doesn't exist in the database.
-However, it has a subdomain, so it exists in the DNS address space. So we
-return NXRRSET instead of NXDOMAIN.
+The domain name does not have any RRs associated with it, so it doesn't
+exist in the database. However, it has a subdomain, so it does exist
+in the DNS address space. This type of domain is known an an "empty
+non-terminal" and so we return NXRRSET instead of NXDOMAIN.
</p></dd><dt><a name="DATASRC_DATABASE_FOUND_NXDOMAIN"></a><span class="term">DATASRC_DATABASE_FOUND_NXDOMAIN search in datasource %1 resulted in NXDOMAIN for %2/%3/%4</span></dt><dd><p>
The data returned by the database backend did not contain any data for the given
domain name, class and type.
-</p></dd><dt><a name="DATASRC_DATABASE_FOUND_NXRRSET"></a><span class="term">DATASRC_DATABASE_FOUND_NXRRSET search in datasource %1 resulted in NXRRSET for %2/%3/%4</span></dt><dd><p>
+</p></dd><dt><a name="DATASRC_DATABASE_FOUND_NXRRSET"></a><span class="term">DATASRC_DATABASE_FOUND_NXRRSET search in datasource %1 for %2/%3/%4 resulted in NXRRSET</span></dt><dd><p>
The data returned by the database backend contained data for the given domain
name and class, but not for the given type.
-</p></dd><dt><a name="DATASRC_DATABASE_FOUND_RRSET"></a><span class="term">DATASRC_DATABASE_FOUND_RRSET search in datasource %1 resulted in RRset %2</span></dt><dd><p>
+</p></dd><dt><a name="DATASRC_DATABASE_FOUND_NXRRSET_NSEC"></a><span class="term">DATASRC_DATABASE_FOUND_NXRRSET_NSEC search in datasource %1 for %2/%3/%4 resulted in RRset %5</span></dt><dd><p>
+A search in the database for RRs for the specified name, type and class has
+located RRs that match the name and class but not the type. DNSSEC information
+has been requested and returned.
+</p></dd><dt><a name="DATASRC_DATABASE_FOUND_RRSET"></a><span class="term">DATASRC_DATABASE_FOUND_RRSET search in datasource %1 resulted in RRset %5</span></dt><dd><p>
The data returned by the database backend contained data for the given domain
name, and it either matches the type or has a relevant type. The RRset that is
returned is printed.
@@ -900,17 +928,31 @@ The zone's name and class, database name, and the start and end
serials, and an additional detail of the error are shown in the
message. The administrator should examine the diff in the database
to find any invalid data and fix it.
+</p></dd><dt><a name="DATASRC_DATABASE_NO_MATCH"></a><span class="term">DATASRC_DATABASE_NO_MATCH not match for %2/%3/%4 in %1</span></dt><dd><p>
+No match (not even a wildcard) was found in the named data source for the given
+name/type/class in the data source.
</p></dd><dt><a name="DATASRC_DATABASE_UPDATER_COMMIT"></a><span class="term">DATASRC_DATABASE_UPDATER_COMMIT updates committed for '%1/%2' on %3</span></dt><dd><p>
Debug information. A set of updates to a zone has been successfully
committed to the corresponding database backend. The zone name,
its class and the database name are printed.
+</p></dd><dt><a name="DATASRC_DATABASE_UPDATER_COMMIT%20(1)"></a><span class="term">DATASRC_DATABASE_UPDATER_COMMIT (1) updates committed for '%1/%2' on %3</span></dt><dd><p>
+Debug information. A set of updates to a zone has been successfully
+committed to the corresponding database backend. The zone name,
+its class and the database name are printed.
</p></dd><dt><a name="DATASRC_DATABASE_UPDATER_CREATED"></a><span class="term">DATASRC_DATABASE_UPDATER_CREATED zone updater created for '%1/%2' on %3</span></dt><dd><p>
Debug information. A zone updater object is created to make updates to
the shown zone on the shown backend database.
+</p></dd><dt><a name="DATASRC_DATABASE_UPDATER_CREATED%20(1)"></a><span class="term">DATASRC_DATABASE_UPDATER_CREATED (1) zone updater created for '%1/%2' on %3</span></dt><dd><p>
+Debug information. A zone updater object is created to make updates to
+the shown zone on the shown backend database.
</p></dd><dt><a name="DATASRC_DATABASE_UPDATER_DESTROYED"></a><span class="term">DATASRC_DATABASE_UPDATER_DESTROYED zone updater destroyed for '%1/%2' on %3</span></dt><dd><p>
Debug information. A zone updater object is destroyed, either successfully
or after failure of, making updates to the shown zone on the shown backend
database.
+</p></dd><dt><a name="DATASRC_DATABASE_UPDATER_DESTROYED%20(1)"></a><span class="term">DATASRC_DATABASE_UPDATER_DESTROYED (1) zone updater destroyed for '%1/%2' on %3</span></dt><dd><p>
+Debug information. A zone updater object is destroyed, either successfully
+or after failure of, making updates to the shown zone on the shown backend
+database.
</p></dd><dt><a name="DATASRC_DATABASE_UPDATER_ROLLBACK"></a><span class="term">DATASRC_DATABASE_UPDATER_ROLLBACK zone updates roll-backed for '%1/%2' on %3</span></dt><dd><p>
A zone updater is being destroyed without committing the changes.
This would typically mean the update attempt was aborted due to some
@@ -918,6 +960,13 @@ error, but may also be a bug of the application that forgets committing
the changes. The intermediate changes made through the updater won't
be applied to the underlying database. The zone name, its class, and
the underlying database name are shown in the log message.
+</p></dd><dt><a name="DATASRC_DATABASE_UPDATER_ROLLBACK%20(1)"></a><span class="term">DATASRC_DATABASE_UPDATER_ROLLBACK (1) zone updates roll-backed for '%1/%2' on %3</span></dt><dd><p>
+A zone updater is being destroyed without committing the changes.
+This would typically mean the update attempt was aborted due to some
+error, but may also be a bug of the application that forgets committing
+the changes. The intermediate changes made through the updater won't
+be applied to the underlying database. The zone name, its class, and
+the underlying database name are shown in the log message.
</p></dd><dt><a name="DATASRC_DATABASE_UPDATER_ROLLBACKFAIL"></a><span class="term">DATASRC_DATABASE_UPDATER_ROLLBACKFAIL failed to roll back zone updates for '%1/%2' on %3: %4</span></dt><dd><p>
A zone updater is being destroyed without committing the changes to
the database, and attempts to rollback incomplete updates, but it
@@ -930,10 +979,23 @@ examine the underlying data source to see what exactly happens and
whether the data is still valid. The zone name, its class, and the
underlying database name as well as the error message thrown from the
database module are shown in the log message.
-</p></dd><dt><a name="DATASRC_DATABASE_WILDCARD"></a><span class="term">DATASRC_DATABASE_WILDCARD constructing RRset %3 from wildcard %2 in %1</span></dt><dd><p>
-The database doesn't contain directly matching domain, but it does contain a
-wildcard one which is being used to synthesize the answer.
-</p></dd><dt><a name="DATASRC_DATABASE_WILDCARD_CANCEL_NS"></a><span class="term">DATASRC_DATABASE_WILDCARD_CANCEL_NS canceled wildcard match on %2 because %3 contains NS in %1</span></dt><dd><p>
+</p></dd><dt><a name="DATASRC_DATABASE_UPDATER_ROLLBACKFAIL%20(1)"></a><span class="term">DATASRC_DATABASE_UPDATER_ROLLBACKFAIL (1) failed to roll back zone updates for '%1/%2' on %3: %4</span></dt><dd><p>
+A zone updater is being destroyed without committing the changes to
+the database, and attempts to rollback incomplete updates, but it
+unexpectedly fails. The higher level implementation does not expect
+it to fail, so this means either a serious operational error in the
+underlying data source (such as a system failure of a database) or
+software bug in the underlying data source implementation. In either
+case if this message is logged the administrator should carefully
+examine the underlying data source to see what exactly happens and
+whether the data is still valid. The zone name, its class, and the
+underlying database name as well as the error message thrown from the
+database module are shown in the log message.
+</p></dd><dt><a name="DATASRC_DATABASE_WILDCARD_ANY"></a><span class="term">DATASRC_DATABASE_WILDCARD_ANY search in datasource %1 resulted in wildcard match type ANY on %2</span></dt><dd><p>
+The database doesn't contain directly matching name. When searching
+for a wildcard match, a wildcard record matching the name of the query
+containing some RRsets was found. All the RRsets of the node are returned.
+</p></dd><dt><a name="DATASRC_DATABASE_WILDCARD_CANCEL_NS"></a><span class="term">DATASRC_DATABASE_WILDCARD_CANCEL_NS canceled wildcard match on %3 because %2 contains NS (data source %1)</span></dt><dd><p>
The database was queried to provide glue data and it didn't find direct match.
It could create it from given wildcard, but matching wildcards is forbidden
under a zone cut, which was found. Therefore the delegation will be returned
@@ -943,11 +1005,27 @@ The answer could be constructed using the wildcard, but the given subdomain
exists, therefore this name is something like empty non-terminal (actually,
from the protocol point of view, it is empty non-terminal, but the code
discovers it differently).
-</p></dd><dt><a name="DATASRC_DATABASE_WILDCARD_EMPTY"></a><span class="term">DATASRC_DATABASE_WILDCARD_EMPTY implicit wildcard %2 used to construct %3 in %1</span></dt><dd><p>
-The given wildcard exists implicitly in the domainspace, as empty nonterminal
-(eg. there's something like subdomain.*.example.org, so *.example.org exists
-implicitly, but is empty). This will produce NXRRSET, because the constructed
-domain is empty as well as the wildcard.
+</p></dd><dt><a name="DATASRC_DATABASE_WILDCARD_CNAME"></a><span class="term">DATASRC_DATABASE_WILDCARD_CNAME search in datasource %1 for %2/%3/%4 found wildcard CNAME at %5, resulting in %6</span></dt><dd><p>
+The database doesn't contain directly matching name. When searching
+for a wildcard match, a CNAME RR was found at a wildcard record
+matching the name. This is returned as the result of the search.
+</p></dd><dt><a name="DATASRC_DATABASE_WILDCARD_EMPTY"></a><span class="term">DATASRC_DATABASE_WILDCARD_EMPTY found subdomains of %2 which is a wildcard match for %3 in %1</span></dt><dd><p>
+The given wildcard matches the name being sough but it as an empty
+nonterminal (e.g. there's nothing at *.example.com but something like
+subdomain.*.example.org, do exist: so *.example.org exists in the
+namespace but has no RRs assopciated with it). This will produce NXRRSET.
+</p></dd><dt><a name="DATASRC_DATABASE_WILDCARD_MATCH"></a><span class="term">DATASRC_DATABASE_WILDCARD_MATCH search in datasource %1 resulted in wildcard match at %5 with RRset %6</span></dt><dd><p>
+The database doesn't contain directly matching name. When searching
+for a wildcard match, a wildcard record matching the name and type of
+the query was found. The data at this point is returned.
+</p></dd><dt><a name="DATASRC_DATABASE_WILDCARD_NS"></a><span class="term">DATASRC_DATABASE_WILDCARD_NS search in datasource %1 for %2/%3/%4 found wildcard delegation at %5, resulting in %6</span></dt><dd><p>
+The database doesn't contain directly matching name. When searching
+for a wildcard match, an NS RR was found at a wildcard record matching
+the name. This is returned as the result of the search.
+</p></dd><dt><a name="DATASRC_DATABASE_WILDCARD_NXRRSET"></a><span class="term">DATASRC_DATABASE_WILDCARD_NXRRSET search in datasource %1 for %2/%3/%4 resulted in wildcard NXRRSET at %5</span></dt><dd><p>
+The database doesn't contain directly matching name. When searching
+for a wildcard match, a matching wildcard entry was found but it did
+not contain RRs the requested type. AN NXRRSET indication is returned.
</p></dd><dt><a name="DATASRC_DO_QUERY"></a><span class="term">DATASRC_DO_QUERY handling query for '%1/%2'</span></dt><dd><p>
A debug message indicating that a query for the given name and RR type is being
processed.
@@ -1031,7 +1109,7 @@ Some resource types are singletons -- only one is allowed in a domain
Debug information. The requested record was found.
</p></dd><dt><a name="DATASRC_MEM_SUPER_STOP"></a><span class="term">DATASRC_MEM_SUPER_STOP stopped at superdomain '%1', domain '%2' is empty</span></dt><dd><p>
Debug information. The search stopped at a superdomain of the requested
-domain. The domain is a empty nonterminal, therefore it is treated as NXRRSET
+domain. The domain is an empty nonterminal, therefore it is treated as NXRRSET
case (eg. the domain exists, but it doesn't have the requested record type).
</p></dd><dt><a name="DATASRC_MEM_SWAP"></a><span class="term">DATASRC_MEM_SWAP swapping contents of two zone representations ('%1' and '%2')</span></dt><dd><p>
Debug information. The contents of two in-memory zones are being exchanged.
@@ -1287,10 +1365,46 @@ data source.
</p></dd><dt><a name="DATASRC_UNEXPECTED_QUERY_STATE"></a><span class="term">DATASRC_UNEXPECTED_QUERY_STATE unexpected query state</span></dt><dd><p>
This indicates a programming error. An internal task of unknown type was
generated.
-</p></dd><dt><a name="LIBXFRIN_DIFFERENT_TTL"></a><span class="term">LIBXFRIN_DIFFERENT_TTL multiple data with different TTLs (%1, %2) on %3/%4. Adjusting %2 -> %1.</span></dt><dd><p>
+</p></dd><dt><a name="DDNS_CC_SESSION_ERROR"></a><span class="term">DDNS_CC_SESSION_ERROR error reading from cc channel: %1</span></dt><dd><p>
+There was a problem reading from the command and control channel. The
+most likely cause is that the msgq process is not running.
+</p></dd><dt><a name="DDNS_CC_SESSION_TIMEOUT_ERROR"></a><span class="term">DDNS_CC_SESSION_TIMEOUT_ERROR timeout waiting for cc response</span></dt><dd><p>
+There was a problem reading a response from another module over the
+command and control channel. The most likely cause is that the
+configuration manager b10-cfgmgr is not running.
+</p></dd><dt><a name="DDNS_CONFIG_ERROR"></a><span class="term">DDNS_CONFIG_ERROR error found in configuration data: %1</span></dt><dd><p>
+The ddns process encountered an error when installing the configuration at
+startup time. Details of the error are included in the log message.
+</p></dd><dt><a name="DDNS_MODULECC_SESSION_ERROR"></a><span class="term">DDNS_MODULECC_SESSION_ERROR error encountered by configuration/command module: %1</span></dt><dd><p>
+There was a problem in the lower level module handling configuration and
+control commands. This could happen for various reasons, but the most likely
+cause is that the configuration database contains a syntax error and ddns
+failed to start at initialization. A detailed error message from the module
+will also be displayed.
+</p></dd><dt><a name="DDNS_RECEIVED_SHUTDOWN_COMMAND"></a><span class="term">DDNS_RECEIVED_SHUTDOWN_COMMAND shutdown command received</span></dt><dd><p>
+The ddns process received a shutdown command from the command channel
+and will now shut down.
+</p></dd><dt><a name="DDNS_RUNNING"></a><span class="term">DDNS_RUNNING ddns server is running and listening for updates</span></dt><dd><p>
+The ddns process has successfully started and is now ready to receive commands
+and updates.
+</p></dd><dt><a name="DDNS_SHUTDOWN"></a><span class="term">DDNS_SHUTDOWN ddns server shutting down</span></dt><dd><p>
+The ddns process is shutting down. It will no longer listen for new commands
+or updates. Any command or update that is being addressed at this moment will
+be completed, after which the process will exit.
+</p></dd><dt><a name="DDNS_STOPPED"></a><span class="term">DDNS_STOPPED ddns server has stopped</span></dt><dd><p>
+The ddns process has successfully stopped and is no longer listening for or
+handling commands or updates, and will now exit.
+</p></dd><dt><a name="DDNS_STOPPED_BY_KEYBOARD"></a><span class="term">DDNS_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down</span></dt><dd><p>
+There was a keyboard interrupt signal to stop the ddns process. The
+process will now shut down.
+</p></dd><dt><a name="DDNS_UNCAUGHT_EXCEPTION"></a><span class="term">DDNS_UNCAUGHT_EXCEPTION uncaught exception of type %1: %2</span></dt><dd><p>
+The b10-ddns process encountered an uncaught exception and will now shut
+down. This is indicative of a programming error and should not happen under
+normal circumstances. The exception type and message are printed.
+</p></dd><dt><a name="LIBXFRIN_DIFFERENT_TTL"></a><span class="term">LIBXFRIN_DIFFERENT_TTL multiple data with different TTLs (%1, %2) on %3/%4/%5. Adjusting %2 -> %1.</span></dt><dd><p>
The xfrin module received an update containing multiple rdata changes for the
same RRset. But the TTLs of these don't match each other. As we combine them
-together, the later one get's overwritten to the earlier one in the sequence.
+together, the latter one gets overwritten to the earlier one in the sequence.
</p></dd><dt><a name="LIBXFRIN_NO_JOURNAL"></a><span class="term">LIBXFRIN_NO_JOURNAL disabled journaling for updates to %1 on %2</span></dt><dd><p>
An attempt was made to create a Diff object with journaling enabled, but
the underlying data source didn't support journaling (while still allowing
@@ -1494,6 +1608,14 @@ be sent to such a zone.
</p></dd><dt><a name="NOTIFY_OUT_ZONE_NO_NS"></a><span class="term">NOTIFY_OUT_ZONE_NO_NS Zone %1 doesn't have NS RR</span></dt><dd><p>
This is a warning issued when the notify_out module finds a zone that
doesn't have an NS RR. Notify message won't be sent to such a zone.
+</p></dd><dt><a name="NSAS_EMPTY_RESPONSE"></a><span class="term">NSAS_EMPTY_RESPONSE response to query for %1 returned an empty answer section</span></dt><dd><p>
+The NSAS (nameserver address store - part of the resolver) made a query
+for information it needed. The query completed successfully but the
+answer section in the response was empty.
+</p></dd><dt><a name="NSAS_ERROR_RESPONSE"></a><span class="term">NSAS_ERROR_RESPONSE error response of %1 returned in query for %2</span></dt><dd><p>
+The NSAS (nameserver address store - part of the resolver) made a query
+for information it needed. The query completed successfully but the
+RCODE in the response was something other than NOERROR.
</p></dd><dt><a name="NSAS_FIND_NS_ADDRESS"></a><span class="term">NSAS_FIND_NS_ADDRESS asking resolver to obtain A and AAAA records for %1</span></dt><dd><p>
A debug message issued when the NSAS (nameserver address store - part
of the resolver) is making a callback into the resolver to retrieve the
@@ -1502,16 +1624,6 @@ address records for the specified nameserver.
A debug message issued when the NSAS (nameserver address store - part
of the resolver) has retrieved the given address for the specified
nameserver through an external query.
-</p></dd><dt><a name="NSAS_INVALID_RESPONSE"></a><span class="term">NSAS_INVALID_RESPONSE queried for %1 but got invalid response</span></dt><dd><p>
-The NSAS (nameserver address store - part of the resolver) made a query
-for a RR for the specified nameserver but received an invalid response.
-Either the success function was called without a DNS message or the
-message was invalid on some way. (In the latter case, the error should
-have been picked up elsewhere in the processing logic, hence the raising
-of the error here.)
-</p><p>
-This message indicates an internal error in the NSAS. Please raise a
-bug report.
</p></dd><dt><a name="NSAS_LOOKUP_CANCEL"></a><span class="term">NSAS_LOOKUP_CANCEL lookup for zone %1 has been canceled</span></dt><dd><p>
A debug message issued when an NSAS (nameserver address store - part of
the resolver) lookup for a zone has been canceled.
@@ -1521,6 +1633,13 @@ the resolver) has been unable to retrieve the specified resource record
for the specified nameserver. This is not necessarily a problem - the
nameserver may be unreachable, in which case the NSAS will try other
nameservers in the zone.
+</p></dd><dt><a name="NSAS_NULL_RESPONSE"></a><span class="term">NSAS_NULL_RESPONSE got null message in success callback for query for %1</span></dt><dd><p>
+The NSAS (nameserver address store - part of the resolver) made a query
+for information it needed. The query completed successfully, but the
+message passed to the callback was null.
+</p><p>
+This message indicates an internal error in the NSAS. Please raise a
+bug report.
</p></dd><dt><a name="NSAS_SEARCH_ZONE_NS"></a><span class="term">NSAS_SEARCH_ZONE_NS searching NSAS for nameservers for zone %1</span></dt><dd><p>
A debug message output when a call is made to the NSAS (nameserver
address store - part of the resolver) to obtain the nameservers for
@@ -1541,25 +1660,78 @@ an answer with a different given type and class.
This message indicates an internal error in the NSAS. Please raise a
bug report.
</p></dd><dt><a name="RESLIB_ANSWER"></a><span class="term">RESLIB_ANSWER answer received in response to query for <%1></span></dt><dd><p>
-A debug message recording that an answer has been received to an upstream
-query for the specified question. Previous debug messages will have indicated
-the server to which the question was sent.
+A debug message reporting that an answer has been received to an upstream
+query for the specified question. Previous debug messages will have
+indicated the server to which the question was sent.
</p></dd><dt><a name="RESLIB_CNAME"></a><span class="term">RESLIB_CNAME CNAME received in response to query for <%1></span></dt><dd><p>
-A debug message recording that CNAME response has been received to an upstream
-query for the specified question. Previous debug messages will have indicated
-the server to which the question was sent.
+A debug message recording that CNAME response has been received to an
+upstream query for the specified question. Previous debug messages will
+have indicated the server to which the question was sent.
</p></dd><dt><a name="RESLIB_DEEPEST"></a><span class="term">RESLIB_DEEPEST did not find <%1> in cache, deepest delegation found is %2</span></dt><dd><p>
-A debug message, a cache lookup did not find the specified <name, class,
-type> tuple in the cache; instead, the deepest delegation found is indicated.
+A debug message, a cache lookup did not find the specified <name,
+class, type> tuple in the cache; instead, the deepest delegation found
+is indicated.
+</p></dd><dt><a name="RESLIB_EMPTY_RESPONSE"></a><span class="term">RESLIB_EMPTY_RESPONSE empty response received to query for <%1></span></dt><dd><p>
+A debug message, the response to the specified query from an upstream
+nameserver did not contain anything in the answer or authority sections,
+although in all other respects it was a valid response. A SERVFAIL will
+be returned to the system making the original query.
+</p></dd><dt><a name="RESLIB_ERROR_RESPONSE"></a><span class="term">RESLIB_ERROR_RESPONSE unspecified error received in response to query for <%1></span></dt><dd><p>
+A debug message, the response to the specified query to an upstream
+nameserver indicated that the response was classified as an erroneous
+response, but that the nature of the error cannot be identified.
+A SERVFAIL will be returned to the system making the original query.
+</p></dd><dt><a name="RESLIB_EXTRADATA_RESPONSE"></a><span class="term">RESLIB_EXTRADATA_RESPONSE extra data in response to query for <%1></span></dt><dd><p>
+A debug message indicating that the response to the specified query
+from an upstream nameserver contained too much data. This can happen if
+an ANY query was sent and the answer section in the response contained
+multiple RRs with different names. A SERVFAIL will be returned to the
+system making the original query.
</p></dd><dt><a name="RESLIB_FOLLOW_CNAME"></a><span class="term">RESLIB_FOLLOW_CNAME following CNAME chain to <%1></span></dt><dd><p>
-A debug message, a CNAME response was received and another query is being issued
-for the <name, class, type> tuple.
+A debug message, a CNAME response was received and another query is
+being issued for the <name, class, type> tuple.
+</p></dd><dt><a name="RESLIB_INVALID_NAMECLASS_RESPONSE"></a><span class="term">RESLIB_INVALID_NAMECLASS_RESPONSE invalid name or class in response to query for <%1></span></dt><dd><p>
+A debug message, the response to the specified query from an upstream
+nameserver (as identified by the ID of the response) contained either
+an answer not matching the query name or an answer having a different
+class to that queried for. A SERVFAIL will be returned to the system
+making the original query.
+</p></dd><dt><a name="RESLIB_INVALID_QNAME_RESPONSE"></a><span class="term">RESLIB_INVALID_QNAME_RESPONSE invalid name or class in response to query for <%1></span></dt><dd><p>
+A debug message, the response to the specified query from an upstream
+nameserver (as identified by the ID of the response) contained a name
+in the question section that did not match that of the query. A SERVFAIL
+will be returned to the system making the original query.
+</p></dd><dt><a name="RESLIB_INVALID_TYPE_RESPONSE"></a><span class="term">RESLIB_INVALID_TYPE_RESPONSE invalid name or class in response to query for <%1></span></dt><dd><p>
+A debug message, the response to the specified query from an upstream
+nameserver (as identified by the ID of the response) contained an
+invalid type field. A SERVFAIL will be returned to the system making
+the original query.
</p></dd><dt><a name="RESLIB_LONG_CHAIN"></a><span class="term">RESLIB_LONG_CHAIN CNAME received in response to query for <%1>: CNAME chain length exceeded</span></dt><dd><p>
A debug message recording that a CNAME response has been received to an upstream
query for the specified question (Previous debug messages will have indicated
the server to which the question was sent). However, receipt of this CNAME
has meant that the resolver has exceeded the CNAME chain limit (a CNAME chain
is where on CNAME points to another) and so an error is being returned.
+</p></dd><dt><a name="RESLIB_MULTIPLE_CLASS_RESPONSE"></a><span class="term">RESLIB_MULTIPLE_CLASS_RESPONSE response to query for <%1> contained multiple RRsets with different classes</span></dt><dd><p>
+A debug message reporting that the response to an upstream query for
+the specified name contained multiple RRsets in the answer and not all
+were of the same class. This is a violation of the standard and so a
+SERVFAIL will be returned.
+</p></dd><dt><a name="RESLIB_NOTSINGLE_RESPONSE"></a><span class="term">RESLIB_NOTSINGLE_RESPONSE response to query for <%1> was not a response</span></dt><dd><p>
+A debug message, the response to the specified query from an upstream
+nameserver was a CNAME that had mutiple RRs in the RRset. This is
+an invalid response according to the standards so a SERVFAIL will be
+returned to the system making the original query.
+</p></dd><dt><a name="RESLIB_NOT_ONE_QNAME_RESPONSE"></a><span class="term">RESLIB_NOT_ONE_QNAME_RESPONSE not one question in response to query for <%1></span></dt><dd><p>
+A debug message, the response to the specified query from an upstream
+nameserver (as identified by the ID of the response) did not contain
+one name in the question section as required by the standard. A SERVFAIL
+will be returned to the system making the original query.
+</p></dd><dt><a name="RESLIB_NOT_RESPONSE"></a><span class="term">RESLIB_NOT_RESPONSE response to query for <%1> was not a response</span></dt><dd><p>
+A debug message, the response to the specified query from an upstream
+nameserver (as identified by the ID of the response) did not have the QR
+bit set (thus indicating that the packet was a query, not a response).
+A SERVFAIL will be returned to the system making the original query.
</p></dd><dt><a name="RESLIB_NO_NS_RRSET"></a><span class="term">RESLIB_NO_NS_RRSET no NS RRSet in referral response received to query for <%1></span></dt><dd><p>
A debug message, this indicates that a response was received for the specified
query and was categorized as a referral. However, the received message did
@@ -1572,6 +1744,12 @@ nameservers for the specified zone.
A debug message recording that either a NXDOMAIN or an NXRRSET response has
been received to an upstream query for the specified question. Previous debug
messages will have indicated the server to which the question was sent.
+</p></dd><dt><a name="RESLIB_OPCODE_RESPONSE"></a><span class="term">RESLIB_OPCODE_RESPONSE response to query for <%1> did not have query opcode</span></dt><dd><p>
+A debug message, the response to the specified query from an upstream
+nameserver was a response that did not have the opcode set to that of
+a query. According to the standards, this is an invalid response to
+the query that was made, so a SERVFAIL will be returned to the system
+making the original query.
</p></dd><dt><a name="RESLIB_PROTOCOL"></a><span class="term">RESLIB_PROTOCOL protocol error in answer for %1: %3</span></dt><dd><p>
A debug message indicating that a protocol error was received. As there
are no retries left, an error will be reported.
@@ -1579,7 +1757,7 @@ are no retries left, an error will be reported.
A debug message indicating that a protocol error was received and that
the resolver is repeating the query to the same nameserver. After this
repeated query, there will be the indicated number of retries left.
-</p></dd><dt><a name="RESLIB_RCODE_ERR"></a><span class="term">RESLIB_RCODE_ERR RCODE indicates error in response to query for <%1></span></dt><dd><p>
+</p></dd><dt><a name="RESLIB_RCODE_ERROR"></a><span class="term">RESLIB_RCODE_ERROR response to query for <%1> returns RCODE of %2</span></dt><dd><p>
A debug message, the response to the specified query indicated an error
that is not covered by a specific code path. A SERVFAIL will be returned.
</p></dd><dt><a name="RESLIB_RECQ_CACHE_FIND"></a><span class="term">RESLIB_RECQ_CACHE_FIND found <%1> in the cache (resolve() instance %2)</span></dt><dd><p>
@@ -1626,6 +1804,10 @@ called because all nameservers for the zone in question are unreachable.
A debug message indicating that a RunningQuery's success callback has been
called because a nameserver has been found, and that a query is being sent
to the specified nameserver.
+</p></dd><dt><a name="RESLIB_TCP_TRUNCATED"></a><span class="term">RESLIB_TCP_TRUNCATED TCP response to query for %1 was truncated</span></dt><dd><p>
+This is a debug message logged when a response to the specified query to an
+upstream nameserver returned a response with the TC (truncation) bit set. This
+is treated as an error by the code.
</p></dd><dt><a name="RESLIB_TEST_SERVER"></a><span class="term">RESLIB_TEST_SERVER setting test server to %1(%2)</span></dt><dd><p>
This is a warning message only generated in unit tests. It indicates
that all upstream queries from the resolver are being routed to the
@@ -1840,6 +2022,27 @@ has been ignored.
This is debug message output when the resolver received a message with an
unsupported opcode (it can only process QUERY opcodes). It will return
a message to the sender with the RCODE set to NOTIMP.
+</p></dd><dt><a name="SOCKETREQUESTOR_CREATED"></a><span class="term">SOCKETREQUESTOR_CREATED Socket requestor created</span></dt><dd><p>
+Debug message. A socket requesor (client of the socket creator) is created
+for the corresponding application. Normally this should happen at most
+one time throughout the lifetime of the application.
+</p></dd><dt><a name="SOCKETREQUESTOR_DESTROYED"></a><span class="term">SOCKETREQUESTOR_DESTROYED Socket requestor destoryed</span></dt><dd><p>
+Debug message. The socket requestor created at SOCKETREQUESTOR_CREATED
+has been destroyed. This event is generally unexpected other than in
+test cases.
+</p></dd><dt><a name="SOCKETREQUESTOR_GETSOCKET"></a><span class="term">SOCKETREQUESTOR_GETSOCKET Received a %1 socket for [%2]:%3, FD=%4, token=%5, path=%6</span></dt><dd><p>
+Debug message. The socket requestor for the corresponding application
+has requested a socket for a set of address, port and protocol (shown
+in the log message) and successfully got it from the creator. The
+corresponding file descriptor and the associated "token" (an internal
+ID used between the creator and requestor) are shown in the log
+message.
+</p></dd><dt><a name="SOCKETREQUESTOR_RELEASESOCKET"></a><span class="term">SOCKETREQUESTOR_RELEASESOCKET Released a socket of token %1</span></dt><dd><p>
+Debug message. The socket requestor has released a socket passed by
+the creator. The associated token of the socket is shown in the
+log message. If the corresponding SOCKETREQUESTOR_GETSOCKET was logged
+more detailed information of the socket can be identified by matching
+the token.
</p></dd><dt><a name="SRVCOMM_ADDRESSES_NOT_LIST"></a><span class="term">SRVCOMM_ADDRESSES_NOT_LIST the address and port specification is not a list in %1</span></dt><dd><p>
This points to an error in configuration. What was supposed to be a list of
IP address - port pairs isn't a list at all but something else.
@@ -1858,7 +2061,7 @@ configuration malformed. The specification causing the error is given in the
message. A valid specification contains an address part (which must be a string
and must represent a valid IPv4 or IPv6 address) and port (which must be an
integer in the range valid for TCP/UDP ports on your system).
-</p></dd><dt><a name="SRVCOMM_ADDRESS_UNRECOVERABLE"></a><span class="term">SRVCOMM_ADDRESS_UNRECOVERABLE failed to recover original addresses also (%2)</span></dt><dd><p>
+</p></dd><dt><a name="SRVCOMM_ADDRESS_UNRECOVERABLE"></a><span class="term">SRVCOMM_ADDRESS_UNRECOVERABLE failed to recover original addresses also (%1)</span></dt><dd><p>
The recovery of old addresses after SRVCOMM_ADDRESS_FAIL also failed for
the reason listed.
</p><p>
@@ -1995,10 +2198,6 @@ is unknown in the implementation. The most likely cause is an
installation problem, where the specification file stats.spec is
from a different version of BIND 10 than the stats module itself.
Please check your installation.
-</p></dd><dt><a name="XFRIN_AXFR_DATABASE_FAILURE"></a><span class="term">XFRIN_AXFR_DATABASE_FAILURE AXFR transfer of zone %1 failed: %2</span></dt><dd><p>
-The AXFR transfer for the given zone has failed due to a database problem.
-The error is shown in the log message. Note: due to the code structure
-this can only happen for AXFR.
</p></dd><dt><a name="XFRIN_AXFR_INCONSISTENT_SOA"></a><span class="term">XFRIN_AXFR_INCONSISTENT_SOA AXFR SOAs are inconsistent for %1: %2 expected, %3 received</span></dt><dd><p>
The serial fields of the first and last SOAs of AXFR (including AXFR-style
IXFR) are not the same. According to RFC 5936 these two SOAs must be the
@@ -2046,6 +2245,15 @@ is not equal to the requested SOA serial.
</p></dd><dt><a name="XFRIN_IMPORT_DNS"></a><span class="term">XFRIN_IMPORT_DNS error importing python DNS module: %1</span></dt><dd><p>
There was an error importing the python DNS module pydnspp. The most
likely cause is a PYTHONPATH problem.
+</p></dd><dt><a name="XFRIN_IXFR_UPTODATE"></a><span class="term">XFRIN_IXFR_UPTODATE IXFR requested serial for %1 is %2, master has %3, not updating</span></dt><dd><p>
+The first SOA record in an IXFR response indicates the zone's serial
+at the primary server is not newer than the client's. This is
+basically unexpected event because normally the client first checks
+the SOA serial by an SOA query, but can still happen if the transfer
+is manually invoked or (although unlikely) there is a rapid change at
+the primary server between the SOA and IXFR queries. The client
+implementation confirms the whole response is this single SOA, and
+aborts the transfer just like a successful case.
</p></dd><dt><a name="XFRIN_MSGQ_SEND_ERROR"></a><span class="term">XFRIN_MSGQ_SEND_ERROR error while contacting %1 and %2</span></dt><dd><p>
There was a problem sending a message to the xfrout module or the
zone manager. This most likely means that the msgq daemon has quit or
@@ -2089,19 +2297,64 @@ message continuously appears, system resource consumption should be
checked, and you may even want to disable the corresponding transfers.
You may also want to file a bug report if this message appears so
often.
-</p></dd><dt><a name="XFRIN_XFR_TRANSFER_FAILURE"></a><span class="term">XFRIN_XFR_TRANSFER_FAILURE %1 transfer of zone %2 failed: %3</span></dt><dd><p>
-The XFR transfer for the given zone has failed due to a protocol error.
+</p></dd><dt><a name="XFRIN_XFR_TRANSFER_FAILURE"></a><span class="term">XFRIN_XFR_TRANSFER_FAILURE %1 transfer of zone %2 with %3 failed: %4</span></dt><dd><p>
+The XFR transfer for the given zone has failed due to an internal error.
The error is shown in the log message.
</p></dd><dt><a name="XFRIN_XFR_TRANSFER_FALLBACK"></a><span class="term">XFRIN_XFR_TRANSFER_FALLBACK falling back from IXFR to AXFR for %1</span></dt><dd><p>
The IXFR transfer of the given zone failed. This might happen in many cases,
such that the remote server doesn't support IXFR, we don't have the SOA record
(or the zone at all), we are out of sync, etc. In many of these situations,
AXFR could still work. Therefore we try that one in case it helps.
+</p></dd><dt><a name="XFRIN_XFR_TRANSFER_PROTOCOL_ERROR"></a><span class="term">XFRIN_XFR_TRANSFER_PROTOCOL_ERROR %1 transfer of zone %2 with %3 failed: %4</span></dt><dd><p>
+The XFR transfer for the given zone has failed due to a protocol
+error, such as an unexpected response from the primary server. The
+error is shown in the log message. It may be because the primary
+server implementation is broken or (although less likely) there was
+some attack attempt, but it can also happen due to configuration
+mismatch such as the remote server does not have authority for the
+zone any more but the local configuration hasn't been updated. So it
+is recommended to check the primary server configuration.
</p></dd><dt><a name="XFRIN_XFR_TRANSFER_STARTED"></a><span class="term">XFRIN_XFR_TRANSFER_STARTED %1 transfer of zone %2 started</span></dt><dd><p>
A connection to the master server has been made, the serial value in
the SOA record has been checked, and a zone transfer has been started.
</p></dd><dt><a name="XFRIN_XFR_TRANSFER_SUCCESS"></a><span class="term">XFRIN_XFR_TRANSFER_SUCCESS %1 transfer of zone %2 succeeded</span></dt><dd><p>
The XFR transfer of the given zone was successfully completed.
+</p></dd><dt><a name="XFRIN_ZONE_CREATED"></a><span class="term">XFRIN_ZONE_CREATED Zone %1 not found in the given data source, newly created</span></dt><dd><p>
+On starting an xfrin session, it is identified that the zone to be
+transferred is not found in the data source. This can happen if a
+secondary DNS server first tries to perform AXFR from a primary server
+without creating the zone image beforehand (e.g. by b10-loadzone). As
+of this writing the xfrin process provides backward compatible
+behavior to previous versions: creating a new one in the data source
+not to surprise existing users too much. This is probably not a good
+idea, however, in terms of who should be responsible for managing
+zones at a higher level. In future it is more likely that a separate
+zone management framework is provided, and the situation where the
+given zone isn't found in xfrout will be treated as an error.
+</p></dd><dt><a name="XFRIN_ZONE_MULTIPLE_SOA"></a><span class="term">XFRIN_ZONE_MULTIPLE_SOA Zone %1 has %2 SOA RRs</span></dt><dd><p>
+On starting an xfrin session, it is identified that the zone to be
+transferred has multiple SOA RRs. Such a zone is broken, but could be
+accidentally configured especially in a data source using "non
+captive" backend database. The implementation ignores entire SOA RRs
+and tries to continue processing as if the zone were empty. This
+means subsequent AXFR can succeed and possibly replace the zone with
+valid content, but an IXFR attempt will fail.
+</p></dd><dt><a name="XFRIN_ZONE_NO_SOA"></a><span class="term">XFRIN_ZONE_NO_SOA Zone %1 does not have SOA</span></dt><dd><p>
+On starting an xfrin session, it is identified that the zone to be
+transferred does not have an SOA RR in the data source. This is not
+necessarily an error; if a secondary DNS server first tries to perform
+transfer from a primary server, the zone can be empty, and therefore
+doesn't have an SOA. Subsequent AXFR will fill in the zone; if the
+attempt is IXFR it will fail in query creation.
+</p></dd><dt><a name="XFRIN_ZONE_SERIAL_AHEAD"></a><span class="term">XFRIN_ZONE_SERIAL_AHEAD Serial number (%1) for %2 received from master %3 < ours (%4)</span></dt><dd><p>
+The response to an SOA query prior to xfr indicated that the zone's
+SOA serial at the primary server is smaller than that of the xfrin
+client. This is not necessarily an error especially if that
+particular primary server is another secondary server which hasn't got
+the latest version of the zone. But if the primary server is known to
+be the real source of the zone, some unexpected inconsistency may have
+happened, and you may want to take a closer look. In this case xfrin
+doesn't perform subsequent zone transfer.
</p></dd><dt><a name="XFROUT_BAD_TSIG_KEY_STRING"></a><span class="term">XFROUT_BAD_TSIG_KEY_STRING bad TSIG key string: %1</span></dt><dd><p>
The TSIG key string as read from the configuration does not represent
a valid TSIG key.
diff --git a/doc/guide/bind10-messages.xml b/doc/guide/bind10-messages.xml
index 4dc02d4..ba55de0 100644
--- a/doc/guide/bind10-messages.xml
+++ b/doc/guide/bind10-messages.xml
@@ -68,6 +68,22 @@
<para>
<variablelist>
+<varlistentry id="ASIODNS_FD_ADD_TCP">
+<term>ASIODNS_FD_ADD_TCP adding a new TCP server by opened fd %1</term>
+<listitem><para>
+A debug message informing about installing a file descriptor as a server.
+The file descriptor number is noted.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="ASIODNS_FD_ADD_UDP">
+<term>ASIODNS_FD_ADD_UDP adding a new UDP server by opened fd %1</term>
+<listitem><para>
+A debug message informing about installing a file descriptor as a server.
+The file descriptor number is noted.
+</para></listitem>
+</varlistentry>
+
<varlistentry id="ASIODNS_FETCH_COMPLETED">
<term>ASIODNS_FETCH_COMPLETED upstream fetch to %1(%2) has now completed</term>
<listitem><para>
@@ -720,6 +736,16 @@ startup, as described for BIND10_KILLING_ALL_PROCESSES
</para></listitem>
</varlistentry>
+<varlistentry id="BIND10_LOST_SOCKET_CONSUMER">
+<term>BIND10_LOST_SOCKET_CONSUMER consumer %1 of sockets disconnected, considering all its sockets closed</term>
+<listitem><para>
+A connection from one of the applications which requested a socket was
+closed. This means the application has terminated, so all the sockets it was
+using are now closed and bind10 process can release them as well, unless the
+same sockets are used by yet another application.
+</para></listitem>
+</varlistentry>
+
<varlistentry id="BIND10_MSGQ_ALREADY_RUNNING">
<term>BIND10_MSGQ_ALREADY_RUNNING msgq daemon already running, cannot start</term>
<listitem><para>
@@ -739,6 +765,15 @@ inconsistent state of the system, and BIND 10 will now shut down.
</para></listitem>
</varlistentry>
+<varlistentry id="BIND10_NO_SOCKET">
+<term>BIND10_NO_SOCKET couldn't send a socket for token %1 because of error: %2</term>
+<listitem><para>
+An error occurred when the bind10 process was asked to send a socket file
+descriptor. The error is mentioned, most common reason is that the request
+is invalid and may not come from bind10 process at all.
+</para></listitem>
+</varlistentry>
+
<varlistentry id="BIND10_PROCESS_ENDED">
<term>BIND10_PROCESS_ENDED process %2 of %1 ended with status %3</term>
<listitem><para>
@@ -1943,7 +1978,7 @@ in the answer as a result.
</varlistentry>
<varlistentry id="DATASRC_DATABASE_FIND_RECORDS">
-<term>DATASRC_DATABASE_FIND_RECORDS looking in datasource %1 for record %2/%3</term>
+<term>DATASRC_DATABASE_FIND_RECORDS looking in datasource %1 for record %2/%3/%4</term>
<listitem><para>
Debug information. The database data source is looking up records with the given
name and type in the database.
@@ -1960,6 +1995,24 @@ database). The data in database should be checked and fixed.
</para></listitem>
</varlistentry>
+<varlistentry id="DATASRC_DATABASE_FOUND_ANY">
+<term>DATASRC_DATABASE_FOUND_ANY search in datasource %1 resulted in returning all records of %2</term>
+<listitem><para>
+The data returned by the database backend contained data for the given domain
+name, so all the RRsets of the domain are returned.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="DATASRC_DATABASE_FOUND_CNAME">
+<term>DATASRC_DATABASE_FOUND_CNAME search in datasource %1 for %2/%3/%4 found CNAME, resulting in %5</term>
+<listitem><para>
+When searching the domain for a name a CNAME was found at that name.
+Even though it was not the RR type being sought, it is returned. (The
+caller may want to continue the lookup by replacing the query name with
+the canonical name and restarting the query with the original RR type.)
+</para></listitem>
+</varlistentry>
+
<varlistentry id="DATASRC_DATABASE_FOUND_DELEGATION">
<term>DATASRC_DATABASE_FOUND_DELEGATION Found delegation at %2 in %1</term>
<listitem><para>
@@ -1969,7 +2022,7 @@ at the given domain name. It will return that one instead.
</varlistentry>
<varlistentry id="DATASRC_DATABASE_FOUND_DELEGATION_EXACT">
-<term>DATASRC_DATABASE_FOUND_DELEGATION_EXACT Found delegation at %2 (exact match) in %1</term>
+<term>DATASRC_DATABASE_FOUND_DELEGATION_EXACT search in datasource %1 for %2/%3/%4 found delegation at %5</term>
<listitem><para>
The program found the domain requested, but it is a delegation point to a
different zone, therefore it is not authoritative for this domain name.
@@ -1989,9 +2042,10 @@ instead.
<varlistentry id="DATASRC_DATABASE_FOUND_EMPTY_NONTERMINAL">
<term>DATASRC_DATABASE_FOUND_EMPTY_NONTERMINAL empty non-terminal %2 in %1</term>
<listitem><para>
-The domain name doesn't have any RRs, so it doesn't exist in the database.
-However, it has a subdomain, so it exists in the DNS address space. So we
-return NXRRSET instead of NXDOMAIN.
+The domain name does not have any RRs associated with it, so it doesn't
+exist in the database. However, it has a subdomain, so it does exist
+in the DNS address space. This type of domain is known an an "empty
+non-terminal" and so we return NXRRSET instead of NXDOMAIN.
</para></listitem>
</varlistentry>
@@ -2004,15 +2058,24 @@ domain name, class and type.
</varlistentry>
<varlistentry id="DATASRC_DATABASE_FOUND_NXRRSET">
-<term>DATASRC_DATABASE_FOUND_NXRRSET search in datasource %1 resulted in NXRRSET for %2/%3/%4</term>
+<term>DATASRC_DATABASE_FOUND_NXRRSET search in datasource %1 for %2/%3/%4 resulted in NXRRSET</term>
<listitem><para>
The data returned by the database backend contained data for the given domain
name and class, but not for the given type.
</para></listitem>
</varlistentry>
+<varlistentry id="DATASRC_DATABASE_FOUND_NXRRSET_NSEC">
+<term>DATASRC_DATABASE_FOUND_NXRRSET_NSEC search in datasource %1 for %2/%3/%4 resulted in RRset %5</term>
+<listitem><para>
+A search in the database for RRs for the specified name, type and class has
+located RRs that match the name and class but not the type. DNSSEC information
+has been requested and returned.
+</para></listitem>
+</varlistentry>
+
<varlistentry id="DATASRC_DATABASE_FOUND_RRSET">
-<term>DATASRC_DATABASE_FOUND_RRSET search in datasource %1 resulted in RRset %2</term>
+<term>DATASRC_DATABASE_FOUND_RRSET search in datasource %1 resulted in RRset %5</term>
<listitem><para>
The data returned by the database backend contained data for the given domain
name, and it either matches the type or has a relevant type. The RRset that is
@@ -2097,6 +2160,14 @@ to find any invalid data and fix it.
</para></listitem>
</varlistentry>
+<varlistentry id="DATASRC_DATABASE_NO_MATCH">
+<term>DATASRC_DATABASE_NO_MATCH not match for %2/%3/%4 in %1</term>
+<listitem><para>
+No match (not even a wildcard) was found in the named data source for the given
+name/type/class in the data source.
+</para></listitem>
+</varlistentry>
+
<varlistentry id="DATASRC_DATABASE_UPDATER_COMMIT">
<term>DATASRC_DATABASE_UPDATER_COMMIT updates committed for '%1/%2' on %3</term>
<listitem><para>
@@ -2106,6 +2177,15 @@ its class and the database name are printed.
</para></listitem>
</varlistentry>
+<varlistentry id="DATASRC_DATABASE_UPDATER_COMMIT (1)">
+<term>DATASRC_DATABASE_UPDATER_COMMIT (1) updates committed for '%1/%2' on %3</term>
+<listitem><para>
+Debug information. A set of updates to a zone has been successfully
+committed to the corresponding database backend. The zone name,
+its class and the database name are printed.
+</para></listitem>
+</varlistentry>
+
<varlistentry id="DATASRC_DATABASE_UPDATER_CREATED">
<term>DATASRC_DATABASE_UPDATER_CREATED zone updater created for '%1/%2' on %3</term>
<listitem><para>
@@ -2114,6 +2194,14 @@ the shown zone on the shown backend database.
</para></listitem>
</varlistentry>
+<varlistentry id="DATASRC_DATABASE_UPDATER_CREATED (1)">
+<term>DATASRC_DATABASE_UPDATER_CREATED (1) zone updater created for '%1/%2' on %3</term>
+<listitem><para>
+Debug information. A zone updater object is created to make updates to
+the shown zone on the shown backend database.
+</para></listitem>
+</varlistentry>
+
<varlistentry id="DATASRC_DATABASE_UPDATER_DESTROYED">
<term>DATASRC_DATABASE_UPDATER_DESTROYED zone updater destroyed for '%1/%2' on %3</term>
<listitem><para>
@@ -2123,6 +2211,15 @@ database.
</para></listitem>
</varlistentry>
+<varlistentry id="DATASRC_DATABASE_UPDATER_DESTROYED (1)">
+<term>DATASRC_DATABASE_UPDATER_DESTROYED (1) zone updater destroyed for '%1/%2' on %3</term>
+<listitem><para>
+Debug information. A zone updater object is destroyed, either successfully
+or after failure of, making updates to the shown zone on the shown backend
+database.
+</para></listitem>
+</varlistentry>
+
<varlistentry id="DATASRC_DATABASE_UPDATER_ROLLBACK">
<term>DATASRC_DATABASE_UPDATER_ROLLBACK zone updates roll-backed for '%1/%2' on %3</term>
<listitem><para>
@@ -2135,6 +2232,18 @@ the underlying database name are shown in the log message.
</para></listitem>
</varlistentry>
+<varlistentry id="DATASRC_DATABASE_UPDATER_ROLLBACK (1)">
+<term>DATASRC_DATABASE_UPDATER_ROLLBACK (1) zone updates roll-backed for '%1/%2' on %3</term>
+<listitem><para>
+A zone updater is being destroyed without committing the changes.
+This would typically mean the update attempt was aborted due to some
+error, but may also be a bug of the application that forgets committing
+the changes. The intermediate changes made through the updater won't
+be applied to the underlying database. The zone name, its class, and
+the underlying database name are shown in the log message.
+</para></listitem>
+</varlistentry>
+
<varlistentry id="DATASRC_DATABASE_UPDATER_ROLLBACKFAIL">
<term>DATASRC_DATABASE_UPDATER_ROLLBACKFAIL failed to roll back zone updates for '%1/%2' on %3: %4</term>
<listitem><para>
@@ -2152,16 +2261,34 @@ database module are shown in the log message.
</para></listitem>
</varlistentry>
-<varlistentry id="DATASRC_DATABASE_WILDCARD">
-<term>DATASRC_DATABASE_WILDCARD constructing RRset %3 from wildcard %2 in %1</term>
+<varlistentry id="DATASRC_DATABASE_UPDATER_ROLLBACKFAIL (1)">
+<term>DATASRC_DATABASE_UPDATER_ROLLBACKFAIL (1) failed to roll back zone updates for '%1/%2' on %3: %4</term>
<listitem><para>
-The database doesn't contain directly matching domain, but it does contain a
-wildcard one which is being used to synthesize the answer.
+A zone updater is being destroyed without committing the changes to
+the database, and attempts to rollback incomplete updates, but it
+unexpectedly fails. The higher level implementation does not expect
+it to fail, so this means either a serious operational error in the
+underlying data source (such as a system failure of a database) or
+software bug in the underlying data source implementation. In either
+case if this message is logged the administrator should carefully
+examine the underlying data source to see what exactly happens and
+whether the data is still valid. The zone name, its class, and the
+underlying database name as well as the error message thrown from the
+database module are shown in the log message.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="DATASRC_DATABASE_WILDCARD_ANY">
+<term>DATASRC_DATABASE_WILDCARD_ANY search in datasource %1 resulted in wildcard match type ANY on %2</term>
+<listitem><para>
+The database doesn't contain directly matching name. When searching
+for a wildcard match, a wildcard record matching the name of the query
+containing some RRsets was found. All the RRsets of the node are returned.
</para></listitem>
</varlistentry>
<varlistentry id="DATASRC_DATABASE_WILDCARD_CANCEL_NS">
-<term>DATASRC_DATABASE_WILDCARD_CANCEL_NS canceled wildcard match on %2 because %3 contains NS in %1</term>
+<term>DATASRC_DATABASE_WILDCARD_CANCEL_NS canceled wildcard match on %3 because %2 contains NS (data source %1)</term>
<listitem><para>
The database was queried to provide glue data and it didn't find direct match.
It could create it from given wildcard, but matching wildcards is forbidden
@@ -2180,13 +2307,49 @@ discovers it differently).
</para></listitem>
</varlistentry>
+<varlistentry id="DATASRC_DATABASE_WILDCARD_CNAME">
+<term>DATASRC_DATABASE_WILDCARD_CNAME search in datasource %1 for %2/%3/%4 found wildcard CNAME at %5, resulting in %6</term>
+<listitem><para>
+The database doesn't contain directly matching name. When searching
+for a wildcard match, a CNAME RR was found at a wildcard record
+matching the name. This is returned as the result of the search.
+</para></listitem>
+</varlistentry>
+
<varlistentry id="DATASRC_DATABASE_WILDCARD_EMPTY">
-<term>DATASRC_DATABASE_WILDCARD_EMPTY implicit wildcard %2 used to construct %3 in %1</term>
+<term>DATASRC_DATABASE_WILDCARD_EMPTY found subdomains of %2 which is a wildcard match for %3 in %1</term>
<listitem><para>
-The given wildcard exists implicitly in the domainspace, as empty nonterminal
-(eg. there's something like subdomain.*.example.org, so *.example.org exists
-implicitly, but is empty). This will produce NXRRSET, because the constructed
-domain is empty as well as the wildcard.
+The given wildcard matches the name being sough but it as an empty
+nonterminal (e.g. there's nothing at *.example.com but something like
+subdomain.*.example.org, do exist: so *.example.org exists in the
+namespace but has no RRs assopciated with it). This will produce NXRRSET.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="DATASRC_DATABASE_WILDCARD_MATCH">
+<term>DATASRC_DATABASE_WILDCARD_MATCH search in datasource %1 resulted in wildcard match at %5 with RRset %6</term>
+<listitem><para>
+The database doesn't contain directly matching name. When searching
+for a wildcard match, a wildcard record matching the name and type of
+the query was found. The data at this point is returned.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="DATASRC_DATABASE_WILDCARD_NS">
+<term>DATASRC_DATABASE_WILDCARD_NS search in datasource %1 for %2/%3/%4 found wildcard delegation at %5, resulting in %6</term>
+<listitem><para>
+The database doesn't contain directly matching name. When searching
+for a wildcard match, an NS RR was found at a wildcard record matching
+the name. This is returned as the result of the search.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="DATASRC_DATABASE_WILDCARD_NXRRSET">
+<term>DATASRC_DATABASE_WILDCARD_NXRRSET search in datasource %1 for %2/%3/%4 resulted in wildcard NXRRSET at %5</term>
+<listitem><para>
+The database doesn't contain directly matching name. When searching
+for a wildcard match, a matching wildcard entry was found but it did
+not contain RRs the requested type. AN NXRRSET indication is returned.
</para></listitem>
</varlistentry>
@@ -2410,7 +2573,7 @@ Debug information. The requested record was found.
<term>DATASRC_MEM_SUPER_STOP stopped at superdomain '%1', domain '%2' is empty</term>
<listitem><para>
Debug information. The search stopped at a superdomain of the requested
-domain. The domain is a empty nonterminal, therefore it is treated as NXRRSET
+domain. The domain is an empty nonterminal, therefore it is treated as NXRRSET
case (eg. the domain exists, but it doesn't have the requested record type).
</para></listitem>
</varlistentry>
@@ -3069,12 +3232,98 @@ generated.
</para></listitem>
</varlistentry>
+<varlistentry id="DDNS_CC_SESSION_ERROR">
+<term>DDNS_CC_SESSION_ERROR error reading from cc channel: %1</term>
+<listitem><para>
+There was a problem reading from the command and control channel. The
+most likely cause is that the msgq process is not running.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="DDNS_CC_SESSION_TIMEOUT_ERROR">
+<term>DDNS_CC_SESSION_TIMEOUT_ERROR timeout waiting for cc response</term>
+<listitem><para>
+There was a problem reading a response from another module over the
+command and control channel. The most likely cause is that the
+configuration manager b10-cfgmgr is not running.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="DDNS_CONFIG_ERROR">
+<term>DDNS_CONFIG_ERROR error found in configuration data: %1</term>
+<listitem><para>
+The ddns process encountered an error when installing the configuration at
+startup time. Details of the error are included in the log message.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="DDNS_MODULECC_SESSION_ERROR">
+<term>DDNS_MODULECC_SESSION_ERROR error encountered by configuration/command module: %1</term>
+<listitem><para>
+There was a problem in the lower level module handling configuration and
+control commands. This could happen for various reasons, but the most likely
+cause is that the configuration database contains a syntax error and ddns
+failed to start at initialization. A detailed error message from the module
+will also be displayed.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="DDNS_RECEIVED_SHUTDOWN_COMMAND">
+<term>DDNS_RECEIVED_SHUTDOWN_COMMAND shutdown command received</term>
+<listitem><para>
+The ddns process received a shutdown command from the command channel
+and will now shut down.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="DDNS_RUNNING">
+<term>DDNS_RUNNING ddns server is running and listening for updates</term>
+<listitem><para>
+The ddns process has successfully started and is now ready to receive commands
+and updates.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="DDNS_SHUTDOWN">
+<term>DDNS_SHUTDOWN ddns server shutting down</term>
+<listitem><para>
+The ddns process is shutting down. It will no longer listen for new commands
+or updates. Any command or update that is being addressed at this moment will
+be completed, after which the process will exit.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="DDNS_STOPPED">
+<term>DDNS_STOPPED ddns server has stopped</term>
+<listitem><para>
+The ddns process has successfully stopped and is no longer listening for or
+handling commands or updates, and will now exit.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="DDNS_STOPPED_BY_KEYBOARD">
+<term>DDNS_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down</term>
+<listitem><para>
+There was a keyboard interrupt signal to stop the ddns process. The
+process will now shut down.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="DDNS_UNCAUGHT_EXCEPTION">
+<term>DDNS_UNCAUGHT_EXCEPTION uncaught exception of type %1: %2</term>
+<listitem><para>
+The b10-ddns process encountered an uncaught exception and will now shut
+down. This is indicative of a programming error and should not happen under
+normal circumstances. The exception type and message are printed.
+</para></listitem>
+</varlistentry>
+
<varlistentry id="LIBXFRIN_DIFFERENT_TTL">
-<term>LIBXFRIN_DIFFERENT_TTL multiple data with different TTLs (%1, %2) on %3/%4. Adjusting %2 -> %1.</term>
+<term>LIBXFRIN_DIFFERENT_TTL multiple data with different TTLs (%1, %2) on %3/%4/%5. Adjusting %2 -> %1.</term>
<listitem><para>
The xfrin module received an update containing multiple rdata changes for the
same RRset. But the TTLs of these don't match each other. As we combine them
-together, the later one get's overwritten to the earlier one in the sequence.
+together, the latter one gets overwritten to the earlier one in the sequence.
</para></listitem>
</varlistentry>
@@ -3476,6 +3725,24 @@ doesn't have an NS RR. Notify message won't be sent to such a zone.
</para></listitem>
</varlistentry>
+<varlistentry id="NSAS_EMPTY_RESPONSE">
+<term>NSAS_EMPTY_RESPONSE response to query for %1 returned an empty answer section</term>
+<listitem><para>
+The NSAS (nameserver address store - part of the resolver) made a query
+for information it needed. The query completed successfully but the
+answer section in the response was empty.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="NSAS_ERROR_RESPONSE">
+<term>NSAS_ERROR_RESPONSE error response of %1 returned in query for %2</term>
+<listitem><para>
+The NSAS (nameserver address store - part of the resolver) made a query
+for information it needed. The query completed successfully but the
+RCODE in the response was something other than NOERROR.
+</para></listitem>
+</varlistentry>
+
<varlistentry id="NSAS_FIND_NS_ADDRESS">
<term>NSAS_FIND_NS_ADDRESS asking resolver to obtain A and AAAA records for %1</term>
<listitem><para>
@@ -3494,21 +3761,6 @@ nameserver through an external query.
</para></listitem>
</varlistentry>
-<varlistentry id="NSAS_INVALID_RESPONSE">
-<term>NSAS_INVALID_RESPONSE queried for %1 but got invalid response</term>
-<listitem><para>
-The NSAS (nameserver address store - part of the resolver) made a query
-for a RR for the specified nameserver but received an invalid response.
-Either the success function was called without a DNS message or the
-message was invalid on some way. (In the latter case, the error should
-have been picked up elsewhere in the processing logic, hence the raising
-of the error here.)
-</para><para>
-This message indicates an internal error in the NSAS. Please raise a
-bug report.
-</para></listitem>
-</varlistentry>
-
<varlistentry id="NSAS_LOOKUP_CANCEL">
<term>NSAS_LOOKUP_CANCEL lookup for zone %1 has been canceled</term>
<listitem><para>
@@ -3528,6 +3780,18 @@ nameservers in the zone.
</para></listitem>
</varlistentry>
+<varlistentry id="NSAS_NULL_RESPONSE">
+<term>NSAS_NULL_RESPONSE got null message in success callback for query for %1</term>
+<listitem><para>
+The NSAS (nameserver address store - part of the resolver) made a query
+for information it needed. The query completed successfully, but the
+message passed to the callback was null.
+</para><para>
+This message indicates an internal error in the NSAS. Please raise a
+bug report.
+</para></listitem>
+</varlistentry>
+
<varlistentry id="NSAS_SEARCH_ZONE_NS">
<term>NSAS_SEARCH_ZONE_NS searching NSAS for nameservers for zone %1</term>
<listitem><para>
@@ -3565,34 +3829,97 @@ bug report.
<varlistentry id="RESLIB_ANSWER">
<term>RESLIB_ANSWER answer received in response to query for <%1></term>
<listitem><para>
-A debug message recording that an answer has been received to an upstream
-query for the specified question. Previous debug messages will have indicated
-the server to which the question was sent.
+A debug message reporting that an answer has been received to an upstream
+query for the specified question. Previous debug messages will have
+indicated the server to which the question was sent.
</para></listitem>
</varlistentry>
<varlistentry id="RESLIB_CNAME">
<term>RESLIB_CNAME CNAME received in response to query for <%1></term>
<listitem><para>
-A debug message recording that CNAME response has been received to an upstream
-query for the specified question. Previous debug messages will have indicated
-the server to which the question was sent.
+A debug message recording that CNAME response has been received to an
+upstream query for the specified question. Previous debug messages will
+have indicated the server to which the question was sent.
</para></listitem>
</varlistentry>
<varlistentry id="RESLIB_DEEPEST">
<term>RESLIB_DEEPEST did not find <%1> in cache, deepest delegation found is %2</term>
<listitem><para>
-A debug message, a cache lookup did not find the specified <name, class,
-type> tuple in the cache; instead, the deepest delegation found is indicated.
+A debug message, a cache lookup did not find the specified <name,
+class, type> tuple in the cache; instead, the deepest delegation found
+is indicated.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="RESLIB_EMPTY_RESPONSE">
+<term>RESLIB_EMPTY_RESPONSE empty response received to query for <%1></term>
+<listitem><para>
+A debug message, the response to the specified query from an upstream
+nameserver did not contain anything in the answer or authority sections,
+although in all other respects it was a valid response. A SERVFAIL will
+be returned to the system making the original query.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="RESLIB_ERROR_RESPONSE">
+<term>RESLIB_ERROR_RESPONSE unspecified error received in response to query for <%1></term>
+<listitem><para>
+A debug message, the response to the specified query to an upstream
+nameserver indicated that the response was classified as an erroneous
+response, but that the nature of the error cannot be identified.
+A SERVFAIL will be returned to the system making the original query.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="RESLIB_EXTRADATA_RESPONSE">
+<term>RESLIB_EXTRADATA_RESPONSE extra data in response to query for <%1></term>
+<listitem><para>
+A debug message indicating that the response to the specified query
+from an upstream nameserver contained too much data. This can happen if
+an ANY query was sent and the answer section in the response contained
+multiple RRs with different names. A SERVFAIL will be returned to the
+system making the original query.
</para></listitem>
</varlistentry>
<varlistentry id="RESLIB_FOLLOW_CNAME">
<term>RESLIB_FOLLOW_CNAME following CNAME chain to <%1></term>
<listitem><para>
-A debug message, a CNAME response was received and another query is being issued
-for the <name, class, type> tuple.
+A debug message, a CNAME response was received and another query is
+being issued for the <name, class, type> tuple.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="RESLIB_INVALID_NAMECLASS_RESPONSE">
+<term>RESLIB_INVALID_NAMECLASS_RESPONSE invalid name or class in response to query for <%1></term>
+<listitem><para>
+A debug message, the response to the specified query from an upstream
+nameserver (as identified by the ID of the response) contained either
+an answer not matching the query name or an answer having a different
+class to that queried for. A SERVFAIL will be returned to the system
+making the original query.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="RESLIB_INVALID_QNAME_RESPONSE">
+<term>RESLIB_INVALID_QNAME_RESPONSE invalid name or class in response to query for <%1></term>
+<listitem><para>
+A debug message, the response to the specified query from an upstream
+nameserver (as identified by the ID of the response) contained a name
+in the question section that did not match that of the query. A SERVFAIL
+will be returned to the system making the original query.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="RESLIB_INVALID_TYPE_RESPONSE">
+<term>RESLIB_INVALID_TYPE_RESPONSE invalid name or class in response to query for <%1></term>
+<listitem><para>
+A debug message, the response to the specified query from an upstream
+nameserver (as identified by the ID of the response) contained an
+invalid type field. A SERVFAIL will be returned to the system making
+the original query.
</para></listitem>
</varlistentry>
@@ -3607,6 +3934,46 @@ is where on CNAME points to another) and so an error is being returned.
</para></listitem>
</varlistentry>
+<varlistentry id="RESLIB_MULTIPLE_CLASS_RESPONSE">
+<term>RESLIB_MULTIPLE_CLASS_RESPONSE response to query for <%1> contained multiple RRsets with different classes</term>
+<listitem><para>
+A debug message reporting that the response to an upstream query for
+the specified name contained multiple RRsets in the answer and not all
+were of the same class. This is a violation of the standard and so a
+SERVFAIL will be returned.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="RESLIB_NOTSINGLE_RESPONSE">
+<term>RESLIB_NOTSINGLE_RESPONSE response to query for <%1> was not a response</term>
+<listitem><para>
+A debug message, the response to the specified query from an upstream
+nameserver was a CNAME that had mutiple RRs in the RRset. This is
+an invalid response according to the standards so a SERVFAIL will be
+returned to the system making the original query.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="RESLIB_NOT_ONE_QNAME_RESPONSE">
+<term>RESLIB_NOT_ONE_QNAME_RESPONSE not one question in response to query for <%1></term>
+<listitem><para>
+A debug message, the response to the specified query from an upstream
+nameserver (as identified by the ID of the response) did not contain
+one name in the question section as required by the standard. A SERVFAIL
+will be returned to the system making the original query.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="RESLIB_NOT_RESPONSE">
+<term>RESLIB_NOT_RESPONSE response to query for <%1> was not a response</term>
+<listitem><para>
+A debug message, the response to the specified query from an upstream
+nameserver (as identified by the ID of the response) did not have the QR
+bit set (thus indicating that the packet was a query, not a response).
+A SERVFAIL will be returned to the system making the original query.
+</para></listitem>
+</varlistentry>
+
<varlistentry id="RESLIB_NO_NS_RRSET">
<term>RESLIB_NO_NS_RRSET no NS RRSet in referral response received to query for <%1></term>
<listitem><para>
@@ -3634,6 +4001,17 @@ messages will have indicated the server to which the question was sent.
</para></listitem>
</varlistentry>
+<varlistentry id="RESLIB_OPCODE_RESPONSE">
+<term>RESLIB_OPCODE_RESPONSE response to query for <%1> did not have query opcode</term>
+<listitem><para>
+A debug message, the response to the specified query from an upstream
+nameserver was a response that did not have the opcode set to that of
+a query. According to the standards, this is an invalid response to
+the query that was made, so a SERVFAIL will be returned to the system
+making the original query.
+</para></listitem>
+</varlistentry>
+
<varlistentry id="RESLIB_PROTOCOL">
<term>RESLIB_PROTOCOL protocol error in answer for %1: %3</term>
<listitem><para>
@@ -3651,8 +4029,8 @@ repeated query, there will be the indicated number of retries left.
</para></listitem>
</varlistentry>
-<varlistentry id="RESLIB_RCODE_ERR">
-<term>RESLIB_RCODE_ERR RCODE indicates error in response to query for <%1></term>
+<varlistentry id="RESLIB_RCODE_ERROR">
+<term>RESLIB_RCODE_ERROR response to query for <%1> returns RCODE of %2</term>
<listitem><para>
A debug message, the response to the specified query indicated an error
that is not covered by a specific code path. A SERVFAIL will be returned.
@@ -3758,6 +4136,15 @@ to the specified nameserver.
</para></listitem>
</varlistentry>
+<varlistentry id="RESLIB_TCP_TRUNCATED">
+<term>RESLIB_TCP_TRUNCATED TCP response to query for %1 was truncated</term>
+<listitem><para>
+This is a debug message logged when a response to the specified query to an
+upstream nameserver returned a response with the TC (truncation) bit set. This
+is treated as an error by the code.
+</para></listitem>
+</varlistentry>
+
<varlistentry id="RESLIB_TEST_SERVER">
<term>RESLIB_TEST_SERVER setting test server to %1(%2)</term>
<listitem><para>
@@ -4217,6 +4604,47 @@ a message to the sender with the RCODE set to NOTIMP.
</para></listitem>
</varlistentry>
+<varlistentry id="SOCKETREQUESTOR_CREATED">
+<term>SOCKETREQUESTOR_CREATED Socket requestor created</term>
+<listitem><para>
+Debug message. A socket requesor (client of the socket creator) is created
+for the corresponding application. Normally this should happen at most
+one time throughout the lifetime of the application.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="SOCKETREQUESTOR_DESTROYED">
+<term>SOCKETREQUESTOR_DESTROYED Socket requestor destoryed</term>
+<listitem><para>
+Debug message. The socket requestor created at SOCKETREQUESTOR_CREATED
+has been destroyed. This event is generally unexpected other than in
+test cases.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="SOCKETREQUESTOR_GETSOCKET">
+<term>SOCKETREQUESTOR_GETSOCKET Received a %1 socket for [%2]:%3, FD=%4, token=%5, path=%6</term>
+<listitem><para>
+Debug message. The socket requestor for the corresponding application
+has requested a socket for a set of address, port and protocol (shown
+in the log message) and successfully got it from the creator. The
+corresponding file descriptor and the associated "token" (an internal
+ID used between the creator and requestor) are shown in the log
+message.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="SOCKETREQUESTOR_RELEASESOCKET">
+<term>SOCKETREQUESTOR_RELEASESOCKET Released a socket of token %1</term>
+<listitem><para>
+Debug message. The socket requestor has released a socket passed by
+the creator. The associated token of the socket is shown in the
+log message. If the corresponding SOCKETREQUESTOR_GETSOCKET was logged
+more detailed information of the socket can be identified by matching
+the token.
+</para></listitem>
+</varlistentry>
+
<varlistentry id="SRVCOMM_ADDRESSES_NOT_LIST">
<term>SRVCOMM_ADDRESSES_NOT_LIST the address and port specification is not a list in %1</term>
<listitem><para>
@@ -4256,7 +4684,7 @@ integer in the range valid for TCP/UDP ports on your system).
</varlistentry>
<varlistentry id="SRVCOMM_ADDRESS_UNRECOVERABLE">
-<term>SRVCOMM_ADDRESS_UNRECOVERABLE failed to recover original addresses also (%2)</term>
+<term>SRVCOMM_ADDRESS_UNRECOVERABLE failed to recover original addresses also (%1)</term>
<listitem><para>
The recovery of old addresses after SRVCOMM_ADDRESS_FAIL also failed for
the reason listed.
@@ -4587,15 +5015,6 @@ Please check your installation.
</para></listitem>
</varlistentry>
-<varlistentry id="XFRIN_AXFR_DATABASE_FAILURE">
-<term>XFRIN_AXFR_DATABASE_FAILURE AXFR transfer of zone %1 failed: %2</term>
-<listitem><para>
-The AXFR transfer for the given zone has failed due to a database problem.
-The error is shown in the log message. Note: due to the code structure
-this can only happen for AXFR.
-</para></listitem>
-</varlistentry>
-
<varlistentry id="XFRIN_AXFR_INCONSISTENT_SOA">
<term>XFRIN_AXFR_INCONSISTENT_SOA AXFR SOAs are inconsistent for %1: %2 expected, %3 received</term>
<listitem><para>
@@ -4698,6 +5117,20 @@ likely cause is a PYTHONPATH problem.
</para></listitem>
</varlistentry>
+<varlistentry id="XFRIN_IXFR_UPTODATE">
+<term>XFRIN_IXFR_UPTODATE IXFR requested serial for %1 is %2, master has %3, not updating</term>
+<listitem><para>
+The first SOA record in an IXFR response indicates the zone's serial
+at the primary server is not newer than the client's. This is
+basically unexpected event because normally the client first checks
+the SOA serial by an SOA query, but can still happen if the transfer
+is manually invoked or (although unlikely) there is a rapid change at
+the primary server between the SOA and IXFR queries. The client
+implementation confirms the whole response is this single SOA, and
+aborts the transfer just like a successful case.
+</para></listitem>
+</varlistentry>
+
<varlistentry id="XFRIN_MSGQ_SEND_ERROR">
<term>XFRIN_MSGQ_SEND_ERROR error while contacting %1 and %2</term>
<listitem><para>
@@ -4787,9 +5220,9 @@ often.
</varlistentry>
<varlistentry id="XFRIN_XFR_TRANSFER_FAILURE">
-<term>XFRIN_XFR_TRANSFER_FAILURE %1 transfer of zone %2 failed: %3</term>
+<term>XFRIN_XFR_TRANSFER_FAILURE %1 transfer of zone %2 with %3 failed: %4</term>
<listitem><para>
-The XFR transfer for the given zone has failed due to a protocol error.
+The XFR transfer for the given zone has failed due to an internal error.
The error is shown in the log message.
</para></listitem>
</varlistentry>
@@ -4804,6 +5237,20 @@ AXFR could still work. Therefore we try that one in case it helps.
</para></listitem>
</varlistentry>
+<varlistentry id="XFRIN_XFR_TRANSFER_PROTOCOL_ERROR">
+<term>XFRIN_XFR_TRANSFER_PROTOCOL_ERROR %1 transfer of zone %2 with %3 failed: %4</term>
+<listitem><para>
+The XFR transfer for the given zone has failed due to a protocol
+error, such as an unexpected response from the primary server. The
+error is shown in the log message. It may be because the primary
+server implementation is broken or (although less likely) there was
+some attack attempt, but it can also happen due to configuration
+mismatch such as the remote server does not have authority for the
+zone any more but the local configuration hasn't been updated. So it
+is recommended to check the primary server configuration.
+</para></listitem>
+</varlistentry>
+
<varlistentry id="XFRIN_XFR_TRANSFER_STARTED">
<term>XFRIN_XFR_TRANSFER_STARTED %1 transfer of zone %2 started</term>
<listitem><para>
@@ -4819,6 +5266,62 @@ The XFR transfer of the given zone was successfully completed.
</para></listitem>
</varlistentry>
+<varlistentry id="XFRIN_ZONE_CREATED">
+<term>XFRIN_ZONE_CREATED Zone %1 not found in the given data source, newly created</term>
+<listitem><para>
+On starting an xfrin session, it is identified that the zone to be
+transferred is not found in the data source. This can happen if a
+secondary DNS server first tries to perform AXFR from a primary server
+without creating the zone image beforehand (e.g. by b10-loadzone). As
+of this writing the xfrin process provides backward compatible
+behavior to previous versions: creating a new one in the data source
+not to surprise existing users too much. This is probably not a good
+idea, however, in terms of who should be responsible for managing
+zones at a higher level. In future it is more likely that a separate
+zone management framework is provided, and the situation where the
+given zone isn't found in xfrout will be treated as an error.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="XFRIN_ZONE_MULTIPLE_SOA">
+<term>XFRIN_ZONE_MULTIPLE_SOA Zone %1 has %2 SOA RRs</term>
+<listitem><para>
+On starting an xfrin session, it is identified that the zone to be
+transferred has multiple SOA RRs. Such a zone is broken, but could be
+accidentally configured especially in a data source using "non
+captive" backend database. The implementation ignores entire SOA RRs
+and tries to continue processing as if the zone were empty. This
+means subsequent AXFR can succeed and possibly replace the zone with
+valid content, but an IXFR attempt will fail.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="XFRIN_ZONE_NO_SOA">
+<term>XFRIN_ZONE_NO_SOA Zone %1 does not have SOA</term>
+<listitem><para>
+On starting an xfrin session, it is identified that the zone to be
+transferred does not have an SOA RR in the data source. This is not
+necessarily an error; if a secondary DNS server first tries to perform
+transfer from a primary server, the zone can be empty, and therefore
+doesn't have an SOA. Subsequent AXFR will fill in the zone; if the
+attempt is IXFR it will fail in query creation.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="XFRIN_ZONE_SERIAL_AHEAD">
+<term>XFRIN_ZONE_SERIAL_AHEAD Serial number (%1) for %2 received from master %3 < ours (%4)</term>
+<listitem><para>
+The response to an SOA query prior to xfr indicated that the zone's
+SOA serial at the primary server is smaller than that of the xfrin
+client. This is not necessarily an error especially if that
+particular primary server is another secondary server which hasn't got
+the latest version of the zone. But if the primary server is known to
+be the real source of the zone, some unexpected inconsistency may have
+happened, and you may want to take a closer look. In this case xfrin
+doesn't perform subsequent zone transfer.
+</para></listitem>
+</varlistentry>
+
<varlistentry id="XFROUT_BAD_TSIG_KEY_STRING">
<term>XFROUT_BAD_TSIG_KEY_STRING bad TSIG key string: %1</term>
<listitem><para>
More information about the bind10-changes
mailing list