From: Jeremy C. Reed Date: Thu, 16 Feb 2012 16:39:01 +0000 (-0600) Subject: [trac1687] remove generated guide and message documentation files X-Git-Tag: trac2351_base~97^2~29 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=878bed3207150a3a006eecba1c30292fbf22cda6;p=thirdparty%2Fkea.git [trac1687] remove generated guide and message documentation files Later steps will make sure these are generated for "make dist" to be included in tarball. --- diff --git a/doc/guide/bind10-guide.html b/doc/guide/bind10-guide.html deleted file mode 100644 index 4ae31f57cc..0000000000 --- a/doc/guide/bind10-guide.html +++ /dev/null @@ -1,1631 +0,0 @@ -BIND 10 Guide

BIND 10 Guide

Administrator Reference for BIND 10

This is the reference guide for BIND 10 version - 20120127.

Copyright © 2010-2012 Internet Systems Consortium, Inc.

Abstract

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 20120127. - 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. -

Table of Contents

Preface
1. Acknowledgements
1. Introduction
1.1. Supported Platforms
1.2. Required Software
1.3. Starting and Stopping the Server
1.4. Managing BIND 10
2. Installation
2.1. Building Requirements
2.2. Quick start
2.3. Installation from source
2.3.1. Download Tar File
2.3.2. Retrieve from Git
2.3.3. Configure before the build
2.3.4. Build
2.3.5. Install
2.3.6. Install Hierarchy
3. Starting BIND10 with bind10
3.1. Starting BIND 10
3.2. Configuration of started processes
4. Command channel
5. Configuration manager
6. Remote control daemon
6.1. Configuration specification for b10-cmdctl
7. Control and configure user interface
8. Authoritative Server
8.1. Server Configurations
8.2. Data Source Backends
8.3. Loading Master Zones Files
9. Incoming Zone Transfers
9.1. Configuration for Incoming Zone Transfers
9.2. Enabling IXFR
9.3. Secondary Manager
9.4. Trigger an Incoming Zone Transfer Manually
10. Outbound Zone Transfers
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
13.4. DHCPv6 Server Limitations
14. libdhcp++ library
14.1. Interface detection
14.2. DHCPv4/DHCPv6 packet handling
15. Statistics
16. Logging
16.1. Logging configuration
16.1.1. Loggers
16.1.2. Output Options
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

1.1. Supported Platforms
1.2. Required Software
1.3. Starting and Stopping the Server
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. - BIND 10 provides a EDNS0- and DNSSEC-capable authoritative - DNS server and a caching recursive name server which also - provides forwarding. -

- This guide covers the experimental prototype of - BIND 10 version 20120127. -

1.1. 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. -

1.2. 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 uses the Botan crypto library for C++ - (http://botan.randombit.net/). - 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. -

- The authoritative DNS server uses SQLite3 - (http://www.sqlite.org/). - - It needs at least SQLite version 3.3.9. -

- 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

- Some operating systems do not provide these dependencies - in their default installation nor standard packages - collections. - You may need to install them separately. -

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. This is a change from - the previous generation of BIND software, which used a - single process. -

- At first, running many different processes may seem confusing. - However, these processes are started, stopped, and maintained - by a single command, bind10. - This command starts a master process which will start other - processes as needed. - The processes started by the bind10 - command have names starting with "b10-", including: -

- -

  • - b10-msgq — - Message bus daemon. - This process coordinates communication between all of the other - BIND 10 processes. -
  • - b10-auth — - Authoritative DNS server. - This process serves DNS requests. -
  • - b10-cfgmgr — - Configuration manager. - This process maintains all of the configuration for BIND 10. -
  • - b10-cmdctl — - Command and control service. - This process allows external control of the BIND 10 system. -
  • - b10-resolver — - Recursive name server. - This process handles incoming queries. - -
  • - b10-stats — - Statistics collection daemon. - This process collects and reports statistics data. -
  • - b10-xfrin — - Incoming zone transfer service. - This process is used to transfer a new copy - of a zone into BIND 10, when acting as a secondary server. -
  • - b10-xfrout — - Outgoing zone transfer service. - This process is used to handle transfer requests to - send a local zone to a remote secondary server, - when acting as a master server. -
  • - b10-zonemgr — - Secondary manager. - This process keeps track of timers and other - necessary information for BIND 10 to act as a slave server. -

-

- These are ran automatically by bind10 - and do not need to be run manually. -

1.4. Managing BIND 10

- Once BIND 10 is running, a few commands are used to interact - directly with the system: -

  • - bindctl — - interactive administration interface. - This is a command-line tool which allows an administrator - to control BIND 10. -
  • - b10-loadzone — - zone file loader. - This tool will load standard masterfile-format zone files into - BIND 10. -
  • - b10-cmdctl-usermgr — - user access control. - This tool allows an administrator to authorize additional users - to manage BIND 10. -

-

- The tools and modules are covered in full detail in this guide. - - In addition, manual pages are also provided in the default installation. -

- BIND 10 also provides libraries and programmer interfaces - for C++ and Python for the message bus, configuration backend, - and, of course, DNS. These include detailed developer - documentation and code examples. - -

Chapter 2. Installation

Table of Contents

2.1. Building Requirements
2.2. Quick start
2.3. Installation from source
2.3.1. Download Tar File
2.3.2. Retrieve from Git
2.3.3. Configure before the build
2.3.4. Build
2.3.5. Install
2.3.6. Install Hierarchy

2.1. Building Requirements

- In addition to the run-time requirements, building BIND 10 - from source code requires various development include headers. -

Note

- Some operating systems have split their distribution packages into - a run-time and a development package. You will need to install - the 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 - (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. -

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

- Visit the wiki at http://bind10.isc.org/wiki/SystemSpecificNotes - for system-specific installation tips. -

2.2. Quick start

Note

- This quickly covers the standard steps for installing - and deploying BIND 10 as an authoritative name server using - its defaults. For troubleshooting, full customizations and further - details, see the respective chapters in the BIND 10 guide. -

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

  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: - 

    $ gzcat bind10-VERSION.tar.gz | tar -xvf -

    -

  4. Go into the source and run configure: - 

    $ cd bind10-VERSION
-  $ ./configure

    -

  5. Build it: - 

    $ make

    -

  6. Install it (to default /usr/local): - 

    $ make install

    -

  7. Start the server: - 

    $ /usr/local/sbin/bind10

    -

  8. Test it; for example: - 

    $ dig @127.0.0.1 -c CH -t TXT authors.bind

    -

  9. Load desired zone file(s), for example: - 

    $ b10-loadzone your.zone.example.org

    -

  10. - Test the new zone. -

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

2.3.1. Download Tar File

- Downloading a release tar file is the recommended method to - obtain the source code. -

- The BIND 10 releases are available as tar file downloads from - ftp://ftp.isc.org/isc/bind10/. - Periodic development snapshots may also be available. -

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 not recommended. -

Note

- When using source code retrieved via Git additional - software will be required: automake (v1.11 or newer), - libtoolize, and autoconf (2.59 or newer). - These may need to be installed. -

- The latest development code, including temporary experiments - and un-reviewed code, is available via the BIND 10 code revision - control system. This is powered by Git and all the BIND 10 - development is public. - The leading development is done in the “master”. -

- The code can be checked out from - git://git.bind10.isc.org/bind10; - for example: - - 

$ git clone git://git.bind10.isc.org/bind10

-

- When checking out the code from - the code version control system, it doesn't include the - generated configure script, Makefile.in files, nor the - related configure files. - They can be created by running autoreconf - with the --install switch. - This will run autoconf, - aclocal, - libtoolize, - autoheader, - automake, - and related commands. -

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: - 

$ ./configure

-

- Run ./configure with the --help - switch to view the different options. The commonly-used options are: - -

--prefix
Define the installation location (the - default is /usr/local/). -
--with-boost-include
Define the path to find the Boost headers. -
--with-pythonpath
Define the path to Python 3.1 if it is not in the - standard execution path. -
--with-gtest
Enable building the C++ Unit Tests using the - Google Tests framework. Optionally this can define the - path to the gtest header files and library. -

- -

- For example, the following configures it to - find the Boost headers, find the - Python interpreter, and sets the installation location: - - 

$ ./configure \
-      --with-boost-include=/usr/pkg/include \
-      --with-pythonpath=/usr/pkg/bin/python3.1 \
-      --prefix=/opt/bind10

-

- If the configure fails, it may be due to missing or old - dependencies. -

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

-

2.3.5. Install

- To install the BIND 10 executables, support files, - and documentation, run: - 

$ make install

-

Note

The install step may require superuser privileges.

2.3.6. Install Hierarchy

- The following is the layout of the complete BIND 10 installation: -

  • - bin/ — - general tools and diagnostic clients. -
  • - etc/bind10-devel/ — - configuration files. -
  • - lib/ — - libraries and python modules. -
  • - libexec/bind10-devel/ — - executables that a user wouldn't normally run directly and - are not run independently. - These are the BIND 10 modules which are daemons started by - the bind10 tool. -
  • - sbin/ — - commands used by the system administrator. -
  • - share/bind10-devel/ — - configuration specifications. -
  • - share/man/ — - manual pages (online documentation). -
  • - var/bind10-devel/ — - data source and configuration databases. -

-

Chapter 3. Starting BIND10 with bind10

Table of Contents

3.1. Starting BIND 10
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. - This is the only command needed to start the BIND 10 system. -

- After starting the b10-msgq communications channel, - bind10 connects to it, - runs the configuration manager, and reads its own configuration. - Then it starts the other modules. -

- The b10-sockcreator, b10-msgq and - b10-cfgmgr - services make up the core. The b10-msgq daemon - provides the communication channel between every part of the system. - The b10-cfgmgr daemon is always needed by every - module, if only to send information about themselves somewhere, - but more importantly to ask about their own settings, and - about other modules. The b10-sockcreator will - allocate sockets for the rest of the system. -

- In its default configuration, the bind10 - master process will also start up - b10-cmdctl for admins to communicate with the - system, b10-auth for authoritative DNS service, - b10-stats for statistics collection, - b10-xfrin for inbound DNS zone transfers, - b10-xfrout for outbound DNS zone transfers, - and b10-zonemgr for secondary service. -

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

Note

- If the setproctitle Python module is detected at start up, - the process names for the Python-based daemons will be renamed - to better identify them instead of just “python”. - This is not needed on some operating systems. -

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

- The configuration is in the Boss/components section. Each element - represents one component, which is an abstraction of a process - (currently there's also one component which doesn't represent - a process). If you didn't want to transfer out at all (your server - is a slave only), you would just remove the corresponding component - from the set, like this and the process would be stopped immediately - (and not started on the next startup): - 

> config remove Boss/components b10-xfrout
-> config commit

-

- To add a process to the set, let's say the resolver (which not started - by default), you would do this: - 

> config add Boss/components b10-resolver
-> config set Boss/components/b10-resolver/special resolver
-> config set Boss/components/b10-resolver/kind needed
-> config set Boss/components/b10-resolver/priority 10
-> config commit

- Now, what it means. We add an entry called b10-resolver. It is both a - name used to reference this component in the configuration and the - name of the process to start. Then we set some parameters on how to - start it. -

- The special one is for components that need some kind of special care - 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: -

Table 3.1. 

ComponentSpecialDescription
b10-authauthAuthoritative server
b10-resolverresolverThe resolver
b10-cmdctlcmdctlThe command control (remote control interface)


-

- The kind specifies how a failure of the component should - be handled. If it is set to “dispensable” - (the default unless you set something else), it will get - started again if it fails. If it is set to “needed” - and it fails at startup, the whole bind10 - shuts down and exits with error exit code. But if it fails - some time later, it is just started again. If you set it - to “core”, you indicate that the system is - not usable without the component and if such component - fails, the system shuts down no matter when the failure - happened. This is the behaviour of the core components - (the ones you can't turn off), but you can declare any - other components as core as well if you wish (but you can - turn these off, they just can't fail). -

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

- 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 bus. The special components already know their - address, but the usual ones don't. The address is by - convention the thing after b10-, with - the first letter capital (eg. b10-stats - would have “Stats” as its address). - -

- The last one is process. It is the name of the process to be started. - It defaults to the name of the component if not set, but you can use - this to override it. -

Note

- This system allows you to start the same component multiple times - (by including it in the configuration with different names, but the - same process setting). However, the rest of the system doesn't expect - such situation, so it would probably not do what you want. Such - support is yet to be implemented. -

Note

- The configuration is quite powerful, but that includes - a lot of space for mistakes. You could turn off the - b10-cmdctl, but then you couldn't - change it back the usual way, as it would require it to - be running (you would have to find and edit the configuration - directly). Also, some modules might have dependencies - -- b10-stats-httpd need - b10-stats, b10-xfrout - needs the b10-auth to be running, etc. - - - -

- In short, you should think twice before disabling something here. -

- It is possible to start some components multiple times (currently - b10-auth and b10-resolzer). - You might want to do that to gain more performance (each one uses only - single core). Just put multiple entries under different names, like - this, with the same config: - 

> config add Boss/components b10-resolver-2
-> config set Boss/components/b10-resolver-2/special resolver
-> config set Boss/components/b10-resolver-2/kind needed
-> config commit

-

- However, this is work in progress and the support is not yet complete. - For example, each resolver will have its own cache, each authoritative - server will keep its own copy of in-memory data and there could be - problems with locking the sqlite database, if used. The configuration - might be changed to something more convenient in future. -

Chapter 4. Command channel

- The BIND 10 components use the b10-msgq - message routing daemon to communicate with other BIND 10 components. - The b10-msgq implements what is called the - “Command Channel”. - Processes intercommunicate by sending messages on the command - channel. - Example messages include shutdown, get configurations, and set - configurations. - This Command Channel is not used for DNS message passing. - It is used only to control and monitor the BIND 10 system. -

- Administrators do not communicate directly with the - b10-msgq daemon. - By default, BIND 10 uses port 9912 for the - b10-msgq service. - It listens on 127.0.0.1. -

Chapter 5. Configuration manager

- The configuration manager, b10-cfgmgr, - handles all BIND 10 system configuration. It provides - persistent storage for configuration, and notifies running - modules of configuration changes. -

- The b10-auth and b10-xfrin - daemons and other components receive their configurations - from the configuration manager over the b10-msgq - command channel. -

The administrator doesn't connect to it directly, but - uses a user interface to communicate with the configuration - manager via b10-cmdctl's REST-ful interface. - b10-cmdctl is covered in Chapter 6, Remote control daemon. -

Note

- The development prototype release only provides the - bindctl as a user interface to - b10-cmdctl. - Upcoming releases will provide another interactive command-line - interface and a web-based interface. -

- The b10-cfgmgr daemon can send all - specifications and all current settings to the - bindctl client (via - b10-cmdctl). -

- b10-cfgmgr relays configurations received - from b10-cmdctl to the appropriate modules. -

- The stored configuration file is at - /usr/local/var/bind10-devel/b10-config.db. - (The full path is what was defined at build configure time for - --localstatedir. - The default is /usr/local/var/.) - The format is loosely based on JSON and is directly parseable - python, but this may change in a future version. - This configuration data file is not manually edited by the - administrator. -

- The configuration manager does not have any command line arguments. - Normally it is not started manually, but is automatically - started using the bind10 master process - (as covered in Chapter 3, Starting BIND10 with bind10). -

Chapter 6. Remote control daemon

Table of Contents

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 username and password validation. - It provides a REST-ful interface for accessing and controlling - BIND 10. -

- When b10-cmdctl starts, it firsts - asks b10-cfgmgr about what modules are - running and what their configuration is (over the - b10-msgq channel). Then it will start listening - on HTTPS for clients — the user interface — such - as bindctl. -

- b10-cmdctl directly sends commands - (received from the user interface) to the specified component. - Configuration changes are actually commands to - b10-cfgmgr so are sent there. -

The HTTPS server requires a private key, - such as a RSA PRIVATE KEY. - The default location is at - /usr/local/etc/bind10-devel/cmdctl-keyfile.pem. - (A sample key is at - /usr/local/share/bind10-devel/cmdctl-keyfile.pem.) - It also uses a certificate located at - /usr/local/etc/bind10-devel/cmdctl-certfile.pem. - (A sample certificate is at - /usr/local/share/bind10-devel/cmdctl-certfile.pem.) - This may be a self-signed certificate or purchased from a - certification authority. -

Note

- The HTTPS server doesn't support a certificate request from a - client (at this time). - - The b10-cmdctl daemon does not provide a - public service. If any client wants to control BIND 10, then - a certificate needs to be first received from the BIND 10 - administrator. - The BIND 10 installation provides a sample PEM bundle that matches - the sample key and certificate. -

- The b10-cmdctl daemon also requires - the user account file located at - /usr/local/etc/bind10-devel/cmdctl-accounts.csv. - This comma-delimited file lists the accounts with a user name, - hashed password, and salt. - (A sample file is at - /usr/local/share/bind10-devel/cmdctl-accounts.csv. - It contains the user named “root” with the password - “bind10”.) -

- The administrator may create a user account with the - b10-cmdctl-usermgr tool. -

- By default the HTTPS server listens on the localhost port 8080. - The port can be set by using the --port command line option. - The address to listen on can be set using the --address command - line argument. - Each HTTPS connection is stateless and timesout in 1200 seconds - by default. This can be - redefined by using the --idle-timeout command line argument. -

6.1. Configuration specification for b10-cmdctl

- The configuration items for b10-cmdctl are: -key_file -cert_file -accounts_file -

- The control commands are: -print_settings - - -shutdown -

Chapter 7. Control and configure user interface

Note

- For this development prototype release, bindctl - is the only user interface. It is expected that upcoming - releases will provide another interactive command-line - interface and a web-based interface for controlling and - configuring BIND 10. -

- The bindctl tool provides an interactive - prompt for configuring, controlling, and querying the BIND 10 - components. - It communicates directly with a REST-ful interface over HTTPS - provided by b10-cmdctl. It doesn't - communicate to any other components directly. -

- Configuration changes are actually commands to - b10-cfgmgr. So when bindctl - sends a configuration, it is sent to b10-cmdctl - (over a HTTPS connection); then b10-cmdctl - sends the command (over a b10-msgq command - channel) to b10-cfgmgr which then stores - the details and relays (over a b10-msgq command - channel) the configuration on to the specified module. -

-

Chapter 8. Authoritative Server

Table of Contents

8.1. Server Configurations
8.2. Data Source Backends
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. -

8.1. Server Configurations

- b10-auth is configured via the - b10-cfgmgr configuration manager. - The module name is “Auth”. - The configuration data item is: - -

database_file
This is an optional string to define the path to find - the SQLite3 database file. - -Note: Later the DNS server will use various data source backends. -This may be a temporary setting until then. -

- -

- - The configuration command is: - -

shutdown
Stop the authoritative DNS server. -

- -

8.2. Data Source Backends

Note

- For the development prototype release, b10-auth - supports a SQLite3 data source backend and in-memory data source - backend. - Upcoming versions will be able to use multiple different - data sources, such as MySQL and Berkeley DB. -

- By default, the SQLite3 backend uses the data file located at - /usr/local/var/bind10-devel/zone.sqlite3. - (The full path is what was defined at build configure time for - --localstatedir. - The default is /usr/local/var/.) - This data file location may be changed by defining the - “database_file” configuration. -

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

- b10-loadzone supports the following - special directives (control entries): - -

$INCLUDE
Loads an additional zone file. This may be recursive. -
$ORIGIN
Defines the relative domain name. -
$TTL
Defines the time-to-live value used for following - records that don't include a TTL. -

- -

- The -o argument may be used to define the - default origin for loaded zone file records. -

Note

- In the development prototype release, only the SQLite3 back - end is used. - By default, it stores the zone data in - /usr/local/var/bind10-devel/zone.sqlite3 - unless the -d switch is used to set the - database filename. - Multiple zones are stored in a single SQLite3 zone database. -

- If you reload a zone already existing in the database, - all records from that prior zone disappear and a whole new set - appears. -

Chapter 9. Incoming Zone Transfers

Table of Contents

9.1. Configuration for Incoming Zone Transfers
9.2. Enabling IXFR
9.3. Secondary Manager
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 BIND 10 - data source, and its records can be served by - b10-auth. - In combination with b10-zonemgr (for - automated SOA checks), this allows the BIND 10 server to - provide “secondary” service. -

- The b10-xfrin process supports both AXFR and - IXFR. Due to some implementation limitations of the current - development release, however, it only tries AXFR by default, - and care should be taken to enable IXFR. -

Note

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

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 transfer manually, without a prior configuration - (see below)). -

- For example, to enable zone transfers for a zone named "example.com" - (whose master address is assumed to be 2001:db8::53 here), - run the following at the bindctl prompt: - - 

> config add Xfrin/zones
-> config set Xfrin/zones[0]/name "example.com"
-> config set Xfrin/zones[0]/master_addr "2001:db8::53"
-> config commit

- - (We assume there has been no zone configuration before). -

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 - configuration parameter to true. - In the above example of configuration sequence, you'll need - to add the following before performing commit: - 

> config set Xfrin/zones[0]/use_ixfr true

-

Note

- One reason why IXFR is disabled by default in the current - release is because it does not support automatic fallback from IXFR to - AXFR when it encounters a primary server that doesn't support - outbound IXFR (and, not many existing implementations support - it). Another, related reason is that it does not use AXFR even - if it has no knowledge about the zone (like at the very first - time the secondary server is set up). IXFR requires the - "current version" of the zone, so obviously it doesn't work - in this situation and AXFR is the only workable choice. - The current release of b10-xfrin does not - make this selection automatically. - These features will be implemented in a near future - version, at which point we will enable IXFR by default. -

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: - - 

> Xfrin retransfer zone_name="foo.example.org" master=192.0.2.99

-

Chapter 10. Outbound Zone Transfers

- The b10-xfrout process is started by - bind10. - When the b10-auth authoritative DNS server - receives an AXFR or IXFR request, b10-auth - internally forwards the request to b10-xfrout, - which handles the rest of request processing. - This is used to provide primary DNS service to share zones - to secondary name servers. - The b10-xfrout is also used to send - NOTIFY messages to secondary servers. -

- A global or per zone transfer_acl configuration - can be used to control accessibility of the outbound zone - transfer service. - By default, b10-xfrout allows any clients to - perform zone transfers for any zones: - 

> config show Xfrout/transfer_acl
-Xfrout/transfer_acl[0]	{"action": "ACCEPT"}	any	(default)

- You can change this to, for example, rejecting all transfer - requests by default while allowing requests for the transfer - of zone "example.com" from 192.0.2.1 and 2001:db8::1 as follows: - 

> config set Xfrout/transfer_acl[0] {"action": "REJECT"}
-> config add Xfrout/zone_config
-> config set Xfrout/zone_config[0]/origin "example.com"
-> config set Xfrout/zone_config[0]/transfer_acl [{"action": "ACCEPT", "from": "192.0.2.1"},
-                                                 {"action": "ACCEPT", "from": "2001:db8::1"}]
-> config commit

Note

- In the above example the lines - for transfer_acl were divided for - readability. In the actual input it must be in a single line. -

- If you want to require TSIG in access control, a separate TSIG - "key ring" must be configured specifically - for b10-xfrout as well as a system wide - key ring, both containing a consistent set of keys. - For example, to change the previous example to allowing requests - from 192.0.2.1 signed by a TSIG with a key name of - "key.example", you'll need to do this: - 

> config set tsig_keys/keys ["key.example:<base64-key>"]
-> config set Xfrout/tsig_keys/keys ["key.example:<base64-key>"]
-> config set Xfrout/zone_config[0]/transfer_acl [{"action": "ACCEPT", "from": "192.0.2.1", "key": "key.example"}]
-> config commit

- The first line of configuration defines a system wide key ring. - This is necessary because the b10-auth server - also checks TSIGs and it uses the system wide configuration. -

Note

- In a future version, b10-xfrout will also - use the system wide TSIG configuration. - The way to specify zone specific configuration (ACLs, etc) is - likely to be changed, too. -

Chapter 11. Recursive Name Server

Table of Contents

11.1. Access Control
11.2. Forwarding

- The b10-resolver process is started by - bind10. - -

- The main bind10 process can be configured - to select to run either the authoritative or resolver or both. - By default, it starts the authoritative service. - - - You may change this using bindctl, for example: - - 

-> config remove Boss/components b10-xfrout
-> config remove Boss/components b10-xfrin
-> config remove Boss/components b10-auth
-> config add Boss/components b10-resolver
-> config set Boss/components/b10-resolver/special resolver
-> config set Boss/components/b10-resolver/kind needed
-> config set Boss/components/b10-resolver/priority 10
-> config commit
-

- -

- The master bind10 will stop and start - the desired services. -

- By default, the resolver listens on port 53 for 127.0.0.1 and ::1. - The following example shows how it can be configured to - listen on an additional address (and port): - - 

-> config add Resolver/listen_on
-> config set Resolver/listen_on[2]/address "192.168.1.1"
-> config set Resolver/listen_on[2]/port 53
-> config commit
-

-

(Replace the “2” - as needed; run “config show - Resolver/listen_on” if needed.)

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 used to reject, drop, or allow specific IPs or networks. - This configuration list is first match. -

- The configuration's action item may be - set to “ACCEPT” to allow the incoming query, - “REJECT” to respond with a DNS REFUSED return - code, or “DROP” to ignore the query without - any response (such as a blackhole). For more information, - see the respective debugging messages: RESOLVER_QUERY_ACCEPTED, - RESOLVER_QUERY_REJECTED, - and RESOLVER_QUERY_DROPPED. -

- The required configuration's from item is set - to an IPv4 or IPv6 address, addresses with an network mask, or to - the special lowercase keywords “any6” (for - any IPv6 address) or “any4” (for any IPv4 - address). -

- For example to allow the 192.168.1.0/24 - network to use your recursive name server, at the - bindctl prompt run: - 

-> config add Resolver/query_acl
-> config set Resolver/query_acl[2]/action "ACCEPT"
-> config set Resolver/query_acl[2]/from "192.168.1.0/24"
-> config commit
-

(Replace the “2” - as needed; run “config show - Resolver/query_acl” if needed.)

Note

This prototype access control configuration - syntax may be changed.

11.2. Forwarding

- - To enable forwarding, the upstream address and port must be - configured to forward queries to, such as: - - 

-> config set Resolver/forward_addresses [{ "address": "192.168.1.1", "port": 53 }]
-> config commit
-

- - (Replace 192.168.1.1 to point to your - full resolver.) -

- Normal iterative name service can be re-enabled by clearing the - forwarding address(es); for example: - - 

-> config set Resolver/forward_addresses []
-> config commit
-

-

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:

  • RFC2131: Supported messages are DISCOVER, OFFER, - REQUEST, and ACK.
  • 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.

  • 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).
  • 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.
  • 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.
  • 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.
  • PRL (Parameter Request List, a list of options - requested by a client) is currently ignored and server - assigns DNS SERVER and DOMAIN NAME options.
  • 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.
  • Interface detection is currently working on Linux - only. See Section 14.1, “Interface detection” for details.
  • 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.
  • Address renewal (RENEW), rebinding (REBIND), - confirmation (CONFIRM), duplication report (DECLINE) and - release (RELEASE) are not supported yet.
  • DNS Update is not supported yet.
  • -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:

  • RFC3315: Supported messages are SOLICIT, - ADVERTISE, REQUEST, and REPLY. Supported options are - SERVER_ID, CLIENT_ID, IA_NA, and IAADDRESS.
  • 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.

-

  • Relayed traffic is not supported.
  • 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.
  • 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.
  • 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.
  • ORO (Option Request Option, a list of options - requested by a client) is currently ignored and server - assigns DNS SERVER option.
  • Temporary addresses are not supported yet.
  • Prefix delegation is not supported yet.
  • Address renewal (RENEW), rebinding (REBIND), - confirmation (CONFIRM), duplication report (DECLINE) and - release (RELEASE) are not supported yet.
  • DNS Update is not supported yet.
  • Interface detection is currently working on Linux - only. See Section 14.1, “Interface detection” for details.
  • -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. - -

- - This stats daemon provides commands to identify if it is - running, show specified or all statistics data, show specified - or all statistics data schema, and set specified statistics - data. - - For example, using bindctl: - - 

-> Stats show
-{
-    "Auth": {
-        "opcode.iquery": 0,
-        "opcode.notify": 10,
-        "opcode.query": 869617,
-        ...
-        "queries.tcp": 1749,
-        "queries.udp": 867868
-    },
-    "Boss": {
-        "boot_time": "2011-01-20T16:59:03Z"
-    },
-    "Stats": {
-        "boot_time": "2011-01-20T16:59:05Z",
-        "last_update_time": "2011-01-20T17:04:05Z",
-        "lname": "4d3869d9_a@jreed.example.net",
-        "report_time": "2011-01-20T17:04:06Z",
-        "timestamp": 1295543046.823504
-    }
-}
-

-

Chapter 16. Logging

Table of Contents

16.1. Logging configuration
16.1.1. Loggers
16.1.2. Output Options
16.1.3. Example session
16.2. Logging Message Format

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

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 each logger can be configured - independently of one another. - -

- - In the Logging module, you can specify the configuration - for zero or more loggers; any that are not specified will - take appropriate default values.. - -

- - The three most important elements of a logger configuration - are the name (the component that is - generating the messages), the severity - (what to log), and the output_options - (where to log). - -

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 for the resolver module, - you add an entry for a logger named “Resolver”. This - configuration will then be used by the loggers in the - Resolver module, and all the libraries used by it. -

- - If you want to specify logging for one specific library - within the module, you set the name to - module.library. For example, the - logger used by the nameserver address store component - has the full name of “Resolver.nsas”. If - there is no entry in Logging for a particular library, - it will use the configuration given for the module. - - - -

- - - - To illustrate this, suppose you want the cache library - to log messages of severity DEBUG, and the rest of the - resolver code to log messages of severity INFO. To achieve - this you specify two loggers, one with the name - “Resolver” and severity INFO, and one with - the name “Resolver.cache” with severity - DEBUG. As there are no entries for other libraries (e.g. - the nsas), they will use the configuration for the module - (“Resolver”), so giving the desired behavior. - -

- - One special case is that of a module name of “*” - (asterisks), which is interpreted as any - module. You can set global logging options by using this, - including setting the logging configuration for a library - that is used by multiple modules (e.g. “*.config” - specifies the configuration library code in whatever - module is using it). - -

- - If there are multiple logger specifications in the - configuration that might match a particular logger, the - specification with the more specific logger name takes - precedence. For example, if there are entries for for - both “*” and “Resolver”, the - resolver module — and all libraries it uses — - will log messages according to the configuration in the - second entry (“Resolver”). All other modules - will use the configuration of the first entry - (“*”). If there was also a configuration - entry for “Resolver.cache”, the cache library - within the resolver would use that in preference to the - entry for “Resolver”. - -

- - One final note about the naming. When specifying the - module name within a logger, use the name of the module - as specified in bindctl, e.g. - “Resolver” for the resolver module, - “Xfrout” for the xfrout module, etc. When - the message is logged, the message will include the name - of the logger generating the message, but with the module - name replaced by the name of the process implementing - the module (so for example, a message generated by the - “Auth.cache” logger will appear in the output - with a logger name of “b10-auth.cache”). - -

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 descending order of - severity): -

  • FATAL
  • ERROR
  • WARN
  • INFO
  • DEBUG

- - When the severity of a logger is set to one of these - values, it will only log messages of that severity, and - the severities above it. The severity may also be set to - NONE, in which case all messages from that logger are - inhibited. - - - -

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: - -

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 verbose). -

- - If severity for the logger is not DEBUG, this value is ignored. - -

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 - “Resolver.cache”, and additive - is true in the second, it will write the log messages - not only to the destinations specified for - “Resolver.cache”, but also to the destinations - as specified in the output_options in - the logger named “Resolver”. - - - -

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

16.1.2.1. destination (string)

- - The destination is the type of output. It can be one of: - -

  • console
  • file
  • syslog

16.1.2.2. output (string)

- - Depending on what is set as the output destination, this - value is interpreted as follows: - -

destination is “console”
- The value of output must be one of “stdout” - (messages printed to standard output) or - “stderr” (messages printed to standard - error). -
destination is “file”
- The value of output is interpreted as a file name; - log messages will be appended to this file. -
destination is “syslog”
- The value of output is interpreted as the - syslog facility (e.g. - local0) that should be used - for log messages. -

- - The other options for output_options are: - -

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

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 renamed and a new file opened. - (For example, a ".1" is appended to the name — - if a ".1" file exists, it is renamed ".2", - etc.) -

- If this is 0, no maximum file size is used. -

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”. -

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 to - log at DEBUG with debuglevel 40, to a different file - (/tmp/debug_messages). - -

- - Start bindctl. - -

- - 

["login success "]
-> config show Logging
-Logging/loggers	[]	list
-

- -

- - By default, no specific loggers are configured, in which - case the severity defaults to INFO and the output is - written to stderr. - -

- - Let's first add a default logger: - -

- - 

> config add Logging/loggers
-> config show Logging
-Logging/loggers/	list	(modified)
-

- -

- - The loggers value line changed to indicate that it is no - longer an empty list: - -

- - 

> config show Logging/loggers
-Logging/loggers[0]/name	""	string	(default)
-Logging/loggers[0]/severity	"INFO"	string	(default)
-Logging/loggers[0]/debuglevel	0	integer	(default)
-Logging/loggers[0]/additive	false	boolean	(default)
-Logging/loggers[0]/output_options	[]	list	(default)
-

- -

- - The name is mandatory, so we must set it. We will also - change the severity as well. Let's start with the global - logger. - -

- - 

> config set Logging/loggers[0]/name *
-> config set Logging/loggers[0]/severity WARN
-> config show Logging/loggers
-Logging/loggers[0]/name	"*"	string	(modified)
-Logging/loggers[0]/severity	"WARN"	string	(modified)
-Logging/loggers[0]/debuglevel	0	integer	(default)
-Logging/loggers[0]/additive	false	boolean	(default)
-Logging/loggers[0]/output_options	[]	list	(default)
-

- -

- - Of course, we need to specify where we want the log - messages to go, so we add an entry for an output option. - -

- - 

>  config add Logging/loggers[0]/output_options
->  config show Logging/loggers[0]/output_options
-Logging/loggers[0]/output_options[0]/destination	"console"	string	(default)
-Logging/loggers[0]/output_options[0]/output	"stdout"	string	(default)
-Logging/loggers[0]/output_options[0]/flush	false	boolean	(default)
-Logging/loggers[0]/output_options[0]/maxsize	0	integer	(default)
-Logging/loggers[0]/output_options[0]/maxver	0	integer	(default)
-

- - -

- - These aren't the values we are looking for. - -

- - 

>  config set Logging/loggers[0]/output_options[0]/destination file
->  config set Logging/loggers[0]/output_options[0]/output /var/log/bind10.log
->  config set Logging/loggers[0]/output_options[0]/maxsize 30000
->  config set Logging/loggers[0]/output_options[0]/maxver 8
-

- -

- - Which would make the entire configuration for this logger - look like: - -

- - 

>  config show all Logging/loggers
-Logging/loggers[0]/name	"*"	string	(modified)
-Logging/loggers[0]/severity	"WARN"	string	(modified)
-Logging/loggers[0]/debuglevel	0	integer	(default)
-Logging/loggers[0]/additive	false	boolean	(default)
-Logging/loggers[0]/output_options[0]/destination	"file"	string	(modified)
-Logging/loggers[0]/output_options[0]/output	"/var/log/bind10.log"	string	(modified)
-Logging/loggers[0]/output_options[0]/flush	false	boolean	(default)
-Logging/loggers[0]/output_options[0]/maxsize	30000	integer	(modified)
-Logging/loggers[0]/output_options[0]/maxver	8	integer	(modified)
-

- -

- - That looks OK, so let's commit it before we add the - configuration for the authoritative server's logger. - -

- - 

>  config commit

- -

- - Now that we have set it, and checked each value along - the way, adding a second entry is quite similar. - -

- - 

>  config add Logging/loggers
->  config set Logging/loggers[1]/name Auth
->  config set Logging/loggers[1]/severity DEBUG
->  config set Logging/loggers[1]/debuglevel 40
->  config add Logging/loggers[1]/output_options
->  config set Logging/loggers[1]/output_options[0]/destination file
->  config set Logging/loggers[1]/output_options[0]/output /tmp/auth_debug.log
->  config commit
-

- -

- - And that's it. Once we have found whatever it was we - needed the debug messages for, we can simply remove the - second logger to let the authoritative server use the - same settings as the rest. - -

- - 

>  config remove Logging/loggers[1]
->  config commit
-

- -

- - And every module will now be using the values from the - logger named “*”. - -

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 and, if the message indicates - a problem, information about the problem that may be - useful in fixing it. -

- Consider the message below logged to a file: - 

2011-06-15 13:48:22.034 ERROR [b10-resolver.asiolink]
-    ASIODNS_OPENSOCK error 111 opening TCP socket to 127.0.0.1(53)

-

- Note: the layout of messages written to the system logging - file (syslog) may be slightly different. This message has - been split across two lines here for display reasons; in the - logging file, it will appear on one line.) -

- The log message comprises a number of components: - -

2011-06-15 13:48:22.034

- The date and time at which the message was generated. -

ERROR

- The severity of the message. -

[b10-resolver.asiolink]

- The source of the message. This comprises two components: - the BIND 10 process generating the message (in this - case, b10-resolver) and the module - within the program from which the message originated - (which in the example is the asynchronous I/O link - module, asiolink). -

ASIODNS_OPENSOCK

- The message identification. Every message in BIND 10 - has a unique identification, which can be used as an - index into the BIND 10 Messages - Manual (http://bind10.isc.org/docs/bind10-messages.html) from which more information can be obtained. -

error 111 opening TCP socket to 127.0.0.1(53)

- A brief description of the cause of the problem. - Within this text, information relating to the condition - that caused the message to be logged will be included. - In this example, error number 111 (an operating - system-specific error number) was encountered when - trying to open a TCP connection to port 53 on the - local system (address 127.0.0.1). The next step - would be to find out the reason for the failure by - consulting your system's documentation to identify - what error number 111 means. -

-

diff --git a/doc/guide/bind10-guide.txt b/doc/guide/bind10-guide.txt deleted file mode 100644 index 7ec35e6da7..0000000000 --- a/doc/guide/bind10-guide.txt +++ /dev/null @@ -1,1726 +0,0 @@ - BIND 10 Guide - -Administrator Reference for BIND 10 - - This is the reference guide for BIND 10 version 20120127. - - Copyright (c) 2010-2012 Internet Systems Consortium, Inc. - - Abstract - - 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 20120127. 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. - - -------------------------------------------------------------------------- - - Table of Contents - - Preface - - 1. Acknowledgements - - 1. Introduction - - 1.1. Supported Platforms - - 1.2. Required Software - - 1.3. Starting and Stopping the Server - - 1.4. Managing BIND 10 - - 2. Installation - - 2.1. Building Requirements - - 2.2. Quick start - - 2.3. Installation from source - - 2.3.1. Download Tar File - - 2.3.2. Retrieve from Git - - 2.3.3. Configure before the build - - 2.3.4. Build - - 2.3.5. Install - - 2.3.6. Install Hierarchy - - 3. Starting BIND10 with bind10 - - 3.1. Starting BIND 10 - - 3.2. Configuration of started processes - - 4. Command channel - - 5. Configuration manager - - 6. Remote control daemon - - 6.1. Configuration specification for b10-cmdctl - - 7. Control and configure user interface - - 8. Authoritative Server - - 8.1. Server Configurations - - 8.2. Data Source Backends - - 8.3. Loading Master Zones Files - - 9. Incoming Zone Transfers - - 9.1. Configuration for Incoming Zone Transfers - - 9.2. Enabling IXFR - - 9.3. Secondary Manager - - 9.4. Trigger an Incoming Zone Transfer Manually - - 10. Outbound Zone Transfers - - 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 - - 13.4. DHCPv6 Server Limitations - - 14. libdhcp++ library - - 14.1. Interface detection - - 14.2. DHCPv4/DHCPv6 packet handling - - 15. Statistics - - 16. Logging - - 16.1. Logging configuration - - 16.1.1. Loggers - - 16.1.2. Output Options - - 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 - - 1.1. Supported Platforms - - 1.2. Required Software - - 1.3. Starting and Stopping the Server - - 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. BIND 10 provides a EDNS0- and DNSSEC-capable authoritative DNS server - and a caching recursive name server which also provides forwarding. - - This guide covers the experimental prototype of BIND 10 version 20120127. - -1.1. 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. - -1.2. 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 uses the Botan crypto library for C++ - (http://botan.randombit.net/). 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. - - The authoritative DNS server uses SQLite3 (http://www.sqlite.org/). It - needs at least SQLite version 3.3.9. - - 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 - - Some operating systems do not provide these dependencies in their default - installation nor standard packages collections. You may need to install - them separately. - -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. - This is a change from the previous generation of BIND software, which used - a single process. - - At first, running many different processes may seem confusing. However, - these processes are started, stopped, and maintained by a single command, - bind10. This command starts a master process which will start other - processes as needed. The processes started by the bind10 command have - names starting with "b10-", including: - - o b10-msgq -- Message bus daemon. This process coordinates communication - between all of the other BIND 10 processes. - o b10-auth -- Authoritative DNS server. This process serves DNS - requests. - o b10-cfgmgr -- Configuration manager. This process maintains all of the - configuration for BIND 10. - o b10-cmdctl -- Command and control service. This process allows - external control of the BIND 10 system. - o b10-resolver -- Recursive name server. This process handles incoming - queries. - o b10-stats -- Statistics collection daemon. This process collects and - reports statistics data. - o b10-xfrin -- Incoming zone transfer service. This process is used to - transfer a new copy of a zone into BIND 10, when acting as a secondary - server. - o b10-xfrout -- Outgoing zone transfer service. This process is used to - handle transfer requests to send a local zone to a remote secondary - server, when acting as a master server. - o b10-zonemgr -- Secondary manager. This process keeps track of timers - and other necessary information for BIND 10 to act as a slave server. - - These are ran automatically by bind10 and do not need to be run manually. - -1.4. Managing BIND 10 - - Once BIND 10 is running, a few commands are used to interact directly with - the system: - - o bindctl -- interactive administration interface. This is a - command-line tool which allows an administrator to control BIND 10. - o b10-loadzone -- zone file loader. This tool will load standard - masterfile-format zone files into BIND 10. - o b10-cmdctl-usermgr -- user access control. This tool allows an - administrator to authorize additional users to manage BIND 10. - - The tools and modules are covered in full detail in this guide. In - addition, manual pages are also provided in the default installation. - - BIND 10 also provides libraries and programmer interfaces for C++ and - Python for the message bus, configuration backend, and, of course, DNS. - These include detailed developer documentation and code examples. - -Chapter 2. Installation - - Table of Contents - - 2.1. Building Requirements - - 2.2. Quick start - - 2.3. Installation from source - - 2.3.1. Download Tar File - - 2.3.2. Retrieve from Git - - 2.3.3. Configure before the build - - 2.3.4. Build - - 2.3.5. Install - - 2.3.6. Install Hierarchy - -2.1. Building Requirements - - In addition to the run-time requirements, building BIND 10 from source - code requires various development include headers. - - Note - - Some operating systems have split their distribution packages into a - run-time and a development package. You will need to install the - 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 - (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. - - 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. - - Visit the wiki at http://bind10.isc.org/wiki/SystemSpecificNotes for - system-specific installation tips. - -2.2. Quick start - - Note - - This quickly covers the standard steps for installing and deploying BIND - 10 as an authoritative name server using its defaults. For - troubleshooting, full customizations and further details, see the - respective chapters in the BIND 10 guide. - - To quickly get started with BIND 10, follow these steps. - - 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: - - $ gzcat bind10-VERSION.tar.gz | tar -xvf - - - 4. Go into the source and run configure: - - $ cd bind10-VERSION - $ ./configure - - 5. Build it: - - $ make - - 6. Install it (to default /usr/local): - - $ make install - - 7. Start the server: - - $ /usr/local/sbin/bind10 - - 8. Test it; for example: - - $ dig @127.0.0.1 -c CH -t TXT authors.bind - - 9. Load desired zone file(s), for example: - - $ b10-loadzone your.zone.example.org - - 10. Test the new zone. - -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. - - 2.3.1. Download Tar File - - Downloading a release tar file is the recommended method to obtain the - source code. - - The BIND 10 releases are available as tar file downloads from - ftp://ftp.isc.org/isc/bind10/. Periodic development snapshots may also be - available. - - 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 - not recommended. - - Note - - When using source code retrieved via Git additional software will be - required: automake (v1.11 or newer), libtoolize, and autoconf (2.59 or - newer). These may need to be installed. - - The latest development code, including temporary experiments and - un-reviewed code, is available via the BIND 10 code revision control - system. This is powered by Git and all the BIND 10 development is public. - The leading development is done in the "master". - - The code can be checked out from git://git.bind10.isc.org/bind10; for - example: - - $ git clone git://git.bind10.isc.org/bind10 - - When checking out the code from the code version control system, it - doesn't include the generated configure script, Makefile.in files, nor the - related configure files. They can be created by running autoreconf with - the --install switch. This will run autoconf, aclocal, libtoolize, - autoheader, automake, and related commands. - - 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: - - $ ./configure - - Run ./configure with the --help switch to view the different options. The - commonly-used options are: - - --prefix - Define the installation location (the default is /usr/local/). - - --with-boost-include - Define the path to find the Boost headers. - - --with-pythonpath - Define the path to Python 3.1 if it is not in the standard - execution path. - - --with-gtest - Enable building the C++ Unit Tests using the Google Tests - framework. Optionally this can define the path to the gtest header - files and library. - - For example, the following configures it to find the Boost headers, find - the Python interpreter, and sets the installation location: - - $ ./configure \ - --with-boost-include=/usr/pkg/include \ - --with-pythonpath=/usr/pkg/bin/python3.1 \ - --prefix=/opt/bind10 - - If the configure fails, it may be due to missing or old dependencies. - - 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 - - 2.3.5. Install - - To install the BIND 10 executables, support files, and documentation, run: - - $ make install - - Note - - The install step may require superuser privileges. - - 2.3.6. Install Hierarchy - - The following is the layout of the complete BIND 10 installation: - - o bin/ -- general tools and diagnostic clients. - o etc/bind10-devel/ -- configuration files. - o lib/ -- libraries and python modules. - o libexec/bind10-devel/ -- executables that a user wouldn't normally run - directly and are not run independently. These are the BIND 10 modules - which are daemons started by the bind10 tool. - o sbin/ -- commands used by the system administrator. - o share/bind10-devel/ -- configuration specifications. - o share/man/ -- manual pages (online documentation). - o var/bind10-devel/ -- data source and configuration databases. - -Chapter 3. Starting BIND10 with bind10 - - Table of Contents - - 3.1. Starting BIND 10 - - 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. - This is the only command needed to start the BIND 10 system. - - After starting the b10-msgq communications channel, bind10 connects to it, - runs the configuration manager, and reads its own configuration. Then it - starts the other modules. - - The b10-sockcreator, b10-msgq and b10-cfgmgr services make up the core. - The b10-msgq daemon provides the communication channel between every part - of the system. The b10-cfgmgr daemon is always needed by every module, if - only to send information about themselves somewhere, but more importantly - to ask about their own settings, and about other modules. The - b10-sockcreator will allocate sockets for the rest of the system. - - In its default configuration, the bind10 master process will also start up - b10-cmdctl for admins to communicate with the system, b10-auth for - authoritative DNS service, b10-stats for statistics collection, b10-xfrin - for inbound DNS zone transfers, b10-xfrout for outbound DNS zone - transfers, and b10-zonemgr for secondary service. - -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. - - Note - - If the setproctitle Python module is detected at start up, the process - names for the Python-based daemons will be renamed to better identify them - instead of just "python". This is not needed on some operating systems. - -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. - - The configuration is in the Boss/components section. Each element - represents one component, which is an abstraction of a process (currently - there's also one component which doesn't represent a process). If you - didn't want to transfer out at all (your server is a slave only), you - would just remove the corresponding component from the set, like this and - the process would be stopped immediately (and not started on the next - startup): - - > config remove Boss/components b10-xfrout - > config commit - - To add a process to the set, let's say the resolver (which not started by - default), you would do this: - - > config add Boss/components b10-resolver - > config set Boss/components/b10-resolver/special resolver - > config set Boss/components/b10-resolver/kind needed - > config set Boss/components/b10-resolver/priority 10 - > config commit - - Now, what it means. We add an entry called b10-resolver. It is both a name - used to reference this component in the configuration and the name of the - process to start. Then we set some parameters on how to start it. - - The special one is for components that need some kind of special care - 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: - - Table 3.1. - - +------------------------------------------------------------------------+ - | Component | Special | Description | - |--------------+----------+----------------------------------------------| - | b10-auth | auth | Authoritative server | - |--------------+----------+----------------------------------------------| - | b10-resolver | resolver | The resolver | - |--------------+----------+----------------------------------------------| - | b10-cmdctl | cmdctl | The command control (remote control | - | | | interface) | - +------------------------------------------------------------------------+ - - The kind specifies how a failure of the component should be handled. If it - is set to "dispensable" (the default unless you set something else), it - will get started again if it fails. If it is set to "needed" and it fails - at startup, the whole bind10 shuts down and exits with error exit code. - But if it fails some time later, it is just started again. If you set it - to "core", you indicate that the system is not usable without the - component and if such component fails, the system shuts down no matter - when the failure happened. This is the behaviour of the core components - (the ones you can't turn off), but you can declare any other components as - core as well if you wish (but you can turn these off, they just can't - fail). - - 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. - - 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 - bus. The special components already know their address, but the usual ones - don't. The address is by convention the thing after b10-, with the first - letter capital (eg. b10-stats would have "Stats" as its address). - - The last one is process. It is the name of the process to be started. It - defaults to the name of the component if not set, but you can use this to - override it. - - Note - - This system allows you to start the same component multiple times (by - including it in the configuration with different names, but the same - process setting). However, the rest of the system doesn't expect such - situation, so it would probably not do what you want. Such support is yet - to be implemented. - - Note - - The configuration is quite powerful, but that includes a lot of space for - mistakes. You could turn off the b10-cmdctl, but then you couldn't change - it back the usual way, as it would require it to be running (you would - have to find and edit the configuration directly). Also, some modules - might have dependencies -- b10-stats-httpd need b10-stats, b10-xfrout - needs the b10-auth to be running, etc. - - In short, you should think twice before disabling something here. - -Chapter 4. Command channel - - The BIND 10 components use the b10-msgq message routing daemon to - communicate with other BIND 10 components. The b10-msgq implements what is - called the "Command Channel". Processes intercommunicate by sending - messages on the command channel. Example messages include shutdown, get - configurations, and set configurations. This Command Channel is not used - for DNS message passing. It is used only to control and monitor the BIND - 10 system. - - Administrators do not communicate directly with the b10-msgq daemon. By - default, BIND 10 uses port 9912 for the b10-msgq service. It listens on - 127.0.0.1. - -Chapter 5. Configuration manager - - The configuration manager, b10-cfgmgr, handles all BIND 10 system - configuration. It provides persistent storage for configuration, and - notifies running modules of configuration changes. - - The b10-auth and b10-xfrin daemons and other components receive their - configurations from the configuration manager over the b10-msgq command - channel. - - The administrator doesn't connect to it directly, but uses a user - interface to communicate with the configuration manager via b10-cmdctl's - REST-ful interface. b10-cmdctl is covered in Chapter 6, Remote control - daemon. - - Note - - The development prototype release only provides the bindctl as a user - interface to b10-cmdctl. Upcoming releases will provide another - interactive command-line interface and a web-based interface. - - The b10-cfgmgr daemon can send all specifications and all current settings - to the bindctl client (via b10-cmdctl). - - b10-cfgmgr relays configurations received from b10-cmdctl to the - appropriate modules. - - The stored configuration file is at - /usr/local/var/bind10-devel/b10-config.db. (The full path is what was - defined at build configure time for --localstatedir. The default is - /usr/local/var/.) The format is loosely based on JSON and is directly - parseable python, but this may change in a future version. This - configuration data file is not manually edited by the administrator. - - The configuration manager does not have any command line arguments. - Normally it is not started manually, but is automatically started using - the bind10 master process (as covered in Chapter 3, Starting BIND10 with - bind10). - -Chapter 6. Remote control daemon - - Table of Contents - - 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 - username and password validation. It provides a REST-ful interface for - accessing and controlling BIND 10. - - When b10-cmdctl starts, it firsts asks b10-cfgmgr about what modules are - running and what their configuration is (over the b10-msgq channel). Then - it will start listening on HTTPS for clients -- the user interface -- such - as bindctl. - - b10-cmdctl directly sends commands (received from the user interface) to - the specified component. Configuration changes are actually commands to - b10-cfgmgr so are sent there. - - The HTTPS server requires a private key, such as a RSA PRIVATE KEY. The - default location is at /usr/local/etc/bind10-devel/cmdctl-keyfile.pem. (A - sample key is at /usr/local/share/bind10-devel/cmdctl-keyfile.pem.) It - also uses a certificate located at - /usr/local/etc/bind10-devel/cmdctl-certfile.pem. (A sample certificate is - at /usr/local/share/bind10-devel/cmdctl-certfile.pem.) This may be a - self-signed certificate or purchased from a certification authority. - - Note - - The HTTPS server doesn't support a certificate request from a client (at - this time). The b10-cmdctl daemon does not provide a public service. If - any client wants to control BIND 10, then a certificate needs to be first - received from the BIND 10 administrator. The BIND 10 installation provides - a sample PEM bundle that matches the sample key and certificate. - - The b10-cmdctl daemon also requires the user account file located at - /usr/local/etc/bind10-devel/cmdctl-accounts.csv. This comma-delimited file - lists the accounts with a user name, hashed password, and salt. (A sample - file is at /usr/local/share/bind10-devel/cmdctl-accounts.csv. It contains - the user named "root" with the password "bind10".) - - The administrator may create a user account with the b10-cmdctl-usermgr - tool. - - By default the HTTPS server listens on the localhost port 8080. The port - can be set by using the --port command line option. The address to listen - on can be set using the --address command line argument. Each HTTPS - connection is stateless and timesout in 1200 seconds by default. This can - be redefined by using the --idle-timeout command line argument. - -6.1. Configuration specification for b10-cmdctl - - The configuration items for b10-cmdctl are: key_file cert_file - accounts_file - - The control commands are: print_settings shutdown - -Chapter 7. Control and configure user interface - - Note - - For this development prototype release, bindctl is the only user - interface. It is expected that upcoming releases will provide another - interactive command-line interface and a web-based interface for - controlling and configuring BIND 10. - - The bindctl tool provides an interactive prompt for configuring, - controlling, and querying the BIND 10 components. It communicates directly - with a REST-ful interface over HTTPS provided by b10-cmdctl. It doesn't - communicate to any other components directly. - - Configuration changes are actually commands to b10-cfgmgr. So when bindctl - sends a configuration, it is sent to b10-cmdctl (over a HTTPS connection); - then b10-cmdctl sends the command (over a b10-msgq command channel) to - b10-cfgmgr which then stores the details and relays (over a b10-msgq - command channel) the configuration on to the specified module. - -Chapter 8. Authoritative Server - - Table of Contents - - 8.1. Server Configurations - - 8.2. Data Source Backends - - 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. - -8.1. Server Configurations - - b10-auth is configured via the b10-cfgmgr configuration manager. The - module name is "Auth". The configuration data item is: - - database_file - This is an optional string to define the path to find the SQLite3 - database file. Note: Later the DNS server will use various data - source backends. This may be a temporary setting until then. - - The configuration command is: - - shutdown - Stop the authoritative DNS server. - -8.2. Data Source Backends - - Note - - For the development prototype release, b10-auth supports a SQLite3 data - source backend and in-memory data source backend. Upcoming versions will - be able to use multiple different data sources, such as MySQL and Berkeley - DB. - - By default, the SQLite3 backend uses the data file located at - /usr/local/var/bind10-devel/zone.sqlite3. (The full path is what was - defined at build configure time for --localstatedir. The default is - /usr/local/var/.) This data file location may be changed by defining the - "database_file" configuration. - -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. - - b10-loadzone supports the following special directives (control entries): - - $INCLUDE - Loads an additional zone file. This may be recursive. - - $ORIGIN - Defines the relative domain name. - - $TTL - Defines the time-to-live value used for following records that - don't include a TTL. - - The -o argument may be used to define the default origin for loaded zone - file records. - - Note - - In the development prototype release, only the SQLite3 back end is used. - By default, it stores the zone data in - /usr/local/var/bind10-devel/zone.sqlite3 unless the -d switch is used to - set the database filename. Multiple zones are stored in a single SQLite3 - zone database. - - If you reload a zone already existing in the database, all records from - that prior zone disappear and a whole new set appears. - -Chapter 9. Incoming Zone Transfers - - Table of Contents - - 9.1. Configuration for Incoming Zone Transfers - - 9.2. Enabling IXFR - - 9.3. Secondary Manager - - 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 - BIND 10 data source, and its records can be served by b10-auth. In - combination with b10-zonemgr (for automated SOA checks), this allows the - BIND 10 server to provide "secondary" service. - - The b10-xfrin process supports both AXFR and IXFR. Due to some - implementation limitations of the current development release, however, it - only tries AXFR by default, and care should be taken to enable IXFR. - - Note - - 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. - -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 - transfer manually, without a prior configuration (see below)). - - For example, to enable zone transfers for a zone named "example.com" - (whose master address is assumed to be 2001:db8::53 here), run the - following at the bindctl prompt: - - > config add Xfrin/zones - > config set Xfrin/zones[0]/name "example.com" - > config set Xfrin/zones[0]/master_addr "2001:db8::53" - > config commit - - (We assume there has been no zone configuration before). - -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 - configuration parameter to true. In the above example of configuration - sequence, you'll need to add the following before performing commit: - - > config set Xfrin/zones[0]/use_ixfr true - - Note - - One reason why IXFR is disabled by default in the current release is - because it does not support automatic fallback from IXFR to AXFR when it - encounters a primary server that doesn't support outbound IXFR (and, not - many existing implementations support it). Another, related reason is that - it does not use AXFR even if it has no knowledge about the zone (like at - the very first time the secondary server is set up). IXFR requires the - "current version" of the zone, so obviously it doesn't work in this - situation and AXFR is the only workable choice. The current release of - b10-xfrin does not make this selection automatically. These features will - be implemented in a near future version, at which point we will enable - IXFR by default. - -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: - - > Xfrin retransfer zone_name="foo.example.org" master=192.0.2.99 - -Chapter 10. Outbound Zone Transfers - - The b10-xfrout process is started by bind10. When the b10-auth - authoritative DNS server receives an AXFR or IXFR request, b10-auth - internally forwards the request to b10-xfrout, which handles the rest of - request processing. This is used to provide primary DNS service to share - zones to secondary name servers. The b10-xfrout is also used to send - NOTIFY messages to secondary servers. - - A global or per zone transfer_acl configuration can be used to control - accessibility of the outbound zone transfer service. By default, - b10-xfrout allows any clients to perform zone transfers for any zones: - - > config show Xfrout/transfer_acl - Xfrout/transfer_acl[0] {"action": "ACCEPT"} any (default) - - You can change this to, for example, rejecting all transfer requests by - default while allowing requests for the transfer of zone "example.com" - from 192.0.2.1 and 2001:db8::1 as follows: - - > config set Xfrout/transfer_acl[0] {"action": "REJECT"} - > config add Xfrout/zone_config - > config set Xfrout/zone_config[0]/origin "example.com" - > config set Xfrout/zone_config[0]/transfer_acl [{"action": "ACCEPT", "from": "192.0.2.1"}, - {"action": "ACCEPT", "from": "2001:db8::1"}] - > config commit - - Note - - In the above example the lines for transfer_acl were divided for - readability. In the actual input it must be in a single line. - - If you want to require TSIG in access control, a separate TSIG "key ring" - must be configured specifically for b10-xfrout as well as a system wide - key ring, both containing a consistent set of keys. For example, to change - the previous example to allowing requests from 192.0.2.1 signed by a TSIG - with a key name of "key.example", you'll need to do this: - - > config set tsig_keys/keys ["key.example:"] - > config set Xfrout/tsig_keys/keys ["key.example:"] - > config set Xfrout/zone_config[0]/transfer_acl [{"action": "ACCEPT", "from": "192.0.2.1", "key": "key.example"}] - > config commit - - The first line of configuration defines a system wide key ring. This is - necessary because the b10-auth server also checks TSIGs and it uses the - system wide configuration. - - Note - - In a future version, b10-xfrout will also use the system wide TSIG - configuration. The way to specify zone specific configuration (ACLs, etc) - is likely to be changed, too. - -Chapter 11. Recursive Name Server - - Table of Contents - - 11.1. Access Control - - 11.2. Forwarding - - The b10-resolver process is started by bind10. - - The main bind10 process can be configured to select to run either the - authoritative or resolver or both. By default, it starts the authoritative - service. You may change this using bindctl, for example: - - > config remove Boss/components b10-xfrout - > config remove Boss/components b10-xfrin - > config remove Boss/components b10-auth - > config add Boss/components b10-resolver - > config set Boss/components/b10-resolver/special resolver - > config set Boss/components/b10-resolver/kind needed - > config set Boss/components/b10-resolver/priority 10 - > config commit - - The master bind10 will stop and start the desired services. - - By default, the resolver listens on port 53 for 127.0.0.1 and ::1. The - following example shows how it can be configured to listen on an - additional address (and port): - - > config add Resolver/listen_on - > config set Resolver/listen_on[2]/address "192.168.1.1" - > config set Resolver/listen_on[2]/port 53 - > config commit - - (Replace the "2" as needed; run "config show Resolver/listen_on" if - needed.) - -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 - used to reject, drop, or allow specific IPs or networks. This - configuration list is first match. - - The configuration's action item may be set to "ACCEPT" to allow the - incoming query, "REJECT" to respond with a DNS REFUSED return code, or - "DROP" to ignore the query without any response (such as a blackhole). For - more information, see the respective debugging messages: - RESOLVER_QUERY_ACCEPTED, RESOLVER_QUERY_REJECTED, and - RESOLVER_QUERY_DROPPED. - - The required configuration's from item is set to an IPv4 or IPv6 address, - addresses with an network mask, or to the special lowercase keywords - "any6" (for any IPv6 address) or "any4" (for any IPv4 address). - - For example to allow the 192.168.1.0/24 network to use your recursive name - server, at the bindctl prompt run: - - > config add Resolver/query_acl - > config set Resolver/query_acl[2]/action "ACCEPT" - > config set Resolver/query_acl[2]/from "192.168.1.0/24" - > config commit - - (Replace the "2" as needed; run "config show Resolver/query_acl" if - needed.) - - Note - - This prototype access control configuration syntax may be changed. - -11.2. Forwarding - - To enable forwarding, the upstream address and port must be configured to - forward queries to, such as: - - > config set Resolver/forward_addresses [{ "address": "192.168.1.1", "port": 53 }] - > config commit - - (Replace 192.168.1.1 to point to your full resolver.) - - Normal iterative name service can be re-enabled by clearing the forwarding - address(es); for example: - - > config set Resolver/forward_addresses [] - > config commit - -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. - - This stats daemon provides commands to identify if it is running, show - specified or all statistics data, show specified or all statistics data - schema, and set specified statistics data. For example, using bindctl: - - > Stats show - { - "Auth": { - "opcode.iquery": 0, - "opcode.notify": 10, - "opcode.query": 869617, - ... - "queries.tcp": 1749, - "queries.udp": 867868 - }, - "Boss": { - "boot_time": "2011-01-20T16:59:03Z" - }, - "Stats": { - "boot_time": "2011-01-20T16:59:05Z", - "last_update_time": "2011-01-20T17:04:05Z", - "lname": "4d3869d9_a@jreed.example.net", - "report_time": "2011-01-20T17:04:06Z", - "timestamp": 1295543046.823504 - } - } - - -Chapter 16. Logging - - Table of Contents - - 16.1. Logging configuration - - 16.1.1. Loggers - - 16.1.2. Output Options - - 16.1.3. Example session - - 16.2. Logging Message Format - -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. - - 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 - each logger can be configured independently of one another. - - In the Logging module, you can specify the configuration for zero or more - loggers; any that are not specified will take appropriate default values.. - - The three most important elements of a logger configuration are the name - (the component that is generating the messages), the severity (what to - log), and the output_options (where to log). - - 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 - for the resolver module, you add an entry for a logger named "Resolver". - This configuration will then be used by the loggers in the Resolver - module, and all the libraries used by it. - - If you want to specify logging for one specific library within the module, - you set the name to module.library. For example, the logger used by the - nameserver address store component has the full name of "Resolver.nsas". - If there is no entry in Logging for a particular library, it will use the - configuration given for the module. - - To illustrate this, suppose you want the cache library to log messages of - severity DEBUG, and the rest of the resolver code to log messages of - severity INFO. To achieve this you specify two loggers, one with the name - "Resolver" and severity INFO, and one with the name "Resolver.cache" with - severity DEBUG. As there are no entries for other libraries (e.g. the - nsas), they will use the configuration for the module ("Resolver"), so - giving the desired behavior. - - One special case is that of a module name of "*" (asterisks), which is - interpreted as any module. You can set global logging options by using - this, including setting the logging configuration for a library that is - used by multiple modules (e.g. "*.config" specifies the configuration - library code in whatever module is using it). - - If there are multiple logger specifications in the configuration that - might match a particular logger, the specification with the more specific - logger name takes precedence. For example, if there are entries for for - both "*" and "Resolver", the resolver module -- and all libraries it uses - -- will log messages according to the configuration in the second entry - ("Resolver"). All other modules will use the configuration of the first - entry ("*"). If there was also a configuration entry for "Resolver.cache", - the cache library within the resolver would use that in preference to the - entry for "Resolver". - - One final note about the naming. When specifying the module name within a - logger, use the name of the module as specified in bindctl, e.g. - "Resolver" for the resolver module, "Xfrout" for the xfrout module, etc. - When the message is logged, the message will include the name of the - logger generating the message, but with the module name replaced by the - name of the process implementing the module (so for example, a message - generated by the "Auth.cache" logger will appear in the output with a - logger name of "b10-auth.cache"). - - 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 - descending order of severity): - - o FATAL - o ERROR - o WARN - o INFO - o DEBUG - - When the severity of a logger is set to one of these values, it will only - log messages of that severity, and the severities above it. The severity - may also be set to NONE, in which case all messages from that logger are - inhibited. - - 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: - - 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 - verbose). - - If severity for the logger is not DEBUG, this value is ignored. - - 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 - "Resolver.cache", and additive is true in the second, it will write the - log messages not only to the destinations specified for "Resolver.cache", - but also to the destinations as specified in the output_options in the - logger named "Resolver". - - 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. - - 16.1.2.1. destination (string) - - The destination is the type of output. It can be one of: - - o console - o file - o syslog - - 16.1.2.2. output (string) - - Depending on what is set as the output destination, this value is - interpreted as follows: - - destination is "console" - The value of output must be one of "stdout" (messages printed to - standard output) or "stderr" (messages printed to standard error). - - destination is "file" - The value of output is interpreted as a file name; log messages - will be appended to this file. - - destination is "syslog" - The value of output is interpreted as the syslog facility (e.g. - local0) that should be used for log messages. - - The other options for output_options are: - - 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. - - 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 - renamed and a new file opened. (For example, a ".1" is appended to the - name -- if a ".1" file exists, it is renamed ".2", etc.) - - If this is 0, no maximum file size is used. - - 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". - - 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 - to log at DEBUG with debuglevel 40, to a different file - (/tmp/debug_messages). - - Start bindctl. - - ["login success "] - > config show Logging - Logging/loggers [] list - - By default, no specific loggers are configured, in which case the severity - defaults to INFO and the output is written to stderr. - - Let's first add a default logger: - - > config add Logging/loggers - > config show Logging - Logging/loggers/ list (modified) - - The loggers value line changed to indicate that it is no longer an empty - list: - - > config show Logging/loggers - Logging/loggers[0]/name "" string (default) - Logging/loggers[0]/severity "INFO" string (default) - Logging/loggers[0]/debuglevel 0 integer (default) - Logging/loggers[0]/additive false boolean (default) - Logging/loggers[0]/output_options [] list (default) - - The name is mandatory, so we must set it. We will also change the severity - as well. Let's start with the global logger. - - > config set Logging/loggers[0]/name * - > config set Logging/loggers[0]/severity WARN - > config show Logging/loggers - Logging/loggers[0]/name "*" string (modified) - Logging/loggers[0]/severity "WARN" string (modified) - Logging/loggers[0]/debuglevel 0 integer (default) - Logging/loggers[0]/additive false boolean (default) - Logging/loggers[0]/output_options [] list (default) - - Of course, we need to specify where we want the log messages to go, so we - add an entry for an output option. - - > config add Logging/loggers[0]/output_options - > config show Logging/loggers[0]/output_options - Logging/loggers[0]/output_options[0]/destination "console" string (default) - Logging/loggers[0]/output_options[0]/output "stdout" string (default) - Logging/loggers[0]/output_options[0]/flush false boolean (default) - Logging/loggers[0]/output_options[0]/maxsize 0 integer (default) - Logging/loggers[0]/output_options[0]/maxver 0 integer (default) - - These aren't the values we are looking for. - - > config set Logging/loggers[0]/output_options[0]/destination file - > config set Logging/loggers[0]/output_options[0]/output /var/log/bind10.log - > config set Logging/loggers[0]/output_options[0]/maxsize 30000 - > config set Logging/loggers[0]/output_options[0]/maxver 8 - - Which would make the entire configuration for this logger look like: - - > config show all Logging/loggers - Logging/loggers[0]/name "*" string (modified) - Logging/loggers[0]/severity "WARN" string (modified) - Logging/loggers[0]/debuglevel 0 integer (default) - Logging/loggers[0]/additive false boolean (default) - Logging/loggers[0]/output_options[0]/destination "file" string (modified) - Logging/loggers[0]/output_options[0]/output "/var/log/bind10.log" string (modified) - Logging/loggers[0]/output_options[0]/flush false boolean (default) - Logging/loggers[0]/output_options[0]/maxsize 30000 integer (modified) - Logging/loggers[0]/output_options[0]/maxver 8 integer (modified) - - That looks OK, so let's commit it before we add the configuration for the - authoritative server's logger. - - > config commit - - Now that we have set it, and checked each value along the way, adding a - second entry is quite similar. - - > config add Logging/loggers - > config set Logging/loggers[1]/name Auth - > config set Logging/loggers[1]/severity DEBUG - > config set Logging/loggers[1]/debuglevel 40 - > config add Logging/loggers[1]/output_options - > config set Logging/loggers[1]/output_options[0]/destination file - > config set Logging/loggers[1]/output_options[0]/output /tmp/auth_debug.log - > config commit - - And that's it. Once we have found whatever it was we needed the debug - messages for, we can simply remove the second logger to let the - authoritative server use the same settings as the rest. - - > config remove Logging/loggers[1] - > config commit - - And every module will now be using the values from the logger named "*". - -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 - and, if the message indicates a problem, information about the problem - that may be useful in fixing it. - - Consider the message below logged to a file: - - 2011-06-15 13:48:22.034 ERROR [b10-resolver.asiolink] - ASIODNS_OPENSOCK error 111 opening TCP socket to 127.0.0.1(53) - - Note: the layout of messages written to the system logging file (syslog) - may be slightly different. This message has been split across two lines - here for display reasons; in the logging file, it will appear on one - line.) - - The log message comprises a number of components: - - 2011-06-15 13:48:22.034 - - The date and time at which the message was generated. - - ERROR - - The severity of the message. - - [b10-resolver.asiolink] - - The source of the message. This comprises two components: the BIND - 10 process generating the message (in this case, b10-resolver) and - the module within the program from which the message originated - (which in the example is the asynchronous I/O link module, - asiolink). - - ASIODNS_OPENSOCK - - The message identification. Every message in BIND 10 has a unique - identification, which can be used as an index into the BIND 10 - Messages Manual (http://bind10.isc.org/docs/bind10-messages.html) - from which more information can be obtained. - - error 111 opening TCP socket to 127.0.0.1(53) - - A brief description of the cause of the problem. Within this text, - information relating to the condition that caused the message to - be logged will be included. In this example, error number 111 (an - operating system-specific error number) was encountered when - trying to open a TCP connection to port 53 on the local system - (address 127.0.0.1). The next step would be to find out the reason - for the failure by consulting your system's documentation to - identify what error number 111 means. diff --git a/doc/guide/bind10-messages.html b/doc/guide/bind10-messages.html deleted file mode 100644 index b82b485603..0000000000 --- a/doc/guide/bind10-messages.html +++ /dev/null @@ -1,2628 +0,0 @@ -BIND 10 Messages Manual

BIND 10 Messages Manual

This is the messages manual for BIND 10 version - 20111129.

Copyright © 2011-2012 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. -

- 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 - http://bind10.isc.org/docs. -

Table of Contents

1. Introduction
2. BIND 10 Messages

Chapter 1. Introduction

- This document lists each message that can be logged by the - programs in the BIND 10 package. Each entry in this manual - is of the form: - 

IDENTIFICATION message-text

- ... where "IDENTIFICATION" is the message identification included - in each message logged and "message-text" is the accompanying - message text. The "message-text" may include placeholders of the - form "%1", "%2" etc.; these parameters are replaced by relevant - values when the message is logged. -

- Each entry is also accompanied by a description giving more - information about the circumstances that result in the message - being logged. -

- For information on configuring and using BIND 10 logging, - refer to the BIND 10 Guide. -

Chapter 2. BIND 10 Messages

-

ASIODNS_FD_ADD_TCP adding a new TCP server by opened fd %1

-A debug message informing about installing a file descriptor as a server. -The file descriptor number is noted. -

ASIODNS_FD_ADD_UDP adding a new UDP server by opened fd %1

-A debug message informing about installing a file descriptor as a server. -The file descriptor number is noted. -

ASIODNS_FETCH_COMPLETED upstream fetch to %1(%2) has now completed

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

ASIODNS_FETCH_STOPPED upstream fetch to %1(%2) has been stopped

-An external component has requested the halting of an upstream fetch. This -is an allowed operation, and the message should only appear if debug is -enabled. -

ASIODNS_OPEN_SOCKET error %1 opening %2 socket to %3(%4)

-The asynchronous I/O code encountered an error when trying to open a socket -of the specified protocol in order to send a message to the target address. -The number of the system error that caused the problem is given in the -message. -

ASIODNS_READ_DATA error %1 reading %2 data from %3(%4)

-The asynchronous I/O code encountered an error when trying to read data from -the specified address on the given protocol. The number of the system -error that caused the problem is given in the message. -

ASIODNS_READ_TIMEOUT receive timeout while waiting for data from %1(%2)

-An upstream fetch from the specified address timed out. This may happen for -any number of reasons and is most probably a problem at the remote server -or a problem on the network. The message will only appear if debug is -enabled. -

ASIODNS_SEND_DATA error %1 sending data using %2 to %3(%4)

-The asynchronous I/O code encountered an error when trying to send data to -the specified address on the given protocol. The number of the system -error that caused the problem is given in the message. -

ASIODNS_UNKNOWN_ORIGIN unknown origin for ASIO error code %1 (protocol: %2, address %3)

-An internal consistency check on the origin of a message from the -asynchronous I/O module failed. This may indicate an internal error; -please submit a bug report. -

ASIODNS_UNKNOWN_RESULT unknown result (%1) when IOFetch::stop() was executed for I/O to %2(%3)

-An internal error indicating that the termination method of the resolver's -upstream fetch class was called with an unknown result code (which is -given in the message). Please submit a bug report. -

AUTH_AXFR_ERROR error handling AXFR request: %1

-This is a debug message produced by the authoritative server when it -has encountered an error processing an AXFR request. The message gives -the reason for the error, and the server will return a SERVFAIL code to -the sender. -

AUTH_AXFR_UDP AXFR query received over UDP

-This is a debug message output when the authoritative server has received -an AXFR query over UDP. Use of UDP for AXFRs is not permitted by the -protocol, so the server will return a FORMERR error to the sender. -

AUTH_COMMAND_FAILED execution of command channel instruction '%1' failed: %2

-Execution of the specified command by the authoritative server failed. The -message contains the reason for the failure. -

AUTH_CONFIG_CHANNEL_CREATED configuration session channel created

-This is a debug message indicating that authoritative server has created -the channel to the configuration manager. It is issued during server -startup is an indication that the initialization is proceeding normally. -

AUTH_CONFIG_CHANNEL_ESTABLISHED configuration session channel established

-This is a debug message indicating that authoritative server -has established communication the configuration manager over the -previously-created channel. It is issued during server startup is an -indication that the initialization is proceeding normally. -

AUTH_CONFIG_CHANNEL_STARTED configuration session channel started

-This is a debug message, issued when the authoritative server has -posted a request to be notified when new configuration information is -available. It is issued during server startup is an indication that -the initialization is proceeding normally. -

AUTH_CONFIG_LOAD_FAIL load of configuration failed: %1

-An attempt to configure the server with information from the configuration -database during the startup sequence has failed. (The reason for -the failure is given in the message.) The server will continue its -initialization although it may not be configured in the desired way. -

AUTH_CONFIG_UPDATE_FAIL update of configuration failed: %1

-At attempt to update the configuration the server with information -from the configuration database has failed, the reason being given in -the message. -

AUTH_DATA_SOURCE data source database file: %1

-This is a debug message produced by the authoritative server when it accesses a -datebase data source, listing the file that is being accessed. -

AUTH_DNS_SERVICES_CREATED DNS services created

-This is a debug message indicating that the component that will handling -incoming queries for the authoritative server (DNSServices) has been -successfully created. It is issued during server startup is an indication -that the initialization is proceeding normally. -

AUTH_HEADER_PARSE_FAIL unable to parse header in received DNS packet: %1

-This is a debug message, generated by the authoritative server when an -attempt to parse the header of a received DNS packet has failed. (The -reason for the failure is given in the message.) The server will drop the -packet. -

AUTH_INVALID_STATISTICS_DATA invalid specification of statistics data specified

-An error was encountered when the authoritiative server specified -statistics data which is invalid for the auth specification file. -

AUTH_LOAD_TSIG loading TSIG keys

-This is a debug message indicating that the authoritative server -has requested the keyring holding TSIG keys from the configuration -database. It is issued during server startup is an indication that the -initialization is proceeding normally. -

AUTH_LOAD_ZONE loaded zone %1/%2

-This debug message is issued during the processing of the 'loadzone' command -when the authoritative server has successfully loaded the named zone of the -named class. -

AUTH_MEM_DATASRC_DISABLED memory data source is disabled for class %1

-This is a debug message reporting that the authoritative server has -discovered that the memory data source is disabled for the given class. -

AUTH_MEM_DATASRC_ENABLED memory data source is enabled for class %1

-This is a debug message reporting that the authoritative server has -discovered that the memory data source is enabled for the given class. -

AUTH_NOTIFY_QUESTIONS invalid number of questions (%1) in incoming NOTIFY

-This debug message is logged by the authoritative server when it receives -a NOTIFY packet that contains zero or more than one question. (A valid -NOTIFY packet contains one question.) The server will return a FORMERR -error to the sender. -

AUTH_NOTIFY_RRTYPE invalid question RR type (%1) in incoming NOTIFY

-This debug message is logged by the authoritative server when it receives -a NOTIFY packet that an RR type of something other than SOA in the -question section. (The RR type received is included in the message.) The -server will return a FORMERR error to the sender. -

AUTH_NO_STATS_SESSION session interface for statistics is not available

-The authoritative server had no session with the statistics module at the -time it attempted to send it data: the attempt has been abandoned. This -could be an error in configuration. -

AUTH_NO_XFRIN received NOTIFY but XFRIN session is not running

-This is a debug message produced by the authoritative server when it receives -a NOTIFY packet but the XFRIN process is not running. The packet will be -dropped and nothing returned to the sender. -

AUTH_PACKET_PARSE_ERROR unable to parse received DNS packet: %1

-This is a debug message, generated by the authoritative server when an -attempt to parse a received DNS packet has failed due to something other -than a protocol error. The reason for the failure is given in the message; -the server will return a SERVFAIL error code to the sender. -

AUTH_PACKET_PROTOCOL_ERROR DNS packet protocol error: %1. Returning %2

-This is a debug message, generated by the authoritative server when an -attempt to parse a received DNS packet has failed due to a protocol error. -The reason for the failure is given in the message, as is the error code -that will be returned to the sender. -

AUTH_PACKET_RECEIVED message received:\n%1

-This is a debug message output by the authoritative server when it -receives a valid DNS packet. -

-Note: This message includes the packet received, rendered in the form of -multiple lines of text. For this reason, it is suggested that this log message -not be routed to the syslog file, where the multiple lines could confuse -programs that expect a format of one message per line. -

AUTH_PROCESS_FAIL message processing failure: %1

-This message is generated by the authoritative server when it has -encountered an internal error whilst processing a received packet: -the cause of the error is included in the message. -

-The server will return a SERVFAIL error code to the sender of the packet. -This message indicates a potential error in the server. Please open a -bug ticket for this issue. -

AUTH_RECEIVED_COMMAND command '%1' received

-This is a debug message issued when the authoritative server has received -a command on the command channel. -

AUTH_RECEIVED_SENDSTATS command 'sendstats' received

-This is a debug message issued when the authoritative server has received -a command from the statistics module to send it data. The 'sendstats' -command is handled differently to other commands, which is why the debug -message associated with it has its own code. -

AUTH_RESPONSE_RECEIVED received response message, ignoring

-This is a debug message, this is output if the authoritative server -receives a DNS packet with the QR bit set, i.e. a DNS response. The -server ignores the packet as it only responds to question packets. -

AUTH_SEND_ERROR_RESPONSE sending an error response (%1 bytes):\n%2

-This is a debug message recording that the authoritative server is sending -an error response to the originator of the query. A previous message will -have recorded details of the failure. -

-Note: This message includes the packet sent, rendered in the form of -multiple lines of text. For this reason, it is suggested that this log message -not be routed to the syslog file, where the multiple lines could confuse -programs that expect a format of one message per line. -

AUTH_SEND_NORMAL_RESPONSE sending an error response (%1 bytes):\n%2

-This is a debug message recording that the authoritative server is sending -a response to the originator of a query. -

-Note: This message includes the packet sent, rendered in the form of -multiple lines of text. For this reason, it is suggested that this log message -not be routed to the syslog file, where the multiple lines could confuse -programs that expect a format of one message per line. -

AUTH_SERVER_CREATED server created

-An informational message indicating that the authoritative server process has -been created and is initializing. The AUTH_SERVER_STARTED message will be -output when initialization has successfully completed and the server starts -accepting queries. -

AUTH_SERVER_FAILED server failed: %1

-The authoritative server has encountered a fatal error and is terminating. The -reason for the failure is included in the message. -

AUTH_SERVER_STARTED server started

-Initialization of the authoritative server has completed successfully -and it is entering the main loop, waiting for queries to arrive. -

AUTH_SQLITE3 nothing to do for loading sqlite3

-This is a debug message indicating that the authoritative server has -found that the data source it is loading is an SQLite3 data source, -so no further validation is needed. -

AUTH_STATS_CHANNEL_CREATED STATS session channel created

-This is a debug message indicating that the authoritative server has -created a channel to the statistics process. It is issued during server -startup is an indication that the initialization is proceeding normally. -

AUTH_STATS_CHANNEL_ESTABLISHED STATS session channel established

-This is a debug message indicating that the authoritative server -has established communication over the previously created statistics -channel. It is issued during server startup is an indication that the -initialization is proceeding normally. -

AUTH_STATS_COMMS communication error in sending statistics data: %1

-An error was encountered when the authoritative server tried to send data -to the statistics daemon. The message includes additional information -describing the reason for the failure. -

AUTH_STATS_TIMEOUT timeout while sending statistics data: %1

-The authoritative server sent data to the statistics daemon but received -no acknowledgement within the specified time. The message includes -additional information describing the reason for the failure. -

AUTH_STATS_TIMER_DISABLED statistics timer has been disabled

-This is a debug message indicating that the statistics timer has been -disabled in the authoritative server and no statistics information is -being produced. -

AUTH_STATS_TIMER_SET statistics timer set to %1 second(s)

-This is a debug message indicating that the statistics timer has been -enabled and that the authoritative server will produce statistics data -at the specified interval. -

AUTH_UNSUPPORTED_OPCODE unsupported opcode: %1

-This is a debug message, produced when a received DNS packet being -processed by the authoritative server has been found to contain an -unsupported opcode. (The opcode is included in the message.) The server -will return an error code of NOTIMPL to the sender. -

AUTH_XFRIN_CHANNEL_CREATED XFRIN session channel created

-This is a debug message indicating that the authoritative server has -created a channel to the XFRIN (Transfer-in) process. It is issued -during server startup is an indication that the initialization is -proceeding normally. -

AUTH_XFRIN_CHANNEL_ESTABLISHED XFRIN session channel established

-This is a debug message indicating that the authoritative server has -established communication over the previously-created channel to the -XFRIN (Transfer-in) process. It is issued during server startup is an -indication that the initialization is proceeding normally. -

AUTH_ZONEMGR_COMMS error communicating with zone manager: %1

-This is a debug message output during the processing of a NOTIFY request. -An error (listed in the message) has been encountered whilst communicating -with the zone manager. The NOTIFY request will not be honored. -

AUTH_ZONEMGR_ERROR received error response from zone manager: %1

-This is a debug message output during the processing of a NOTIFY -request. The zone manager component has been informed of the request, -but has returned an error response (which is included in the message). The -NOTIFY request will not be honored. -

BIND10_CHECK_MSGQ_ALREADY_RUNNING checking if msgq is already running

-The boss process is starting up and will now check if the message bus -daemon is already running. If so, it will not be able to start, as it -needs a dedicated message bus. -

BIND10_COMPONENT_FAILED component %1 (pid %2) failed with %3 exit status

-The process terminated, but the bind10 boss didn't expect it to, which means -it must have failed. -

BIND10_COMPONENT_RESTART component %1 is about to restart

-The named component failed previously and we will try to restart it to provide -as flawless service as possible, but it should be investigated what happened, -as it could happen again. -

BIND10_COMPONENT_START component %1 is starting

-The named component is about to be started by the boss process. -

BIND10_COMPONENT_START_EXCEPTION component %1 failed to start: %2

-An exception (mentioned in the message) happened during the startup of the -named component. The componet is not considered started and further actions -will be taken about it. -

BIND10_COMPONENT_STOP component %1 is being stopped

-A component is about to be asked to stop willingly by the boss. -

BIND10_COMPONENT_UNSATISFIED component %1 is required to run and failed

-A component failed for some reason (see previous messages). It is either a core -component or needed component that was just started. In any case, the system -can't continue without it and will terminate. -

BIND10_CONFIGURATOR_BUILD building plan '%1' -> '%2'

-A debug message. This indicates that the configurator is building a plan -how to change configuration from the older one to newer one. This does no -real work yet, it just does the planning what needs to be done. -

BIND10_CONFIGURATOR_PLAN_INTERRUPTED configurator plan interrupted, only %1 of %2 done

-There was an exception during some planned task. The plan will not continue and -only some tasks of the plan were completed. The rest is aborted. The exception -will be propagated. -

BIND10_CONFIGURATOR_RECONFIGURE reconfiguring running components

-A different configuration of which components should be running is being -installed. All components that are no longer needed will be stopped and -newly introduced ones started. This happens at startup, when the configuration -is read the first time, or when an operator changes configuration of the boss. -

BIND10_CONFIGURATOR_RUN running plan of %1 tasks

-A debug message. The configurator is about to execute a plan of actions it -computed previously. -

BIND10_CONFIGURATOR_START bind10 component configurator is starting up

-The part that cares about starting and stopping the right component from the -boss process is starting up. This happens only once at the startup of the -boss process. It will start the basic set of processes now (the ones boss -needs to read the configuration), the rest will be started after the -configuration is known. -

BIND10_CONFIGURATOR_STOP bind10 component configurator is shutting down

-The part that cares about starting and stopping processes in the boss is -shutting down. All started components will be shut down now (more precisely, -asked to terminate by their own, if they fail to comply, other parts of -the boss process will try to force them). -

BIND10_CONFIGURATOR_TASK performing task %1 on %2

-A debug message. The configurator is about to perform one task of the plan it -is currently executing on the named component. -

BIND10_INVALID_STATISTICS_DATA invalid specification of statistics data specified

-An error was encountered when the boss module specified -statistics data which is invalid for the boss specification file. -

BIND10_INVALID_USER invalid user: %1

-The boss process was started with the -u option, to drop root privileges -and continue running as the specified user, but the user is unknown. -

BIND10_KILLING_ALL_PROCESSES killing all started processes

-The boss module was not able to start every process it needed to start -during startup, and will now kill the processes that did get started. -

BIND10_KILL_PROCESS killing process %1

-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 -

BIND10_LOST_SOCKET_CONSUMER consumer %1 of sockets disconnected, considering all its sockets closed

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

BIND10_MSGQ_ALREADY_RUNNING msgq daemon already running, cannot start

-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 -another instance of BIND10, with the same msgq domain socket, is -running, which needs to be stopped. -

BIND10_MSGQ_DISAPPEARED msgq channel disappeared

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

BIND10_NO_SOCKET couldn't send a socket for token %1 because of error: %2

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

BIND10_PROCESS_ENDED process %2 of %1 ended with status %3

-This indicates a process started previously terminated. The process id -and component owning the process are indicated, as well as the exit code. -This doesn't distinguish if the process was supposed to terminate or not. -

BIND10_READING_BOSS_CONFIGURATION reading boss configuration

-The boss process is starting up, and will now process the initial -configuration, as received from the configuration manager. -

BIND10_RECEIVED_COMMAND received command: %1

-The boss module received a command and shall now process it. The command -is printed. -

BIND10_RECEIVED_NEW_CONFIGURATION received new configuration: %1

-The boss module received a configuration update and is going to apply -it now. The new configuration is printed. -

BIND10_RECEIVED_SIGNAL received signal %1

-The boss module received the given signal. -

BIND10_RESURRECTED_PROCESS resurrected %1 (PID %2)

-The given process has been restarted successfully, and is now running -with the given process id. -

BIND10_RESURRECTING_PROCESS resurrecting dead %1 process...

-The given process has ended unexpectedly, and is now restarted. -

BIND10_SELECT_ERROR error in select() call: %1

-There was a fatal error in the call to select(), used to see if a child -process has ended or if there is a message on the message bus. This -should not happen under normal circumstances and is considered fatal, -so BIND 10 will now shut down. The specific error is printed. -

BIND10_SEND_SIGKILL sending SIGKILL to %1 (PID %2)

-The boss module is sending a SIGKILL signal to the given process. -

BIND10_SEND_SIGTERM sending SIGTERM to %1 (PID %2)

-The boss module is sending a SIGTERM signal to the given process. -

BIND10_SETUID setting UID to %1

-The boss switches the user it runs as to the given UID. -

BIND10_SHUTDOWN stopping the server

-The boss process received a command or signal telling it to shut down. -It will send a shutdown command to each process. The processes that do -not shut down will then receive a SIGTERM signal. If that doesn't work, -it shall send SIGKILL signals to the processes still alive. -

BIND10_SHUTDOWN_COMPLETE all processes ended, shutdown complete

-All child processes have been stopped, and the boss process will now -stop itself. -

BIND10_SOCKCREATOR_BAD_CAUSE unknown error cause from socket creator: %1

-The socket creator reported an error when creating a socket. But the function -which failed is unknown (not one of 'S' for socket or 'B' for bind). -

BIND10_SOCKCREATOR_BAD_RESPONSE unknown response for socket request: %1

-The boss requested a socket from the creator, but the answer is unknown. This -looks like a programmer error. -

BIND10_SOCKCREATOR_EOF eof while expecting data from socket creator

-There should be more data from the socket creator, but it closed the socket. -It probably crashed. -

BIND10_SOCKCREATOR_INIT initializing socket creator parser

-The boss module initializes routines for parsing the socket creator -protocol. -

BIND10_SOCKCREATOR_KILL killing the socket creator

-The socket creator is being terminated the aggressive way, by sending it -sigkill. This should not happen usually. -

BIND10_SOCKCREATOR_TERMINATE terminating socket creator

-The boss module sends a request to terminate to the socket creator. -

BIND10_SOCKCREATOR_TRANSPORT_ERROR transport error when talking to the socket creator: %1

-Either sending or receiving data from the socket creator failed with the given -error. The creator probably crashed or some serious OS-level problem happened, -as the communication happens only on local host. -

BIND10_SOCKET_CREATED successfully created socket %1

-The socket creator successfully created and sent a requested socket, it has -the given file number. -

BIND10_SOCKET_ERROR error on %1 call in the creator: %2/%3

-The socket creator failed to create the requested socket. It failed on the -indicated OS API function with given error. -

BIND10_SOCKET_GET requesting socket [%1]:%2 of type %3 from the creator

-The boss forwards a request for a socket to the socket creator. -

BIND10_STARTED_CC started configuration/command session

-Debug message given when BIND 10 has successfull started the object that -handles configuration and commands. -

BIND10_STARTED_PROCESS started %1

-The given process has successfully been started. -

BIND10_STARTED_PROCESS_PID started %1 (PID %2)

-The given process has successfully been started, and has the given PID. -

BIND10_STARTING starting BIND10: %1

-Informational message on startup that shows the full version. -

BIND10_STARTING_CC starting configuration/command session

-Informational message given when BIND 10 is starting the session object -that handles configuration and commands. -

BIND10_STARTING_PROCESS starting process %1

-The boss module is starting the given process. -

BIND10_STARTING_PROCESS_PORT starting process %1 (to listen on port %2)

-The boss module is starting the given process, which will listen on the -given port number. -

BIND10_STARTING_PROCESS_PORT_ADDRESS starting process %1 (to listen on %2#%3)

-The boss module is starting the given process, which will listen on the -given address and port number (written as <address>#<port>). -

BIND10_STARTUP_COMPLETE BIND 10 started

-All modules have been successfully started, and BIND 10 is now running. -

BIND10_STARTUP_ERROR error during startup: %1

-There was a fatal error when BIND10 was trying to start. The error is -shown, and BIND10 will now shut down. -

BIND10_STARTUP_UNEXPECTED_MESSAGE unrecognised startup message %1

-During the startup process, a number of messages are exchanged between the -Boss process and the processes it starts. This error is output when a -message received by the Boss process is recognised as being of the -correct format but is unexpected. It may be that processes are starting -of sequence. -

BIND10_STARTUP_UNRECOGNISED_MESSAGE unrecognised startup message %1

-During the startup process, a number of messages are exchanged between the -Boss process and the processes it starts. This error is output when a -message received by the Boss process is not recognised. -

BIND10_START_AS_NON_ROOT_AUTH starting b10-auth as a user, not root. This might fail.

-The authoritative server is being started or restarted without root privileges. -If the module needs these privileges, it may have problems starting. -Note that this issue should be resolved by the pending 'socket-creator' -process; once that has been implemented, modules should not need root -privileges anymore. See tickets #800 and #801 for more information. -

BIND10_START_AS_NON_ROOT_RESOLVER starting b10-resolver as a user, not root. This might fail.

-The resolver is being started or restarted without root privileges. -If the module needs these privileges, it may have problems starting. -Note that this issue should be resolved by the pending 'socket-creator' -process; once that has been implemented, modules should not need root -privileges anymore. See tickets #800 and #801 for more information. -

BIND10_STOP_PROCESS asking %1 to shut down

-The boss module is sending a shutdown command to the given module over -the message channel. -

BIND10_UNKNOWN_CHILD_PROCESS_ENDED unknown child pid %1 exited

-An unknown child process has exited. The PID is printed, but no further -action will be taken by the boss process. -

BIND10_WAIT_CFGMGR waiting for configuration manager process to initialize

-The configuration manager process is so critical to operation of BIND 10 -that after starting it, the Boss module will wait for it to initialize -itself before continuing. This debug message is produced during the -wait and may be output zero or more times depending on how long it takes -the configuration manager to start up. The total length of time Boss -will wait for the configuration manager before reporting an error is -set with the command line --wait switch, which has a default value of -ten seconds. -

CACHE_ENTRY_MISSING_RRSET missing RRset to generate message for %1

-The cache tried to generate the complete answer message. It knows the structure -of the message, but some of the RRsets to be put there are not in cache (they -probably expired already). Therefore it pretends the message was not found. -

CACHE_LOCALZONE_FOUND found entry with key %1 in local zone data

-Debug message, noting that the requested data was successfully found in the -local zone data of the cache. -

CACHE_LOCALZONE_UNKNOWN entry with key %1 not found in local zone data

-Debug message. The requested data was not found in the local zone data. -

CACHE_LOCALZONE_UPDATE updating local zone element at key %1

-Debug message issued when there's update to the local zone section of cache. -

CACHE_MESSAGES_DEINIT deinitialized message cache

-Debug message. It is issued when the server deinitializes the message cache. -

CACHE_MESSAGES_EXPIRED found an expired message entry for %1 in the message cache

-Debug message. The requested data was found in the message cache, but it -already expired. Therefore the cache removes the entry and pretends it found -nothing. -

CACHE_MESSAGES_FOUND found a message entry for %1 in the message cache

-Debug message. We found the whole message in the cache, so it can be returned -to user without any other lookups. -

CACHE_MESSAGES_INIT initialized message cache for %1 messages of class %2

-Debug message issued when a new message cache is issued. It lists the class -of messages it can hold and the maximum size of the cache. -

CACHE_MESSAGES_REMOVE removing old instance of %1/%2/%3 first

-Debug message. This may follow CACHE_MESSAGES_UPDATE and indicates that, while -updating, the old instance is being removed prior of inserting a new one. -

CACHE_MESSAGES_UNCACHEABLE not inserting uncacheable message %1/%2/%3

-Debug message, noting that the given message can not be cached. This is because -there's no SOA record in the message. See RFC 2308 section 5 for more -information. -

CACHE_MESSAGES_UNKNOWN no entry for %1 found in the message cache

-Debug message. The message cache didn't find any entry for the given key. -

CACHE_MESSAGES_UPDATE updating message entry %1/%2/%3

-Debug message issued when the message cache is being updated with a new -message. Either the old instance is removed or, if none is found, new one -is created. -

CACHE_RESOLVER_DEEPEST looking up deepest NS for %1/%2

-Debug message. The resolver cache is looking up the deepest known nameserver, -so the resolution doesn't have to start from the root. -

CACHE_RESOLVER_INIT initializing resolver cache for class %1

-Debug message. The resolver cache is being created for this given class. -

CACHE_RESOLVER_INIT_INFO initializing resolver cache for class %1

-Debug message, the resolver cache is being created for this given class. The -difference from CACHE_RESOLVER_INIT is only in different format of passed -information, otherwise it does the same. -

CACHE_RESOLVER_LOCAL_MSG message for %1/%2 found in local zone data

-Debug message. The resolver cache found a complete message for the user query -in the zone data. -

CACHE_RESOLVER_LOCAL_RRSET RRset for %1/%2 found in local zone data

-Debug message. The resolver cache found a requested RRset in the local zone -data. -

CACHE_RESOLVER_LOOKUP_MSG looking up message in resolver cache for %1/%2

-Debug message. The resolver cache is trying to find a message to answer the -user query. -

CACHE_RESOLVER_LOOKUP_RRSET looking up RRset in resolver cache for %1/%2

-Debug message. The resolver cache is trying to find an RRset (which usually -originates as internally from resolver). -

CACHE_RESOLVER_NO_QUESTION answer message for %1/%2 has empty question section

-The cache tried to fill in found data into the response message. But it -discovered the message contains no question section, which is invalid. -This is likely a programmer error, please submit a bug report. -

CACHE_RESOLVER_UNKNOWN_CLASS_MSG no cache for class %1

-Debug message. While trying to lookup a message in the resolver cache, it was -discovered there's no cache for this class at all. Therefore no message is -found. -

CACHE_RESOLVER_UNKNOWN_CLASS_RRSET no cache for class %1

-Debug message. While trying to lookup an RRset in the resolver cache, it was -discovered there's no cache for this class at all. Therefore no data is found. -

CACHE_RESOLVER_UPDATE_MSG updating message for %1/%2/%3

-Debug message. The resolver is updating a message in the cache. -

CACHE_RESOLVER_UPDATE_RRSET updating RRset for %1/%2/%3

-Debug message. The resolver is updating an RRset in the cache. -

CACHE_RESOLVER_UPDATE_UNKNOWN_CLASS_MSG no cache for class %1

-Debug message. While trying to insert a message into the cache, it was -discovered that there's no cache for the class of message. Therefore -the message will not be cached. -

CACHE_RESOLVER_UPDATE_UNKNOWN_CLASS_RRSET no cache for class %1

-Debug message. While trying to insert an RRset into the cache, it was -discovered that there's no cache for the class of the RRset. Therefore -the message will not be cached. -

CACHE_RRSET_EXPIRED found expired RRset %1/%2/%3

-Debug message. The requested data was found in the RRset cache. However, it is -expired, so the cache removed it and is going to pretend nothing was found. -

CACHE_RRSET_INIT initializing RRset cache for %1 RRsets of class %2

-Debug message. The RRset cache to hold at most this many RRsets for the given -class is being created. -

CACHE_RRSET_LOOKUP looking up %1/%2/%3 in RRset cache

-Debug message. The resolver is trying to look up data in the RRset cache. -

CACHE_RRSET_NOT_FOUND no RRset found for %1/%2/%3 in cache

-Debug message which can follow CACHE_RRSET_LOOKUP. This means the data is not -in the cache. -

CACHE_RRSET_REMOVE_OLD removing old RRset for %1/%2/%3 to make space for new one

-Debug message which can follow CACHE_RRSET_UPDATE. During the update, the cache -removed an old instance of the RRset to replace it with the new one. -

CACHE_RRSET_UNTRUSTED not replacing old RRset for %1/%2/%3, it has higher trust level

-Debug message which can follow CACHE_RRSET_UPDATE. The cache already holds the -same RRset, but from more trusted source, so the old one is kept and new one -ignored. -

CACHE_RRSET_UPDATE updating RRset %1/%2/%3 in the cache

-Debug message. The RRset is updating its data with this given RRset. -

CC_ASYNC_READ_FAILED asynchronous read failed

-This marks a low level error, we tried to read data from the message queue -daemon asynchronously, but the ASIO library returned an error. -

CC_CONN_ERROR error connecting to message queue (%1)

-It is impossible to reach the message queue daemon for the reason given. It -is unlikely there'll be reason for whatever program this currently is to -continue running, as the communication with the rest of BIND 10 is vital -for the components. -

CC_DISCONNECT disconnecting from message queue daemon

-The library is disconnecting from the message queue daemon. This debug message -indicates that the program is trying to shut down gracefully. -

CC_ESTABLISH trying to establish connection with message queue daemon at %1

-This debug message indicates that the command channel library is about to -connect to the message queue daemon, which should be listening on the UNIX-domain -socket listed in the output. -

CC_ESTABLISHED successfully connected to message queue daemon

-This debug message indicates that the connection was successfully made, this -should follow CC_ESTABLISH. -

CC_GROUP_RECEIVE trying to receive a message

-Debug message, noting that a message is expected to come over the command -channel. -

CC_GROUP_RECEIVED message arrived ('%1', '%2')

-Debug message, noting that we successfully received a message (its envelope and -payload listed). This follows CC_GROUP_RECEIVE, but might happen some time -later, depending if we waited for it or just polled. -

CC_GROUP_SEND sending message '%1' to group '%2'

-Debug message, we're about to send a message over the command channel. -

CC_INVALID_LENGTHS invalid length parameters (%1, %2)

-This happens when garbage comes over the command channel or some kind of -confusion happens in the program. The data received from the socket make no -sense if we interpret it as lengths of message. The first one is total length -of the message; the second is the length of the header. The header -and its length (2 bytes) is counted in the total length. -

CC_LENGTH_NOT_READY length not ready

-There should be data representing the length of message on the socket, but it -is not there. -

CC_NO_MESSAGE no message ready to be received yet

-The program polled for incoming messages, but there was no message waiting. -This is a debug message which may happen only after CC_GROUP_RECEIVE. -

CC_NO_MSGQ unable to connect to message queue (%1)

-It isn't possible to connect to the message queue daemon, for reason listed. -It is unlikely any program will be able continue without the communication. -

CC_READ_ERROR error reading data from command channel (%1)

-A low level error happened when the library tried to read data from the -command channel socket. The reason is listed. -

CC_READ_EXCEPTION error reading data from command channel (%1)

-We received an exception while trying to read data from the command -channel socket. The reason is listed. -

CC_REPLY replying to message from '%1' with '%2'

-Debug message, noting we're sending a response to the original message -with the given envelope. -

CC_SET_TIMEOUT setting timeout to %1ms

-Debug message. A timeout for which the program is willing to wait for a reply -is being set. -

CC_START_READ starting asynchronous read

-Debug message. From now on, when a message (or command) comes, it'll wake the -program and the library will automatically pass it over to correct place. -

CC_SUBSCRIBE subscribing to communication group %1

-Debug message. The program wants to receive messages addressed to this group. -

CC_TIMEOUT timeout reading data from command channel

-The program waited too long for data from the command channel (usually when it -sent a query to different program and it didn't answer for whatever reason). -

CC_UNSUBSCRIBE unsubscribing from communication group %1

-Debug message. The program no longer wants to receive messages addressed to -this group. -

CC_WRITE_ERROR error writing data to command channel (%1)

-A low level error happened when the library tried to write data to the command -channel socket. -

CC_ZERO_LENGTH invalid message length (0)

-The library received a message length being zero, which makes no sense, since -all messages must contain at least the envelope. -

CFGMGR_AUTOMATIC_CONFIG_DATABASE_UPDATE Updating configuration database from version %1 to %2

-An older version of the configuration database has been found, from which -there was an automatic upgrade path to the current version. These changes -are now applied, and no action from the administrator is necessary. -

CFGMGR_BAD_UPDATE_RESPONSE_FROM_MODULE Unable to parse response from module %1: %2

-The configuration manager sent a configuration update to a module, but -the module responded with an answer that could not be parsed. The answer -message appears to be invalid JSON data, or not decodable to a string. -This is likely to be a problem in the module in question. The update is -assumed to have failed, and will not be stored. -

CFGMGR_CC_SESSION_ERROR Error connecting to command channel: %1

-The configuration manager daemon was unable to connect to the messaging -system. The most likely cause is that msgq is not running. -

CFGMGR_DATA_READ_ERROR error reading configuration database from disk: %1

-There was a problem reading the persistent configuration data as stored -on disk. The file may be corrupted, or it is of a version from where -there is no automatic upgrade path. The file needs to be repaired or -removed. The configuration manager daemon will now shut down. -

CFGMGR_IOERROR_WHILE_WRITING_CONFIGURATION Unable to write configuration file; configuration not stored: %1

-There was an IO error from the system while the configuration manager -was trying to write the configuration database to disk. The specific -error is given. The most likely cause is that the directory where -the file is stored does not exist, or is not writable. The updated -configuration is not stored. -

CFGMGR_OSERROR_WHILE_WRITING_CONFIGURATION Unable to write configuration file; configuration not stored: %1

-There was an OS error from the system while the configuration manager -was trying to write the configuration database to disk. The specific -error is given. The most likely cause is that the system does not have -write access to the configuration database file. The updated -configuration is not stored. -

CFGMGR_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down

-There was a keyboard interrupt signal to stop the cfgmgr daemon. The -daemon will now shut down. -

CMDCTL_BAD_CONFIG_DATA error in config data: %1

-There was an error reading the updated configuration data. The specific -error is printed. -

CMDCTL_BAD_PASSWORD bad password for user: %1

-A login attempt was made to b10-cmdctl, but the password was wrong. -Users can be managed with the tool b10-cmdctl-usermgr. -

CMDCTL_CC_SESSION_ERROR error reading from cc channel: %1

-There was a problem reading from the command and control channel. The -most likely cause is that the message bus daemon is not running. -

CMDCTL_CC_SESSION_TIMEOUT timeout on cc channel

-A timeout occurred when waiting for essential data from the cc session. -This usually occurs when b10-cfgmgr is not running or not responding. -Since we are waiting for essential information, this is a fatal error, -and the cmdctl daemon will now shut down. -

CMDCTL_COMMAND_ERROR error in command %1 to module %2: %3

-An error was encountered sending the given command to the given module. -Either there was a communication problem with the module, or the module -was not able to process the command, and sent back an error. The -specific error is printed in the message. -

CMDCTL_COMMAND_SENT command '%1' to module '%2' was sent

-This debug message indicates that the given command has been sent to -the given module. -

CMDCTL_NO_SUCH_USER username not found in user database: %1

-A login attempt was made to b10-cmdctl, but the username was not known. -Users can be added with the tool b10-cmdctl-usermgr. -

CMDCTL_NO_USER_ENTRIES_READ failed to read user information, all users will be denied

-The b10-cmdctl daemon was unable to find any user data in the user -database file. Either it was unable to read the file (in which case -this message follows a message CMDCTL_USER_DATABASE_READ_ERROR -containing a specific error), or the file was empty. Users can be added -with the tool b10-cmdctl-usermgr. -

CMDCTL_SEND_COMMAND sending command %1 to module %2

-This debug message indicates that the given command is being sent to -the given module. -

CMDCTL_SSL_SETUP_FAILURE_USER_DENIED failed to create an SSL connection (user denied): %1

-The user was denied because the SSL connection could not successfully -be set up. The specific error is given in the log message. Possible -causes may be that the ssl request itself was bad, or the local key or -certificate file could not be read. -

CMDCTL_STARTED cmdctl is listening for connections on %1:%2

-The cmdctl daemon has started and is now listening for connections. -

CMDCTL_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down

-There was a keyboard interrupt signal to stop the cmdctl daemon. The -daemon will now shut down. -

CMDCTL_UNCAUGHT_EXCEPTION uncaught exception: %1

-The b10-cmdctl daemon 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 message -is printed. -

CMDCTL_USER_DATABASE_READ_ERROR failed to read user database file %1: %2

-The b10-cmdctl daemon was unable to read the user database file. The -file may be unreadable for the daemon, or it may be corrupted. In the -latter case, it can be recreated with b10-cmdctl-usermgr. The specific -error is printed in the log message. -

CONFIG_CCSESSION_MSG error in CC session message: %1

-There was a problem with an incoming message on the command and control -channel. The message does not appear to be a valid command, and is -missing a required element or contains an unknown data format. This -most likely means that another BIND10 module is sending a bad message. -The message itself is ignored by this module. -

CONFIG_CCSESSION_MSG_INTERNAL error handling CC session message: %1

-There was an internal problem handling an incoming message on the command -and control channel. An unexpected exception was thrown, details of -which are appended to the message. The module will continue to run, -but will not send back an answer. -

-The most likely cause of this error is a programming error. Please raise -a bug report. -

CONFIG_GET_FAIL error getting configuration from cfgmgr: %1

-The configuration manager returned an error when this module requested -the configuration. The full error message answer from the configuration -manager is appended to the log error. The most likely cause is that -the module is of a different (command specification) version than the -running configuration manager. -

CONFIG_GET_FAILED error getting configuration from cfgmgr: %1

-The configuration manager returned an error response when the module -requested its configuration. The full error message answer from the -configuration manager is appended to the log error. -

CONFIG_JSON_PARSE JSON parse error in %1: %2

-There was an error parsing the JSON file. The given file does not appear -to be in valid JSON format. Please verify that the filename is correct -and that the contents are valid JSON. -

CONFIG_LOG_CONFIG_ERRORS error(s) in logging configuration: %1

-There was a logging configuration update, but the internal validator -for logging configuration found that it contained errors. The errors -are shown, and the update is ignored. -

CONFIG_LOG_EXPLICIT will use logging configuration for explicitly-named logger %1

-This is a debug message. When processing the "loggers" part of the -configuration file, the configuration library found an entry for the named -logger that matches the logger specification for the program. The logging -configuration for the program will be updated with the information. -

CONFIG_LOG_IGNORE_EXPLICIT ignoring logging configuration for explicitly-named logger %1

-This is a debug message. When processing the "loggers" part of the -configuration file, the configuration library found an entry for the -named logger. As this does not match the logger specification for the -program, it has been ignored. -

CONFIG_LOG_IGNORE_WILD ignoring logging configuration for wildcard logger %1

-This is a debug message. When processing the "loggers" part of the -configuration file, the configuration library found the named wildcard -entry (one containing the "*" character) that matched a logger already -matched by an explicitly named entry. The configuration is ignored. -

CONFIG_LOG_WILD_MATCH will use logging configuration for wildcard logger %1

-This is a debug message. When processing the "loggers" part of -the configuration file, the configuration library found the named -wildcard entry (one containing the "*" character) that matches a logger -specification in the program. The logging configuration for the program -will be updated with the information. -

CONFIG_MOD_SPEC_FORMAT module specification error in %1: %2

-The given file does not appear to be a valid specification file: details -are included in the message. Please verify that the filename is correct -and that its contents are a valid BIND10 module specification. -

CONFIG_MOD_SPEC_REJECT module specification rejected by cfgmgr: %1

-The specification file for this module was rejected by the configuration -manager. The full error message answer from the configuration manager is -appended to the log error. The most likely cause is that the module is of -a different (specification file) version than the running configuration -manager. -

CONFIG_OPEN_FAIL error opening %1: %2

-There was an error opening the given file. The reason for the failure -is included in the message. -

DATASRC_CACHE_CREATE creating the hotspot cache

-This is a debug message issued during startup when the hotspot cache -is created. -

DATASRC_CACHE_DESTROY destroying the hotspot cache

-Debug information. The hotspot cache is being destroyed. -

DATASRC_CACHE_DISABLE disabling the hotspot cache

-A debug message issued when the hotspot cache is disabled. -

DATASRC_CACHE_ENABLE enabling the hotspot cache

-A debug message issued when the hotspot cache is enabled. -

DATASRC_CACHE_EXPIRED item '%1' in the hotspot cache has expired

-A debug message issued when a hotspot cache lookup located the item but it -had expired. The item was removed and the program proceeded as if the item -had not been found. -

DATASRC_CACHE_FOUND the item '%1' was found

-Debug information. An item was successfully located in the hotspot cache. -

DATASRC_CACHE_FULL hotspot cache is full, dropping oldest

-Debug information. After inserting an item into the hotspot cache, the -maximum number of items was exceeded, so the least recently used item will -be dropped. This should be directly followed by CACHE_REMOVE. -

DATASRC_CACHE_INSERT inserting item '%1' into the hotspot cache

-A debug message indicating that a new item is being inserted into the hotspot -cache. -

DATASRC_CACHE_NOT_FOUND the item '%1' was not found in the hotspot cache

-A debug message issued when hotspot cache was searched for the specified -item but it was not found. -

DATASRC_CACHE_OLD_FOUND older instance of hotspot cache item '%1' found, replacing

-Debug information. While inserting an item into the hotspot cache, an older -instance of an item with the same name was found; the old instance will be -removed. This will be directly followed by CACHE_REMOVE. -

DATASRC_CACHE_REMOVE removing '%1' from the hotspot cache

-Debug information. An item is being removed from the hotspot cache. -

DATASRC_CACHE_SLOTS setting the hotspot cache size to '%1', dropping '%2' items

-The maximum allowed number of items of the hotspot cache is set to the given -number. If there are too many, some of them will be dropped. The size of 0 -means no limit. -

DATASRC_DATABASE_COVER_NSEC_UNSUPPORTED %1 doesn't support DNSSEC when asked for NSEC data covering %2

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

DATASRC_DATABASE_FIND_RECORDS looking in datasource %1 for record %2/%3/%4

-Debug information. The database data source is looking up records with the given -name and type in the database. -

DATASRC_DATABASE_FIND_TTL_MISMATCH TTL values differ in %1 for elements of %2/%3/%4, setting to %5

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

DATASRC_DATABASE_FOUND_ANY search in datasource %1 resulted in returning all records of %2

-The data returned by the database backend contained data for the given domain -name, so all the RRsets of the domain are returned. -

DATASRC_DATABASE_FOUND_CNAME search in datasource %1 for %2/%3/%4 found CNAME, resulting in %5

-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.) -

DATASRC_DATABASE_FOUND_DELEGATION Found delegation at %2 in %1

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

DATASRC_DATABASE_FOUND_DELEGATION_EXACT search in datasource %1 for %2/%3/%4 found delegation at %5

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

DATASRC_DATABASE_FOUND_DNAME Found DNAME at %2 in %1

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

DATASRC_DATABASE_FOUND_EMPTY_NONTERMINAL empty non-terminal %2 in %1

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

DATASRC_DATABASE_FOUND_NXDOMAIN search in datasource %1 resulted in NXDOMAIN for %2/%3/%4

-The data returned by the database backend did not contain any data for the given -domain name, class and type. -

DATASRC_DATABASE_FOUND_NXRRSET search in datasource %1 for %2/%3/%4 resulted in NXRRSET

-The data returned by the database backend contained data for the given domain -name and class, but not for the given type. -

DATASRC_DATABASE_FOUND_NXRRSET_NSEC search in datasource %1 for %2/%3/%4 resulted in RRset %5

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

DATASRC_DATABASE_FOUND_RRSET search in datasource %1 resulted in RRset %5

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

DATASRC_DATABASE_ITERATE iterating zone %1

-The program is reading the whole zone, eg. not searching for data, but going -through each of the RRsets there. -

DATASRC_DATABASE_ITERATE_END iterating zone finished

-While iterating through the zone, the program reached end of the data. -

DATASRC_DATABASE_ITERATE_NEXT next RRset in zone is %1/%2

-While iterating through the zone, the program extracted next RRset from it. -The name and RRtype of the RRset is indicated in the message. -

DATASRC_DATABASE_ITERATE_TTL_MISMATCH TTL values differ for RRs of %1/%2/%3, setting to %4

-While iterating through the zone, the time to live for RRs of the given RRset -were found to be different. 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. -

DATASRC_DATABASE_JOURNALREADER_END %1/%2 on %3 from %4 to %5

-This is a debug message indicating that the program (successfully) -reaches the end of sequences of a zone's differences. The zone's name -and class, database name, and the start and end serials are shown in -the message. -

DATASRC_DATABASE_JOURNALREADER_NEXT %1/%2 in %3/%4 on %5

-This is a debug message indicating that the program retrieves one -difference in difference sequences of a zone and successfully converts -it to an RRset. The zone's name and class, database name, and the -name and RR type of the retrieved diff are shown in the message. -

DATASRC_DATABASE_JOURNALREADER_START %1/%2 on %3 from %4 to %5

-This is a debug message indicating that the program starts reading -a zone's difference sequences from a database-based data source. The -zone's name and class, database name, and the start and end serials -are shown in the message. -

DATASRC_DATABASE_JOURNALREADR_BADDATA failed to convert a diff to RRset in %1/%2 on %3 between %4 and %5: %6

-This is an error message indicating that a zone's diff is broken and -the data source library failed to convert it to a valid RRset. The -most likely cause of this is that someone has manually modified the -zone's diff in the database and inserted invalid data as a result. -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. -

DATASRC_DATABASE_NO_MATCH not match for %2/%3/%4 in %1

-No match (not even a wildcard) was found in the named data source for the given -name/type/class in the data source. -

DATASRC_DATABASE_UPDATER_COMMIT updates committed for '%1/%2' on %3

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

DATASRC_DATABASE_UPDATER_COMMIT (1) updates committed for '%1/%2' on %3

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

DATASRC_DATABASE_UPDATER_CREATED zone updater created for '%1/%2' on %3

-Debug information. A zone updater object is created to make updates to -the shown zone on the shown backend database. -

DATASRC_DATABASE_UPDATER_CREATED (1) zone updater created for '%1/%2' on %3

-Debug information. A zone updater object is created to make updates to -the shown zone on the shown backend database. -

DATASRC_DATABASE_UPDATER_DESTROYED zone updater destroyed for '%1/%2' on %3

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

DATASRC_DATABASE_UPDATER_DESTROYED (1) zone updater destroyed for '%1/%2' on %3

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

DATASRC_DATABASE_UPDATER_ROLLBACK zone updates roll-backed for '%1/%2' on %3

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

DATASRC_DATABASE_UPDATER_ROLLBACK (1) zone updates roll-backed for '%1/%2' on %3

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

DATASRC_DATABASE_UPDATER_ROLLBACKFAIL failed to roll back zone updates for '%1/%2' on %3: %4

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

DATASRC_DATABASE_UPDATER_ROLLBACKFAIL (1) failed to roll back zone updates for '%1/%2' on %3: %4

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

DATASRC_DATABASE_WILDCARD_ANY search in datasource %1 resulted in wildcard match type ANY on %2

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

DATASRC_DATABASE_WILDCARD_CANCEL_NS canceled wildcard match on %3 because %2 contains NS (data source %1)

-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 -instead. -

DATASRC_DATABASE_WILDCARD_CANCEL_SUB wildcard %2 can't be used to construct %3 because %4 exists in %1

-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). -

DATASRC_DATABASE_WILDCARD_CNAME search in datasource %1 for %2/%3/%4 found wildcard CNAME at %5, resulting in %6

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

DATASRC_DATABASE_WILDCARD_EMPTY found subdomains of %2 which is a wildcard match for %3 in %1

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

DATASRC_DATABASE_WILDCARD_MATCH search in datasource %1 resulted in wildcard match at %5 with RRset %6

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

DATASRC_DATABASE_WILDCARD_NS search in datasource %1 for %2/%3/%4 found wildcard delegation at %5, resulting in %6

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

DATASRC_DATABASE_WILDCARD_NXRRSET search in datasource %1 for %2/%3/%4 resulted in wildcard NXRRSET at %5

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

DATASRC_DO_QUERY handling query for '%1/%2'

-A debug message indicating that a query for the given name and RR type is being -processed. -

DATASRC_MEM_ADD_RRSET adding RRset '%1/%2' into zone '%3'

-Debug information. An RRset is being added to the in-memory data source. -

DATASRC_MEM_ADD_WILDCARD adding wildcards for '%1'

-This is a debug message issued during the processing of a wildcard -name. The internal domain name tree is scanned and some nodes are -specially marked to allow the wildcard lookup to succeed. -

DATASRC_MEM_ADD_ZONE adding zone '%1/%2'

-Debug information. A zone is being added into the in-memory data source. -

DATASRC_MEM_ANY_SUCCESS ANY query for '%1' successful

-Debug information. The domain was found and an ANY type query is being answered -by providing everything found inside the domain. -

DATASRC_MEM_CNAME CNAME at the domain '%1'

-Debug information. The requested domain is an alias to a different domain, -returning the CNAME instead. -

DATASRC_MEM_CNAME_COEXIST can't add data to CNAME in domain '%1'

-This is the same problem as in MEM_CNAME_TO_NONEMPTY, but it happened the -other way around -- adding some other data to CNAME. -

DATASRC_MEM_CNAME_TO_NONEMPTY can't add CNAME to domain with other data in '%1'

-Someone or something tried to add a CNAME into a domain that already contains -some other data. But the protocol forbids coexistence of CNAME with anything -(RFC 1034, section 3.6.2). This indicates a problem with provided data. -

DATASRC_MEM_CREATE creating zone '%1' in '%2' class

-Debug information. A representation of a zone for the in-memory data source is -being created. -

DATASRC_MEM_DELEG_FOUND delegation found at '%1'

-Debug information. A delegation point was found above the requested record. -

DATASRC_MEM_DESTROY destroying zone '%1' in '%2' class

-Debug information. A zone from in-memory data source is being destroyed. -

DATASRC_MEM_DNAME_ENCOUNTERED encountered a DNAME

-Debug information. While searching for the requested domain, a DNAME was -encountered on the way. This may lead to redirection to a different domain and -stop the search. -

DATASRC_MEM_DNAME_FOUND DNAME found at '%1'

-Debug information. A DNAME was found instead of the requested information. -

DATASRC_MEM_DNAME_NS DNAME and NS can't coexist in non-apex domain '%1'

-A request was made for DNAME and NS records to be put into the same -domain which is not the apex (the top of the zone). This is forbidden -by RFC 2672 (section 3) and indicates a problem with provided data. -

DATASRC_MEM_DOMAIN_EMPTY requested domain '%1' is empty

-Debug information. The requested domain exists in the tree of domains, but -it is empty. Therefore it doesn't contain the requested resource type. -

DATASRC_MEM_DUP_RRSET duplicate RRset '%1/%2'

-An RRset is being inserted into in-memory data source for a second time. The -original version must be removed first. Note that loading master files where an -RRset is split into multiple locations is not supported yet. -

DATASRC_MEM_EXACT_DELEGATION delegation at the exact domain '%1'

-Debug information. There's a NS record at the requested domain. This means -this zone is not authoritative for the requested domain, but a delegation -should be followed. The requested domain is an apex of some zone. -

DATASRC_MEM_FIND find '%1/%2'

-Debug information. A search for the requested RRset is being started. -

DATASRC_MEM_FIND_ZONE looking for zone '%1'

-Debug information. A zone object for this zone is being searched for in the -in-memory data source. -

DATASRC_MEM_LOAD loading zone '%1' from file '%2'

-Debug information. The content of master file is being loaded into the memory. -

DATASRC_MEM_NOT_FOUND requested domain '%1' not found

-Debug information. The requested domain does not exist. -

DATASRC_MEM_NS_ENCOUNTERED encountered a NS

-Debug information. While searching for the requested domain, a NS was -encountered on the way (a delegation). This may lead to stop of the search. -

DATASRC_MEM_NXRRSET no such type '%1' at '%2'

-Debug information. The domain exists, but it doesn't hold any record of the -requested type. -

DATASRC_MEM_OUT_OF_ZONE domain '%1' doesn't belong to zone '%2'

-It was attempted to add the domain into a zone that shouldn't have it -(eg. the domain is not subdomain of the zone origin). This indicates a -problem with provided data. -

DATASRC_MEM_RENAME renaming RRset from '%1' to '%2'

-Debug information. A RRset is being generated from a different RRset (most -probably a wildcard). So it must be renamed to whatever the user asked for. In -fact, it's impossible to rename RRsets with our libraries, so a new one is -created and all resource records are copied over. -

DATASRC_MEM_SINGLETON trying to add multiple RRs for domain '%1' and type '%2'

-Some resource types are singletons -- only one is allowed in a domain -(for example CNAME or SOA). This indicates a problem with provided data. -

DATASRC_MEM_SUCCESS query for '%1/%2' successful

-Debug information. The requested record was found. -

DATASRC_MEM_SUPER_STOP stopped at superdomain '%1', domain '%2' is empty

-Debug information. The search stopped at a superdomain of the requested -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). -

DATASRC_MEM_SWAP swapping contents of two zone representations ('%1' and '%2')

-Debug information. The contents of two in-memory zones are being exchanged. -This is usual practice to do some manipulation in exception-safe manner -- the -new data are prepared in a different zone object and when it works, they are -swapped. The old one contains the new data and the other one can be safely -destroyed. -

DATASRC_MEM_WILDCARD_CANCEL wildcard match canceled for '%1'

-Debug information. A domain above wildcard was reached, but there's something -below the requested domain. Therefore the wildcard doesn't apply here. This -behaviour is specified by RFC 1034, section 4.3.3 -

DATASRC_MEM_WILDCARD_DNAME DNAME record in wildcard domain '%1'

-The software refuses to load DNAME records into a wildcard domain. It isn't -explicitly forbidden, but the protocol is ambiguous about how this should -behave and BIND 9 refuses that as well. Please describe your intention using -different tools. -

DATASRC_MEM_WILDCARD_NS NS record in wildcard domain '%1'

-The software refuses to load NS records into a wildcard domain. It isn't -explicitly forbidden, but the protocol is ambiguous about how this should -behave and BIND 9 refuses that as well. Please describe your intention using -different tools. -

DATASRC_META_ADD adding a data source into meta data source

-This is a debug message issued during startup or reconfiguration. -Another data source is being added into the meta data source. -

DATASRC_META_ADD_CLASS_MISMATCH mismatch between classes '%1' and '%2'

-It was attempted to add a data source into a meta data source, but their -classes do not match. -

DATASRC_META_REMOVE removing data source from meta data source

-Debug information. A data source is being removed from meta data source. -

DATASRC_QUERY_ADD_NSEC adding NSEC record for '%1'

-Debug information. A NSEC record covering this zone is being added. -

DATASRC_QUERY_ADD_NSEC3 adding NSEC3 record of zone '%1'

-Debug information. A NSEC3 record for the given zone is being added to the -response message. -

DATASRC_QUERY_ADD_RRSET adding RRset '%1/%2' to message

-Debug information. An RRset is being added to the response message. -

DATASRC_QUERY_ADD_SOA adding SOA of '%1'

-Debug information. A SOA record of the given zone is being added to the -authority section of the response message. -

DATASRC_QUERY_AUTH_FAIL the underlying data source failed with %1

-The underlying data source failed to answer the authoritative query. 1 means -some error, 2 is not implemented. The data source should have logged the -specific error already. -

DATASRC_QUERY_BAD_REFERRAL bad referral to '%1'

-The domain lives in another zone. But it is not possible to generate referral -information for it. -

DATASRC_QUERY_CACHED data for %1/%2 found in hotspot cache

-Debug information. The requested data were found in the hotspot cache, so -no query is sent to the real data source. -

DATASRC_QUERY_CHECK_CACHE checking hotspot cache for '%1/%2'

-Debug information. While processing a query, lookup to the hotspot cache -is being made. -

DATASRC_QUERY_COPY_AUTH copying authoritative section into message

-Debug information. The whole referral information is being copied into the -response message. -

DATASRC_QUERY_DELEGATION looking for delegation on the path to '%1'

-Debug information. The software is trying to identify delegation points on the -way down to the given domain. -

DATASRC_QUERY_EMPTY_CNAME CNAME at '%1' is empty

-A CNAME chain was being followed and an entry was found that pointed -to a domain name that had no RRsets associated with it. As a result, -the query cannot be answered. This indicates a problem with supplied data. -

DATASRC_QUERY_EMPTY_DNAME the DNAME on '%1' is empty

-During an attempt to synthesize CNAME from this DNAME it was discovered the -DNAME is empty (it has no records). This indicates problem with supplied data. -

DATASRC_QUERY_FAIL query failed

-Some subtask of query processing failed. The reason should have been reported -already and a SERVFAIL will be returned to the querying system. -

DATASRC_QUERY_FOLLOW_CNAME following CNAME at '%1'

-Debug information. The domain is a CNAME (or a DNAME and a CNAME for it -has already been created) and the search is following this chain. -

DATASRC_QUERY_GET_MX_ADDITIONAL addition of A/AAAA for '%1' requested by MX '%2'

-Debug information. While processing a query, a MX record was met. It -references the mentioned address, so A/AAAA records for it are looked up -and put it into the additional section. -

DATASRC_QUERY_GET_NS_ADDITIONAL addition of A/AAAA for '%1' requested by NS '%2'

-Debug information. While processing a query, a NS record was met. It -references the mentioned address, so A/AAAA records for it are looked up -and put it into the additional section. -

DATASRC_QUERY_GLUE_FAIL the underlying data source failed with %1

-The underlying data source failed to answer the glue query. 1 means some error, -2 is not implemented. The data source should have logged the specific error -already. -

DATASRC_QUERY_INVALID_OP invalid query operation requested

-This indicates a programmer error. The DO_QUERY was called with unknown -operation code. -

DATASRC_QUERY_IS_AUTH auth query (%1/%2)

-Debug information. The last DO_QUERY is an auth query. -

DATASRC_QUERY_IS_GLUE glue query (%1/%2)

-Debug information. The last DO_QUERY is a query for glue addresses. -

DATASRC_QUERY_IS_NOGLUE query for non-glue addresses (%1/%2)

-Debug information. The last DO_QUERY is a query for addresses that are not -glue. -

DATASRC_QUERY_IS_REF query for referral (%1/%2)

-Debug information. The last DO_QUERY is a query for referral information. -

DATASRC_QUERY_IS_SIMPLE simple query (%1/%2)

-Debug information. The last DO_QUERY is a simple query. -

DATASRC_QUERY_MISPLACED_TASK task of this type should not be here

-This indicates a programming error. A task was found in the internal task -queue, but this kind of task wasn't designed to be inside the queue (it should -be handled right away, not queued). -

DATASRC_QUERY_MISSING_NS missing NS records for '%1'

-NS records should have been put into the authority section. However, this zone -has none. This indicates problem with provided data. -

DATASRC_QUERY_MISSING_SOA the zone '%1' has no SOA

-The answer should have been a negative one (eg. of nonexistence of something). -To do so, a SOA record should be put into the authority section, but the zone -does not have one. This indicates problem with provided data. -

DATASRC_QUERY_NOGLUE_FAIL the underlying data source failed with %1

-The underlying data source failed to answer the no-glue query. 1 means some -error, 2 is not implemented. The data source should have logged the specific -error already. -

DATASRC_QUERY_NO_CACHE_ANY_AUTH ignoring hotspot cache for ANY query (%1/%2 in %3 class)

-Debug information. The hotspot cache is ignored for authoritative ANY queries -for consistency reasons. -

DATASRC_QUERY_NO_CACHE_ANY_SIMPLE ignoring hotspot cache for ANY query (%1/%2 in %3 class)

-Debug information. The hotspot cache is ignored for ANY queries for consistency -reasons. -

DATASRC_QUERY_NO_DS_NSEC there's no DS record in the '%1' zone

-An attempt to add a NSEC record into the message failed, because the zone does -not have any DS record. This indicates problem with the provided data. -

DATASRC_QUERY_NO_DS_NSEC3 there's no DS record in the '%1' zone

-An attempt to add a NSEC3 record into the message failed, because the zone does -not have any DS record. This indicates problem with the provided data. -

DATASRC_QUERY_NO_ZONE no zone containing '%1' in class '%2'

-Lookup of domain failed because the data have no zone that contain the -domain. Maybe someone sent a query to the wrong server for some reason. -

DATASRC_QUERY_PROCESS processing query '%1/%2' in the '%3' class

-Debug information. A sure query is being processed now. -

DATASRC_QUERY_PROVE_NX_FAIL unable to prove nonexistence of '%1'

-The user wants DNSSEC and we discovered the entity doesn't exist (either -domain or the record). But there was an error getting NSEC/NSEC3 record -to prove the nonexistence. -

DATASRC_QUERY_REF_FAIL the underlying data source failed with %1

-The underlying data source failed to answer the query for referral information. -1 means some error, 2 is not implemented. The data source should have logged -the specific error already. -

DATASRC_QUERY_RRSIG unable to answer RRSIG query

-The server is unable to answer a direct query for RRSIG type, but was asked -to do so. -

DATASRC_QUERY_SIMPLE_FAIL the underlying data source failed with %1

-The underlying data source failed to answer the simple query. 1 means some -error, 2 is not implemented. The data source should have logged the specific -error already. -

DATASRC_QUERY_SYNTH_CNAME synthesizing CNAME from DNAME on '%1'

-This is a debug message. While answering a query, a DNAME was encountered. The -DNAME itself will be returned, along with a synthesized CNAME for clients that -do not understand the DNAME RR. -

DATASRC_QUERY_TASK_FAIL task failed with %1

-The query subtask failed. The reason should have been reported by the subtask -already. The code is 1 for error, 2 for not implemented. -

DATASRC_QUERY_TOO_MANY_CNAMES CNAME chain limit exceeded at '%1'

-A CNAME led to another CNAME and it led to another, and so on. After 16 -CNAMEs, the software gave up. Long CNAME chains are discouraged, and this -might possibly be a loop as well. Note that some of the CNAMEs might have -been synthesized from DNAMEs. This indicates problem with supplied data. -

DATASRC_QUERY_UNKNOWN_RESULT unknown result of subtask

-This indicates a programmer error. The answer of subtask doesn't look like -anything known. -

DATASRC_QUERY_WILDCARD looking for a wildcard covering '%1'

-Debug information. A direct match wasn't found, so a wildcard covering the -domain is being looked for now. -

DATASRC_QUERY_WILDCARD_FAIL error processing wildcard for '%1'

-During an attempt to cover the domain by a wildcard an error happened. The -exact kind was hopefully already reported. -

DATASRC_QUERY_WILDCARD_PROVE_NX_FAIL unable to prove nonexistence of '%1' (%2)

-While processing a wildcard, it wasn't possible to prove nonexistence of the -given domain or record. The code is 1 for error and 2 for not implemented. -

DATASRC_QUERY_WILDCARD_REFERRAL unable to find referral info for '%1' (%2)

-While processing a wildcard, a referral was met. But it wasn't possible to get -enough information for it. The code is 1 for error, 2 for not implemented. -

DATASRC_SQLITE_CLOSE closing SQLite database

-Debug information. The SQLite data source is closing the database file. -

DATASRC_SQLITE_CONNCLOSE Closing sqlite database

-The database file is no longer needed and is being closed. -

DATASRC_SQLITE_CONNOPEN Opening sqlite database file '%1'

-The database file is being opened so it can start providing data. -

DATASRC_SQLITE_CREATE SQLite data source created

-Debug information. An instance of SQLite data source is being created. -

DATASRC_SQLITE_DESTROY SQLite data source destroyed

-Debug information. An instance of SQLite data source is being destroyed. -

DATASRC_SQLITE_DROPCONN SQLite3Database is being deinitialized

-The object around a database connection is being destroyed. -

DATASRC_SQLITE_ENCLOSURE looking for zone containing '%1'

-Debug information. The SQLite data source is trying to identify which zone -should hold this domain. -

DATASRC_SQLITE_ENCLOSURE_NOT_FOUND no zone contains '%1'

-Debug information. The last SQLITE_ENCLOSURE query was unsuccessful; there's -no such zone in our data. -

DATASRC_SQLITE_FIND looking for RRset '%1/%2'

-Debug information. The SQLite data source is looking up a resource record -set. -

DATASRC_SQLITE_FINDADDRS looking for A/AAAA addresses for '%1'

-Debug information. The data source is looking up the addresses for given -domain name. -

DATASRC_SQLITE_FINDADDRS_BAD_CLASS class mismatch looking for addresses ('%1' and '%2')

-The SQLite data source was looking up A/AAAA addresses, but the data source -contains different class than the query was for. -

DATASRC_SQLITE_FINDEXACT looking for exact RRset '%1/%2'

-Debug information. The SQLite data source is looking up an exact resource -record. -

DATASRC_SQLITE_FINDEXACT_BAD_CLASS class mismatch looking for an RRset ('%1' and '%2')

-The SQLite data source was looking up an exact RRset, but the data source -contains different class than the query was for. -

DATASRC_SQLITE_FINDREC looking for record '%1/%2'

-Debug information. The SQLite data source is looking up records of given name -and type in the database. -

DATASRC_SQLITE_FINDREF looking for referral at '%1'

-Debug information. The SQLite data source is identifying if this domain is -a referral and where it goes. -

DATASRC_SQLITE_FINDREF_BAD_CLASS class mismatch looking for referral ('%1' and '%2')

-The SQLite data source was trying to identify if there's a referral. But -it contains different class than the query was for. -

DATASRC_SQLITE_FIND_BAD_CLASS class mismatch looking for an RRset ('%1' and '%2')

-The SQLite data source was looking up an RRset, but the data source contains -different class than the query was for. -

DATASRC_SQLITE_FIND_NSEC3 looking for NSEC3 in zone '%1' for hash '%2'

-Debug information. We're trying to look up a NSEC3 record in the SQLite data -source. -

DATASRC_SQLITE_FIND_NSEC3_NO_ZONE no such zone '%1'

-The SQLite data source was asked to provide a NSEC3 record for given zone. -But it doesn't contain that zone. -

DATASRC_SQLITE_NEWCONN SQLite3Database is being initialized

-A wrapper object to hold database connection is being initialized. -

DATASRC_SQLITE_OPEN opening SQLite database '%1'

-Debug information. The SQLite data source is loading an SQLite database in -the provided file. -

DATASRC_SQLITE_PREVIOUS looking for name previous to '%1'

-This is a debug message. The name given was not found, so the program -is searching for the next name higher up the hierarchy (e.g. if -www.example.com were queried for and not found, the software searches -for the "previous" name, example.com). -

DATASRC_SQLITE_PREVIOUS_NO_ZONE no zone containing '%1'

-The name given was not found, so the program is searching for the next -name higher up the hierarchy (e.g. if www.example.com were queried -for and not found, the software searches for the "previous" name, -example.com). However, this name is not contained in any zone in the -data source. This is an error since it indicates a problem in the earlier -processing of the query. -

DATASRC_SQLITE_SETUP setting up SQLite database

-The database for SQLite data source was found empty. It is assumed this is the -first run and it is being initialized with current schema. It'll still contain -no data, but it will be ready for use. -

DATASRC_STATIC_CLASS_NOT_CH static data source can handle CH class only

-An error message indicating that a query requesting a RR for a class other -that CH was sent to the static data source (which only handles CH queries). -

DATASRC_STATIC_CREATE creating the static datasource

-Debug information. The static data source (the one holding stuff like -version.bind) is being created. -

DATASRC_STATIC_FIND looking for '%1/%2'

-Debug information. This resource record set is being looked up in the static -data source. -

DATASRC_UNEXPECTED_QUERY_STATE unexpected query state

-This indicates a programming error. An internal task of unknown type was -generated. -

DDNS_CC_SESSION_ERROR error reading from cc channel: %1

-There was a problem reading from the command and control channel. The -most likely cause is that the msgq process is not running. -

DDNS_CC_SESSION_TIMEOUT_ERROR timeout waiting for cc response

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

DDNS_CONFIG_ERROR error found in configuration data: %1

-The ddns process encountered an error when installing the configuration at -startup time. Details of the error are included in the log message. -

DDNS_MODULECC_SESSION_ERROR error encountered by configuration/command module: %1

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

DDNS_RECEIVED_SHUTDOWN_COMMAND shutdown command received

-The ddns process received a shutdown command from the command channel -and will now shut down. -

DDNS_RUNNING ddns server is running and listening for updates

-The ddns process has successfully started and is now ready to receive commands -and updates. -

DDNS_SHUTDOWN ddns server shutting down

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

DDNS_STOPPED ddns server has stopped

-The ddns process has successfully stopped and is no longer listening for or -handling commands or updates, and will now exit. -

DDNS_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down

-There was a keyboard interrupt signal to stop the ddns process. The -process will now shut down. -

DDNS_UNCAUGHT_EXCEPTION uncaught exception of type %1: %2

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

LIBXFRIN_DIFFERENT_TTL multiple data with different TTLs (%1, %2) on %3/%4/%5. Adjusting %2 -> %1.

-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 latter one gets overwritten to the earlier one in the sequence. -

LIBXFRIN_NO_JOURNAL disabled journaling for updates to %1 on %2

-An attempt was made to create a Diff object with journaling enabled, but -the underlying data source didn't support journaling (while still allowing -updates) and so the created object has it disabled. At a higher level this -means that the updates will be applied to the zone but subsequent IXFR requests -will result in a full zone transfer (i.e., an AXFR-style IXFR). Unless the -overhead of the full transfer is an issue this message can be ignored; -otherwise you may want to check why the journaling wasn't allowed on the -data source and either fix the issue or use a different type of data source. -

LOGIMPL_ABOVE_MAX_DEBUG debug level of %1 is too high and will be set to the maximum of %2

-A message from the interface to the underlying logger implementation reporting -that the debug level (as set by an internally-created string DEBUGn, where n -is an integer, e.g. DEBUG22) is above the maximum allowed value and has -been reduced to that value. The appearance of this message may indicate -a programming error - please submit a bug report. -

LOGIMPL_BAD_DEBUG_STRING debug string '%1' has invalid format

-A message from the interface to the underlying logger implementation -reporting that an internally-created string used to set the debug level -is not of the correct format (it should be of the form DEBUGn, where n -is an integer, e.g. DEBUG22). The appearance of this message indicates -a programming error - please submit a bug report. -

LOGIMPL_BELOW_MIN_DEBUG debug level of %1 is too low and will be set to the minimum of %2

-A message from the interface to the underlying logger implementation reporting -that the debug level (as set by an internally-created string DEBUGn, where n -is an integer, e.g. DEBUG22) is below the minimum allowed value and has -been increased to that value. The appearance of this message may indicate -a programming error - please submit a bug report. -

LOG_BAD_DESTINATION unrecognized log destination: %1

-A logger destination value was given that was not recognized. The -destination should be one of "console", "file", or "syslog". -

LOG_BAD_SEVERITY unrecognized log severity: %1

-A logger severity value was given that was not recognized. The severity -should be one of "DEBUG", "INFO", "WARN", "ERROR", "FATAL" or "NONE". -

LOG_BAD_STREAM bad log console output stream: %1

-Logging has been configured so that output is written to the terminal -(console) but the stream on which it is to be written is not recognised. -Allowed values are "stdout" and "stderr". -

LOG_DUPLICATE_MESSAGE_ID duplicate message ID (%1) in compiled code

-During start-up, BIND 10 detected that the given message identification -had been defined multiple times in the BIND 10 code. This indicates a -programming error; please submit a bug report. -

LOG_DUPLICATE_NAMESPACE line %1: duplicate $NAMESPACE directive found

-When reading a message file, more than one $NAMESPACE directive was found. -(This directive is used to set a C++ namespace when generating header -files during software development.) Such a condition is regarded as an -error and the read will be abandoned. -

LOG_INPUT_OPEN_FAIL unable to open message file %1 for input: %2

-The program was not able to open the specified input message file for -the reason given. -

LOG_INVALID_MESSAGE_ID line %1: invalid message identification '%2'

-An invalid message identification (ID) has been found during the read of -a message file. Message IDs should comprise only alphanumeric characters -and the underscore, and should not start with a digit. -

LOG_NAMESPACE_EXTRA_ARGS line %1: $NAMESPACE directive has too many arguments

-The $NAMESPACE directive in a message file takes a single argument, a -namespace in which all the generated symbol names are placed. This error -is generated when the compiler finds a $NAMESPACE directive with more -than one argument. -

LOG_NAMESPACE_INVALID_ARG line %1: $NAMESPACE directive has an invalid argument ('%2')

-The $NAMESPACE argument in a message file should be a valid C++ namespace. -This message is output if the simple check on the syntax of the string -carried out by the reader fails. -

LOG_NAMESPACE_NO_ARGS line %1: no arguments were given to the $NAMESPACE directive

-The $NAMESPACE directive in a message file takes a single argument, -a C++ namespace in which all the generated symbol names are placed. -This error is generated when the compiler finds a $NAMESPACE directive -with no arguments. -

LOG_NO_MESSAGE_ID line %1: message definition line found without a message ID

-Within a message file, message are defined by lines starting with a "%". -The rest of the line should comprise the message ID and text describing -the message. This error indicates the message compiler found a line in -the message file comprising just the "%" and nothing else. -

LOG_NO_MESSAGE_TEXT line %1: line found containing a message ID ('%2') and no text

-Within a message file, message are defined by lines starting with a "%". -The rest of the line should comprise the message ID and text describing -the message. This error indicates the message compiler found a line -in the message file comprising just the "%" and message identification, -but no text. -

LOG_NO_SUCH_MESSAGE could not replace message text for '%1': no such message

-During start-up a local message file was read. A line with the listed -message identification was found in the file, but the identification is -not one contained in the compiled-in message dictionary. This message -may appear a number of times in the file, once for every such unknown -message identification. -

-There may be several reasons why this message may appear: -

-- The message ID has been mis-spelled in the local message file. -

-- The program outputting the message may not use that particular message -(e.g. it originates in a module not used by the program.) -

-- The local file was written for an earlier version of the BIND 10 software -and the later version no longer generates that message. -

-Whatever the reason, there is no impact on the operation of BIND 10. -

LOG_OPEN_OUTPUT_FAIL unable to open %1 for output: %2

-Originating within the logging code, the program was not able to open -the specified output file for the reason given. -

LOG_PREFIX_EXTRA_ARGS line %1: $PREFIX directive has too many arguments

-Within a message file, the $PREFIX directive takes a single argument, -a prefix to be added to the symbol names when a C++ file is created. -This error is generated when the compiler finds a $PREFIX directive with -more than one argument. -

-Note: the $PREFIX directive is deprecated and will be removed in a future -version of BIND 10. -

LOG_PREFIX_INVALID_ARG line %1: $PREFIX directive has an invalid argument ('%2')

-Within a message file, the $PREFIX directive takes a single argument, -a prefix to be added to the symbol names when a C++ file is created. -As such, it must adhere to restrictions on C++ symbol names (e.g. may -only contain alphanumeric characters or underscores, and may nor start -with a digit). A $PREFIX directive was found with an argument (given -in the message) that violates those restrictions. -

-Note: the $PREFIX directive is deprecated and will be removed in a future -version of BIND 10. -

LOG_READING_LOCAL_FILE reading local message file %1

-This is an informational message output by BIND 10 when it starts to read -a local message file. (A local message file may replace the text of -one of more messages; the ID of the message will not be changed though.) -

LOG_READ_ERROR error reading from message file %1: %2

-The specified error was encountered reading from the named message file. -

LOG_UNRECOGNISED_DIRECTIVE line %1: unrecognised directive '%2'

-Within a message file, a line starting with a dollar symbol was found -(indicating the presence of a directive) but the first word on the line -(shown in the message) was not recognised. -

LOG_WRITE_ERROR error writing to %1: %2

-The specified error was encountered by the message compiler when writing -to the named output file. -

NOTIFY_OUT_DATASRC_ACCESS_FAILURE failed to get access to data source: %1

-notify_out failed to get access to one of configured data sources. -Detailed error is shown in the log message. This can be either a -configuration error or installation setup failure. -

NOTIFY_OUT_DATASRC_ZONE_NOT_FOUND Zone %1 is not found

-notify_out attempted to get slave information of a zone but the zone -isn't found in the expected data source. This shouldn't happen, -because notify_out first identifies a list of available zones before -this process. So this means some critical inconsistency in the data -source or software bug. -

NOTIFY_OUT_INVALID_ADDRESS invalid address %1#%2: %3

-The notify_out library tried to send a notify message to the given -address, but it appears to be an invalid address. The configuration -for secondary nameservers might contain a typographic error, or a -different BIND 10 module has forgotten to validate its data before -sending this module a notify command. As such, this should normally -not happen, and points to an oversight in a different module. -

NOTIFY_OUT_REPLY_BAD_OPCODE bad opcode in notify reply from %1#%2: %3

-The notify_out library sent a notify message to the nameserver at -the given address, but the response did not have the opcode set to -NOTIFY. The opcode in the response is printed. Since there was a -response, no more notifies will be sent to this server for this -notification event. -

NOTIFY_OUT_REPLY_BAD_QID bad QID in notify reply from %1#%2: got %3, should be %4

-The notify_out library sent a notify message to the nameserver at -the given address, but the query id in the response does not match -the one we sent. Since there was a response, no more notifies will -be sent to this server for this notification event. -

NOTIFY_OUT_REPLY_BAD_QUERY_NAME bad query name in notify reply from %1#%2: got %3, should be %4

-The notify_out library sent a notify message to the nameserver at -the given address, but the query name in the response does not match -the one we sent. Since there was a response, no more notifies will -be sent to this server for this notification event. -

NOTIFY_OUT_REPLY_QR_NOT_SET QR flags set to 0 in reply to notify from %1#%2

-The notify_out library sent a notify message to the namesever at the -given address, but the reply did not have the QR bit set to one. -Since there was a response, no more notifies will be sent to this -server for this notification event. -

NOTIFY_OUT_REPLY_UNCAUGHT_EXCEPTION uncaught exception: %1

-There was an uncaught exception in the handling of a notify reply -message, either in the message parser, or while trying to extract data -from the parsed message. The error is printed, and notify_out will -treat the response as a bad message, but this does point to a -programming error, since all exceptions should have been caught -explicitly. Please file a bug report. Since there was a response, -no more notifies will be sent to this server for this notification -event. -

NOTIFY_OUT_RETRY_EXCEEDED notify to %1#%2: number of retries (%3) exceeded

-The maximum number of retries for the notify target has been exceeded. -Either the address of the secondary nameserver is wrong, or it is not -responding. -

NOTIFY_OUT_SENDING_NOTIFY sending notify to %1#%2

-A notify message is sent to the secondary nameserver at the given -address. -

NOTIFY_OUT_SOCKET_ERROR socket error sending notify to %1#%2: %3

-There was a network error while trying to send a notify message to -the given address. The address might be unreachable. The socket -error is printed and should provide more information. -

NOTIFY_OUT_SOCKET_RECV_ERROR socket error reading notify reply from %1#%2: %3

-There was a network error while trying to read a notify reply -message from the given address. The socket error is printed and should -provide more information. -

NOTIFY_OUT_TIMEOUT retry notify to %1#%2

-The notify message to the given address (noted as address#port) has -timed out, and the message will be resent until the max retry limit -is reached. -

NOTIFY_OUT_ZONE_BAD_SOA Zone %1 is invalid in terms of SOA

-This is a warning issued when the notify_out module finds a zone that -doesn't have an SOA RR or has multiple SOA RRs. Notify message won't -be sent to such a zone. -

NOTIFY_OUT_ZONE_NO_NS Zone %1 doesn't have NS RR

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

NSAS_EMPTY_RESPONSE response to query for %1 returned an empty answer section

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

NSAS_ERROR_RESPONSE error response of %1 returned in query for %2

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

NSAS_FIND_NS_ADDRESS asking resolver to obtain A and AAAA records for %1

-A debug message issued when the NSAS (nameserver address store - part -of the resolver) is making a callback into the resolver to retrieve the -address records for the specified nameserver. -

NSAS_FOUND_ADDRESS found address %1 for %2

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

NSAS_LOOKUP_CANCEL lookup for zone %1 has been canceled

-A debug message issued when an NSAS (nameserver address store - part of -the resolver) lookup for a zone has been canceled. -

NSAS_NS_LOOKUP_FAIL failed to lookup any %1 for %2

-A debug message issued when the NSAS (nameserver address store - part of -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. -

NSAS_NULL_RESPONSE got null message in success callback for query for %1

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

-This message indicates an internal error in the NSAS. Please raise a -bug report. -

NSAS_SEARCH_ZONE_NS searching NSAS for nameservers for zone %1

-A debug message output when a call is made to the NSAS (nameserver -address store - part of the resolver) to obtain the nameservers for -the specified zone. -

NSAS_UPDATE_RTT update RTT for %1: was %2 ms, is now %3 ms

-A NSAS (nameserver address store - part of the resolver) debug message -reporting the update of a round-trip time (RTT) for a query made to the -specified nameserver. The RTT has been updated using the value given -and the new RTT is displayed. (The RTT is subject to a calculation that -damps out sudden changes. As a result, the new RTT used by the NSAS in -future decisions of which nameserver to use is not necessarily equal to -the RTT reported.) -

NSAS_WRONG_ANSWER queried for %1 RR of type/class %2/%3, received response %4/%5

-A NSAS (nameserver address store - part of the resolver) made a query for -a resource record of a particular type and class, but instead received -an answer with a different given type and class. -

-This message indicates an internal error in the NSAS. Please raise a -bug report. -

RESLIB_ANSWER answer received in response to query for <%1>

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

RESLIB_CNAME CNAME received in response to query for <%1>

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

RESLIB_DEEPEST did not find <%1> in cache, deepest delegation found is %2

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

RESLIB_EMPTY_RESPONSE empty response received to query for <%1>

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

RESLIB_ERROR_RESPONSE unspecified error received in response to query for <%1>

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

RESLIB_EXTRADATA_RESPONSE extra data in response to query for <%1>

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

RESLIB_FOLLOW_CNAME following CNAME chain to <%1>

-A debug message, a CNAME response was received and another query is -being issued for the <name, class, type> tuple. -

RESLIB_INVALID_NAMECLASS_RESPONSE invalid name or class in response to query for <%1>

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

RESLIB_INVALID_QNAME_RESPONSE invalid name or class in response to query for <%1>

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

RESLIB_INVALID_TYPE_RESPONSE invalid name or class in response to query for <%1>

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

RESLIB_LONG_CHAIN CNAME received in response to query for <%1>: CNAME chain length exceeded

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

RESLIB_MULTIPLE_CLASS_RESPONSE response to query for <%1> contained multiple RRsets with different classes

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

RESLIB_NOTSINGLE_RESPONSE response to query for <%1> was not a response

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

RESLIB_NOT_ONE_QNAME_RESPONSE not one question in response to query for <%1>

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

RESLIB_NOT_RESPONSE response to query for <%1> was not a response

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

RESLIB_NO_NS_RRSET no NS RRSet in referral response received to query for <%1>

-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 -not contain any NS RRsets. This may indicate a programming error in the -response classification code. -

RESLIB_NSAS_LOOKUP looking up nameserver for zone %1 in the NSAS

-A debug message, the RunningQuery object is querying the NSAS for the -nameservers for the specified zone. -

RESLIB_NXDOM_NXRR NXDOMAIN/NXRRSET received in response to query for <%1>

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

RESLIB_OPCODE_RESPONSE response to query for <%1> did not have query opcode

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

RESLIB_PROTOCOL protocol error in answer for %1: %3

-A debug message indicating that a protocol error was received. As there -are no retries left, an error will be reported. -

RESLIB_PROTOCOL_RETRY protocol error in answer for %1: %2 (retries left: %3)

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

RESLIB_RCODE_ERROR response to query for <%1> returns RCODE of %2

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

RESLIB_RECQ_CACHE_FIND found <%1> in the cache (resolve() instance %2)

-This is a debug message and indicates that a RecursiveQuery object found the -the specified <name, class, type> tuple in the cache. The instance number -at the end of the message indicates which of the two resolve() methods has -been called. -

RESLIB_RECQ_CACHE_NO_FIND did not find <%1> in the cache, starting RunningQuery (resolve() instance %2)

-This is a debug message and indicates that the look in the cache made by the -RecursiveQuery::resolve() method did not find an answer, so a new RunningQuery -object has been created to resolve the question. The instance number at -the end of the message indicates which of the two resolve() methods has -been called. -

RESLIB_REFERRAL referral received in response to query for <%1>

-A debug message recording that a referral 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. -

RESLIB_REFER_ZONE referred to zone %1

-A debug message indicating that the last referral message was to the specified -zone. -

RESLIB_RESOLVE asked to resolve <%1> (resolve() instance %2)

-A debug message, the RecursiveQuery::resolve method has been called to resolve -the specified <name, class, type> tuple. The first action will be to lookup -the specified tuple in the cache. The instance number at the end of the -message indicates which of the two resolve() methods has been called. -

RESLIB_RRSET_FOUND found single RRset in the cache when querying for <%1> (resolve() instance %2)

-A debug message, indicating that when RecursiveQuery::resolve queried the -cache, a single RRset was found which was put in the answer. The instance -number at the end of the message indicates which of the two resolve() -methods has been called. -

RESLIB_RTT round-trip time of last query calculated as %1 ms

-A debug message giving the round-trip time of the last query and response. -

RESLIB_RUNQ_CACHE_FIND found <%1> in the cache

-This is a debug message and indicates that a RunningQuery object found -the specified <name, class, type> tuple in the cache. -

RESLIB_RUNQ_CACHE_LOOKUP looking up up <%1> in the cache

-This is a debug message and indicates that a RunningQuery object has made -a call to its doLookup() method to look up the specified <name, class, type> -tuple, the first action of which will be to examine the cache. -

RESLIB_RUNQ_FAIL failure callback - nameservers are unreachable

-A debug message indicating that a RunningQuery's failure callback has been -called because all nameservers for the zone in question are unreachable. -

RESLIB_RUNQ_SUCCESS success callback - sending query to %1

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

RESLIB_TCP_TRUNCATED TCP response to query for %1 was truncated

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

RESLIB_TEST_SERVER setting test server to %1(%2)

-This is a warning message only generated in unit tests. It indicates -that all upstream queries from the resolver are being routed to the -specified server, regardless of the address of the nameserver to which -the query would normally be routed. If seen during normal operation, -please submit a bug report. -

RESLIB_TEST_UPSTREAM sending upstream query for <%1> to test server at %2

-This is a debug message and should only be seen in unit tests. A query for -the specified <name, class, type> tuple is being sent to a test nameserver -whose address is given in the message. -

RESLIB_TIMEOUT query <%1> to %2 timed out

-A debug message indicating that the specified upstream query has timed out and -there are no retries left. -

RESLIB_TIMEOUT_RETRY query <%1> to %2 timed out, re-trying (retries left: %3)

-A debug message indicating that the specified query has timed out 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. -

RESLIB_TRUNCATED response to query for <%1> was truncated, re-querying over TCP

-A debug message, this indicates that the response to the specified query was -truncated and that the resolver will be re-querying over TCP. There are -various reasons why responses may be truncated, so this message is normal and -gives no cause for concern. -

RESLIB_UPSTREAM sending upstream query for <%1> to %2

-A debug message indicating that a query for the specified <name, class, type> -tuple is being sent to a nameserver whose address is given in the message. -

RESOLVER_AXFR_TCP AXFR request received over TCP

-This is a debug message output when the resolver received a request for -an AXFR (full transfer of a zone) over TCP. Only authoritative servers -are able to handle AXFR requests, so the resolver will return an error -message to the sender with the RCODE set to NOTIMP. -

RESOLVER_AXFR_UDP AXFR request received over UDP

-This is a debug message output when the resolver received a request for -an AXFR (full transfer of a zone) over UDP. Only authoritative servers -are able to handle AXFR requests (and in any case, an AXFR request should -be sent over TCP), so the resolver will return an error message to the -sender with the RCODE set to NOTIMP. -

RESOLVER_CLIENT_TIME_SMALL client timeout of %1 is too small

-During the update of the resolver's configuration parameters, the value -of the client timeout was found to be too small. The configuration -update was abandoned and the parameters were not changed. -

RESOLVER_CONFIG_CHANNEL configuration channel created

-This is a debug message output when the resolver has successfully -established a connection to the configuration channel. -

RESOLVER_CONFIG_ERROR error in configuration: %1

-An error was detected in a configuration update received by the -resolver. This may be in the format of the configuration message (in -which case this is a programming error) or it may be in the data supplied -(in which case it is a user error). The reason for the error, included -in the message, will give more details. The configuration update is -not applied and the resolver parameters were not changed. -

RESOLVER_CONFIG_LOADED configuration loaded

-This is a debug message output when the resolver configuration has been -successfully loaded. -

RESOLVER_CONFIG_UPDATED configuration updated: %1

-This is a debug message output when the resolver configuration is being -updated with the specified information. -

RESOLVER_CREATED main resolver object created

-This is a debug message indicating that the main resolver object has -been created. -

RESOLVER_DNS_MESSAGE_RECEIVED DNS message received: %1

-This is a debug message from the resolver listing the contents of a -received DNS message. -

RESOLVER_DNS_MESSAGE_SENT DNS message of %1 bytes sent: %2

-This is a debug message containing details of the response returned by -the resolver to the querying system. -

RESOLVER_FAILED resolver failed, reason: %1

-This is an error message output when an unhandled exception is caught -by the resolver. After this, the resolver will shut itself down. -Please submit a bug report. -

RESOLVER_FORWARD_ADDRESS setting forward address %1(%2)

-If the resolver is running in forward mode, this message will appear -during startup to list the forward address. If multiple addresses are -specified, it will appear once for each address. -

RESOLVER_FORWARD_QUERY processing forward query

-This is a debug message indicating that a query received by the resolver -has passed a set of checks (message is well-formed, it is allowed by the -ACL, it is a supported opcode, etc.) and is being forwarded to upstream -servers. -

RESOLVER_HEADER_ERROR message received, exception when processing header: %1

-This is a debug message from the resolver noting that an exception -occurred during the processing of a received packet. The packet has -been dropped. -

RESOLVER_IXFR IXFR request received

-This is a debug message indicating that the resolver received a request -for an IXFR (incremental transfer of a zone). Only authoritative servers -are able to handle IXFR requests, so the resolver will return an error -message to the sender with the RCODE set to NOTIMP. -

RESOLVER_LOOKUP_TIME_SMALL lookup timeout of %1 is too small

-During the update of the resolver's configuration parameters, the value -of the lookup timeout was found to be too small. The configuration -update will not be applied. -

RESOLVER_MESSAGE_ERROR error parsing received message: %1 - returning %2

-This is a debug message noting that parsing of the body of a received -message by the resolver failed due to some error (although the parsing of -the header succeeded). The message parameters give a textual description -of the problem and the RCODE returned. -

RESOLVER_NEGATIVE_RETRIES negative number of retries (%1) specified in the configuration

-This error is issued when a resolver configuration update has specified -a negative retry count: only zero or positive values are valid. The -configuration update was abandoned and the parameters were not changed. -

RESOLVER_NON_IN_PACKET non-IN class request received, returning REFUSED message

-This debug message is issued when resolver has received a DNS packet that -was not IN (Internet) class. The resolver cannot handle such packets, -so is returning a REFUSED response to the sender. -

RESOLVER_NORMAL_QUERY processing normal query

-This is a debug message indicating that the query received by the resolver -has passed a set of checks (message is well-formed, it is allowed by the -ACL, it is a supported opcode, etc.) and is being processed by the resolver. -

RESOLVER_NOTIFY_RECEIVED NOTIFY arrived but server is not authoritative

-The resolver has received a NOTIFY message. As the server is not -authoritative it cannot process it, so it returns an error message to -the sender with the RCODE set to NOTAUTH. -

RESOLVER_NOT_ONE_QUESTION query contained %1 questions, exactly one question was expected

-This debug message indicates that the resolver received a query that -contained the number of entries in the question section detailed in -the message. This is a malformed message, as a DNS query must contain -only one question. The resolver will return a message to the sender -with the RCODE set to FORMERR. -

RESOLVER_NO_ROOT_ADDRESS no root addresses available

-A warning message issued during resolver startup, this indicates that -no root addresses have been set. This may be because the resolver will -get them from a priming query. -

RESOLVER_PARSE_ERROR error parsing received message: %1 - returning %2

-This is a debug message noting that the resolver received a message and -the parsing of the body of the message failed due to some non-protocol -related reason (although the parsing of the header succeeded). -The message parameters give a textual description of the problem and -the RCODE returned. -

RESOLVER_PRINT_COMMAND print message command, arguments are: %1

-This debug message is logged when a "print_message" command is received -by the resolver over the command channel. -

RESOLVER_PROTOCOL_ERROR protocol error parsing received message: %1 - returning %2

-This is a debug message noting that the resolver received a message and -the parsing of the body of the message failed due to some protocol error -(although the parsing of the header succeeded). The message parameters -give a textual description of the problem and the RCODE returned. -

RESOLVER_QUERY_ACCEPTED query accepted: '%1/%2/%3' from %4

-This debug message is produced by the resolver when an incoming query -is accepted in terms of the query ACL. The log message shows the query -in the form of <query name>/<query type>/<query class>, and the client -that sends the query in the form of <Source IP address>#<source port>. -

RESOLVER_QUERY_DROPPED query dropped: '%1/%2/%3' from %4

-This is an informational message that indicates an incoming query has -been dropped by the resolver because of the query ACL. Unlike the -RESOLVER_QUERY_REJECTED case, the server does not return any response. -The log message shows the query in the form of <query name>/<query -type>/<query class>, and the client that sends the query in the form of -<Source IP address>#<source port>. -

RESOLVER_QUERY_REJECTED query rejected: '%1/%2/%3' from %4

-This is an informational message that indicates an incoming query has -been rejected by the resolver because of the query ACL. This results -in a response with an RCODE of REFUSED. The log message shows the query -in the form of <query name>/<query type>/<query class>, and the client -that sends the query in the form of <Source IP address>#<source port>. -

RESOLVER_QUERY_SETUP query setup

-This is a debug message noting that the resolver is creating a -RecursiveQuery object. -

RESOLVER_QUERY_SHUTDOWN query shutdown

-This is a debug message noting that the resolver is destroying a -RecursiveQuery object. -

RESOLVER_QUERY_TIME_SMALL query timeout of %1 is too small

-During the update of the resolver's configuration parameters, the value -of the query timeout was found to be too small. The configuration -parameters were not changed. -

RESOLVER_RECEIVED_MESSAGE resolver has received a DNS message

-This is a debug message indicating that the resolver has received a -DNS message. Depending on the debug settings, subsequent log output -will indicate the nature of the message. -

RESOLVER_RECURSIVE running in recursive mode

-This is an informational message that appears at startup noting that -the resolver is running in recursive mode. -

RESOLVER_SERVICE_CREATED service object created

-This debug message is output when resolver creates the main service object -(which handles the received queries). -

RESOLVER_SET_PARAMS query timeout: %1, client timeout: %2, lookup timeout: %3, retry count: %4

-This debug message lists the parameters being set for the resolver. These are: -query timeout: the timeout (in ms) used for queries originated by the resolver -to upstream servers. Client timeout: the interval to resolve a query by -a client: after this time, the resolver sends back a SERVFAIL to the client -whilst continuing to resolve the query. Lookup timeout: the time at which the -resolver gives up trying to resolve a query. Retry count: the number of times -the resolver will retry a query to an upstream server if it gets a timeout. -

-The client and lookup timeouts require a bit more explanation. The -resolution of the client query might require a large number of queries to -upstream nameservers. Even if none of these queries timeout, the total time -taken to perform all the queries may exceed the client timeout. When this -happens, a SERVFAIL is returned to the client, but the resolver continues -with the resolution process; data received is added to the cache. However, -there comes a time - the lookup timeout - when even the resolver gives up. -At this point it will wait for pending upstream queries to complete or -timeout and drop the query. -

RESOLVER_SET_QUERY_ACL query ACL is configured

-This debug message is generated when a new query ACL is configured for -the resolver. -

RESOLVER_SET_ROOT_ADDRESS setting root address %1(%2)

-This message gives the address of one of the root servers used by the -resolver. It is output during startup and may appear multiple times, -once for each root server address. -

RESOLVER_SHUTDOWN resolver shutdown complete

-This informational message is output when the resolver has shut down. -

RESOLVER_STARTED resolver started

-This informational message is output by the resolver when all initialization -has been completed and it is entering its main loop. -

RESOLVER_STARTING starting resolver with command line '%1'

-An informational message, this is output when the resolver starts up. -

RESOLVER_UNEXPECTED_RESPONSE received unexpected response, ignoring

-This is a debug message noting that the resolver received a DNS response -packet on the port on which is it listening for queries. The packet -has been ignored. -

RESOLVER_UNSUPPORTED_OPCODE opcode %1 not supported by the resolver

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

SOCKETREQUESTOR_CREATED Socket requestor created

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

SOCKETREQUESTOR_DESTROYED Socket requestor destoryed

-Debug message. The socket requestor created at SOCKETREQUESTOR_CREATED -has been destroyed. This event is generally unexpected other than in -test cases. -

SOCKETREQUESTOR_GETSOCKET Received a %1 socket for [%2]:%3, FD=%4, token=%5, path=%6

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

SOCKETREQUESTOR_RELEASESOCKET Released a socket of token %1

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

SRVCOMM_ADDRESSES_NOT_LIST the address and port specification is not a list in %1

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

SRVCOMM_ADDRESS_FAIL failed to listen on addresses (%1)

-The server failed to bind to one of the address/port pair it should according -to configuration, for reason listed in the message (usually because that pair -is already used by other service or missing privileges). The server will try -to recover and bind the address/port pairs it was listening to before (if any). -

SRVCOMM_ADDRESS_MISSING address specification is missing "address" or "port" element in %1

-This points to an error in configuration. An address specification in the -configuration is missing either an address or port and so cannot be used. The -specification causing the error is given in the message. -

SRVCOMM_ADDRESS_TYPE address specification type is invalid in %1

-This points to an error in configuration. An address specification in the -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). -

SRVCOMM_ADDRESS_UNRECOVERABLE failed to recover original addresses also (%1)

-The recovery of old addresses after SRVCOMM_ADDRESS_FAIL also failed for -the reason listed. -

-The condition indicates problems with the server and/or the system on -which it is running. The server will continue running to allow -reconfiguration, but will not be listening on any address or port until -an administrator does so. -

SRVCOMM_ADDRESS_VALUE address to set: %1#%2

-Debug message. This lists one address and port value of the set of -addresses we are going to listen on (eg. there will be one log message -per pair). This appears only after SRVCOMM_SET_LISTEN, but might -be hidden, as it has higher debug level. -

SRVCOMM_KEYS_DEINIT deinitializing TSIG keyring

-Debug message indicating that the server is deinitializing the TSIG keyring. -

SRVCOMM_KEYS_INIT initializing TSIG keyring

-Debug message indicating that the server is initializing the global TSIG -keyring. This should be seen only at server start. -

SRVCOMM_KEYS_UPDATE updating TSIG keyring

-Debug message indicating new keyring is being loaded from configuration (either -on startup or as a result of configuration update). -

SRVCOMM_PORT_RANGE port out of valid range (%1 in %2)

-This points to an error in configuration. The port in an address -specification is outside the valid range of 0 to 65535. -

SRVCOMM_SET_LISTEN setting addresses to listen to

-Debug message, noting that the server is about to start listening on a -different set of IP addresses and ports than before. -

STATHTTPD_BAD_OPTION_VALUE bad command line argument: %1

-The stats-httpd module was called with a bad command-line argument -and will not start. -

STATHTTPD_CC_SESSION_ERROR error connecting to message bus: %1

-The stats-httpd module was unable to connect to the BIND 10 command -and control bus. A likely problem is that the message bus daemon -(b10-msgq) is not running. The stats-httpd module will now shut down. -

STATHTTPD_CLOSING closing %1#%2

-The stats-httpd daemon will stop listening for requests on the given -address and port number. -

STATHTTPD_CLOSING_CC_SESSION stopping cc session

-Debug message indicating that the stats-httpd module is disconnecting -from the command and control bus. -

STATHTTPD_HANDLE_CONFIG reading configuration: %1

-The stats-httpd daemon has received new configuration data and will now -process it. The (changed) data is printed. -

STATHTTPD_RECEIVED_SHUTDOWN_COMMAND shutdown command received

-A shutdown command was sent to the stats-httpd module, and it will -now shut down. -

STATHTTPD_RECEIVED_STATUS_COMMAND received command to return status

-A status command was sent to the stats-httpd module, and it will -respond with 'Stats Httpd is up.' and its PID. -

STATHTTPD_RECEIVED_UNKNOWN_COMMAND received unknown command: %1

-An unknown command has been sent to the stats-httpd module. The -stats-httpd module will respond with an error, and the command will -be ignored. -

STATHTTPD_SERVER_DATAERROR HTTP server data error: %1

-An internal error occurred while handling an HTTP request. An HTTP 404 -response will be sent back, and the specific error is printed. This -is an error condition that likely points the specified data -corresponding to the requested URI is incorrect. -

STATHTTPD_SERVER_ERROR HTTP server error: %1

-An internal error occurred while handling an HTTP request. An HTTP 500 -response will be sent back, and the specific error is printed. This -is an error condition that likely points to a module that is not -responding correctly to statistic requests. -

STATHTTPD_SERVER_INIT_ERROR HTTP server initialization error: %1

-There was a problem initializing the HTTP server in the stats-httpd -module upon receiving its configuration data. The most likely cause -is a port binding problem or a bad configuration value. The specific -error is printed in the message. The new configuration is ignored, -and an error is sent back. -

STATHTTPD_SHUTDOWN shutting down

-The stats-httpd daemon is shutting down. -

STATHTTPD_STARTED listening on %1#%2

-The stats-httpd daemon will now start listening for requests on the -given address and port number. -

STATHTTPD_STARTING_CC_SESSION starting cc session

-Debug message indicating that the stats-httpd module is connecting to -the command and control bus. -

STATHTTPD_START_SERVER_INIT_ERROR HTTP server initialization error: %1

-There was a problem initializing the HTTP server in the stats-httpd -module upon startup. The most likely cause is that it was not able -to bind to the listening port. The specific error is printed, and the -module will shut down. -

STATHTTPD_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down

-There was a keyboard interrupt signal to stop the stats-httpd -daemon. The daemon will now shut down. -

STATHTTPD_UNKNOWN_CONFIG_ITEM unknown configuration item: %1

-The stats-httpd daemon received a configuration update from the -configuration manager. However, one of the items in the -configuration is unknown. The new configuration is ignored, and an -error is sent back. As possible cause is that there was an upgrade -problem, and the stats-httpd version is out of sync with the rest of -the system. -

STATS_BAD_OPTION_VALUE bad command line argument: %1

-The stats module was called with a bad command-line argument and will -not start. -

STATS_CC_SESSION_ERROR error connecting to message bus: %1

-The stats module was unable to connect to the BIND 10 command and -control bus. A likely problem is that the message bus daemon -(b10-msgq) is not running. The stats module will now shut down. -

STATS_RECEIVED_NEW_CONFIG received new configuration: %1

-This debug message is printed when the stats module has received a -configuration update from the configuration manager. -

STATS_RECEIVED_SHOWSCHEMA_ALL_COMMAND received command to show all statistics schema

-The stats module received a command to show all statistics schemas of all modules. -

STATS_RECEIVED_SHOWSCHEMA_NAME_COMMAND received command to show statistics schema for %1

-The stats module received a command to show the specified statistics schema of the specified module. -

STATS_RECEIVED_SHOW_ALL_COMMAND received command to show all statistics

-The stats module received a command to show all statistics that it has -collected. -

STATS_RECEIVED_SHOW_NAME_COMMAND received command to show statistics for %1

-The stats module received a command to show the statistics that it has -collected for the given item. -

STATS_RECEIVED_SHUTDOWN_COMMAND shutdown command received

-A shutdown command was sent to the stats module and it will now shut down. -

STATS_RECEIVED_STATUS_COMMAND received command to return status

-A status command was sent to the stats module. It will return a -response indicating that it is running normally. -

STATS_RECEIVED_UNKNOWN_COMMAND received unknown command: %1

-An unknown command has been sent to the stats module. The stats module -will respond with an error and the command will be ignored. -

STATS_SEND_REQUEST_BOSS requesting boss to send statistics

-This debug message is printed when a request is sent to the boss module -to send its data to the stats module. -

STATS_STARTING starting

-The stats module will be now starting. -

STATS_START_ERROR stats module error: %1

-An internal error occurred while starting the stats module. The stats -module will be now shutting down. -

STATS_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down

-There was a keyboard interrupt signal to stop the stats module. The -daemon will now shut down. -

STATS_UNKNOWN_COMMAND_IN_SPEC unknown command in specification file: %1

-The specification file for the stats module contains a command that -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. -

XFRIN_AXFR_INCONSISTENT_SOA AXFR SOAs are inconsistent for %1: %2 expected, %3 received

-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 -"same" (not only for the serial), but it is still not clear what the -receiver should do if this condition does not hold. There was a discussion -about this at the IETF dnsext wg: -http://www.ietf.org/mail-archive/web/dnsext/current/msg07908.html -and the general feeling seems that it would be better to reject the -transfer if a mismatch is detected. On the other hand, also as noted -in that email thread, neither BIND 9 nor NSD performs any comparison -on the SOAs. For now, we only check the serials (ignoring other fields) -and only leave a warning log message when a mismatch is found. If it -turns out to happen with a real world primary server implementation -and that server actually feeds broken data (e.g. mixed versions of -zone), we can consider a stricter action. -

XFRIN_BAD_MASTER_ADDR_FORMAT bad format for master address: %1

-The given master address is not a valid IP address. -

XFRIN_BAD_MASTER_PORT_FORMAT bad format for master port: %1

-The master port as read from the configuration is not a valid port number. -

XFRIN_BAD_TSIG_KEY_STRING bad TSIG key string: %1

-The TSIG key string as read from the configuration does not represent -a valid TSIG key. -

XFRIN_BAD_ZONE_CLASS Invalid zone class: %1

-The zone class as read from the configuration is not a valid DNS class. -

XFRIN_CC_SESSION_ERROR error reading from cc channel: %1

-There was a problem reading from the command and control channel. The -most likely cause is that xfrin the msgq daemon is not running. -

XFRIN_COMMAND_ERROR error while executing command '%1': %2

-There was an error while the given command was being processed. The -error is given in the log message. -

XFRIN_CONNECT_MASTER error connecting to master at %1: %2

-There was an error opening a connection to the master. The error is -shown in the log message. -

XFRIN_GOT_INCREMENTAL_RESP got incremental response for %1

-In an attempt of IXFR processing, the begenning SOA of the first difference -(following the initial SOA that specified the final SOA for all the -differences) was found. This means a connection for xfrin tried IXFR -and really aot a response for incremental updates. -

XFRIN_GOT_NONINCREMENTAL_RESP got nonincremental response for %1

-Non incremental transfer was detected at the "first data" of a transfer, -which is the RR following the initial SOA. Non incremental transfer is -either AXFR or AXFR-style IXFR. In the latter case, it means that -in a response to IXFR query the first data is not SOA or its SOA serial -is not equal to the requested SOA serial. -

XFRIN_IMPORT_DNS error importing python DNS module: %1

-There was an error importing the python DNS module pydnspp. The most -likely cause is a PYTHONPATH problem. -

XFRIN_IXFR_UPTODATE IXFR requested serial for %1 is %2, master has %3, not updating

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

XFRIN_MSGQ_SEND_ERROR error while contacting %1 and %2

-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 -was killed. -

XFRIN_MSGQ_SEND_ERROR_ZONE_MANAGER error while contacting %1

-There was a problem sending a message to the zone manager. This most -likely means that the msgq daemon has quit or was killed. -

XFRIN_NOTIFY_UNKNOWN_MASTER got notification to retransfer zone %1 from %2, expected %3

-The system received a notify for the given zone, but the address it came -from does not match the master address in the Xfrin configuration. The notify -is ignored. This may indicate that the configuration for the master is wrong, -that a wrong machine is sending notifies, or that fake notifies are being sent. -

XFRIN_RETRANSFER_UNKNOWN_ZONE got notification to retransfer unknown zone %1

-There was an internal command to retransfer the given zone, but the -zone is not known to the system. This may indicate that the configuration -for xfrin is incomplete, or there was a typographical error in the -zone name in the configuration. -

XFRIN_STARTING starting resolver with command line '%1'

-An informational message, this is output when the resolver starts up. -

XFRIN_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down

-There was a keyboard interrupt signal to stop the xfrin daemon. The -daemon will now shut down. -

XFRIN_UNKNOWN_ERROR unknown error: %1

-An uncaught exception was raised while running the xfrin daemon. The -exception message is printed in the log message. -

XFRIN_XFR_OTHER_FAILURE %1 transfer of zone %2 failed: %3

-The XFR transfer for the given zone has failed due to a problem outside -of the xfrin module. Possible reasons are a broken DNS message or failure -in database connection. The error is shown in the log message. -

XFRIN_XFR_PROCESS_FAILURE %1 transfer of zone %2/%3 failed: %4

-An XFR session failed outside the main protocol handling. This -includes an error at the data source level at the initialization -phase, unexpected failure in the network connection setup to the -master server, or even more unexpected failure due to unlikely events -such as memory allocation failure. Details of the error are shown in -the log message. In general, these errors are not really expected -ones, and indicate an installation error or a program bug. The -session handler thread tries to clean up all intermediate resources -even on these errors, but it may be incomplete. So, if this log -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. -

XFRIN_XFR_TRANSFER_FAILURE %1 transfer of zone %2 with %3 failed: %4

-The XFR transfer for the given zone has failed due to an internal error. -The error is shown in the log message. -

XFRIN_XFR_TRANSFER_FALLBACK falling back from IXFR to AXFR for %1

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

XFRIN_XFR_TRANSFER_PROTOCOL_ERROR %1 transfer of zone %2 with %3 failed: %4

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

XFRIN_XFR_TRANSFER_STARTED %1 transfer of zone %2 started

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

XFRIN_XFR_TRANSFER_SUCCESS %1 transfer of zone %2 succeeded

-The XFR transfer of the given zone was successfully completed. -

XFRIN_ZONE_CREATED Zone %1 not found in the given data source, newly created

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

XFRIN_ZONE_MULTIPLE_SOA Zone %1 has %2 SOA RRs

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

XFRIN_ZONE_NO_SOA Zone %1 does not have SOA

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

XFRIN_ZONE_SERIAL_AHEAD Serial number (%1) for %2 received from master %3 < ours (%4)

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

XFROUT_BAD_TSIG_KEY_STRING bad TSIG key string: %1

-The TSIG key string as read from the configuration does not represent -a valid TSIG key. -

XFROUT_CC_SESSION_ERROR error reading from cc channel: %1

-There was a problem reading from the command and control channel. The -most likely cause is that the msgq daemon is not running. -

XFROUT_CC_SESSION_TIMEOUT_ERROR timeout waiting for cc response

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

XFROUT_CONFIG_ERROR error found in configuration data: %1

-The xfrout process encountered an error when installing the configuration at -startup time. Details of the error are included in the log message. -

XFROUT_FETCH_REQUEST_ERROR socket error while fetching a request from the auth daemon

-There was a socket error while contacting the b10-auth daemon to -fetch a transfer request. The auth daemon may have shutdown. -

XFROUT_HANDLE_QUERY_ERROR error while handling query: %1

-There was a general error handling an xfrout query. The error is shown -in the message. In principle this error should not appear, and points -to an oversight catching exceptions in the right place. However, to -ensure the daemon keeps running, this error is caught and reported. -

XFROUT_IMPORT error importing python module: %1

-There was an error importing a python module. One of the modules needed -by xfrout could not be found. This suggests that either some libraries -are missing on the system, or the PYTHONPATH variable is not correct. -The specific place where this library needs to be depends on your -system and your specific installation. -

XFROUT_IXFR_MULTIPLE_SOA IXFR client %1: authority section has multiple SOAs

-An IXFR request was received with more than one SOA RRs in the authority -section. The xfrout daemon rejects the request with an RCODE of -FORMERR. -

XFROUT_IXFR_NO_JOURNAL_SUPPORT IXFR client %1, %2: journaling not supported in the data source, falling back to AXFR

-An IXFR request was received but the underlying data source did -not support journaling. The xfrout daemon fell back to AXFR-style -IXFR. -

XFROUT_IXFR_NO_SOA IXFR client %1: missing SOA

-An IXFR request was received with no SOA RR in the authority section. -The xfrout daemon rejects the request with an RCODE of FORMERR. -

XFROUT_IXFR_NO_VERSION IXFR client %1, %2: version (%3 to %4) not in journal, falling back to AXFR

-An IXFR request was received, but the requested range of differences -were not found in the data source. The xfrout daemon fell back to -AXFR-style IXFR. -

XFROUT_IXFR_NO_ZONE IXFR client %1, %2: zone not found with journal

-The requested zone in IXFR was not found in the data source -even though the xfrout daemon sucessfully found the SOA RR of the zone -in the data source. This can happen if the administrator removed the -zone from the data source within the small duration between these -operations, but it's more likely to be a bug or broken data source. -Unless you know why this message was logged, and especially if it -happens often, it's advisable to check whether the data source is -valid for this zone. The xfrout daemon considers it a possible, -though unlikely, event, and returns a response with an RCODE of -NOTAUTH. -

XFROUT_IXFR_UPTODATE IXFR client %1, %2: client version is new enough (theirs=%3, ours=%4)

-An IXFR request was received, but the client's SOA version is the same as -or newer than that of the server. The xfrout server responds to the -request with the answer section being just one SOA of that version. -Note: as of this wrting the 'newer version' cannot be identified due to -the lack of support for the serial number arithmetic. This will soon -be implemented. -

XFROUT_MODULECC_SESSION_ERROR error encountered by configuration/command module: %1

-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 xfrout -failed to start at initialization. A detailed error message from the module -will also be displayed. -

XFROUT_NEW_CONFIG Update xfrout configuration

-New configuration settings have been sent from the configuration -manager. The xfrout daemon will now apply them. -

XFROUT_NEW_CONFIG_DONE Update xfrout configuration done

-The xfrout daemon is now done reading the new configuration settings -received from the configuration manager. -

XFROUT_NOTIFY_COMMAND received command to send notifies for %1/%2

-The xfrout daemon received a command on the command channel that -NOTIFY packets should be sent for the given zone. -

XFROUT_PARSE_QUERY_ERROR error parsing query: %1

-There was a parse error while reading an incoming query. The parse -error is shown in the log message. A remote client sent a packet we -do not understand or support. The xfrout request will be ignored. -In general, this should only occur for unexpected problems like -memory allocation failures, as the query should already have been -parsed by the b10-auth daemon, before it was passed here. -

XFROUT_PROCESS_REQUEST_ERROR error processing transfer request: %2

-There was an error processing a transfer request. The error is included -in the log message, but at this point no specific information other -than that could be given. This points to incomplete exception handling -in the code. -

XFROUT_QUERY_DROPPED %1 client %2: request to transfer %3 dropped

-The xfrout process silently dropped a request to transfer zone to -given host. This is required by the ACLs. The %2 represents the IP -address and port of the peer requesting the transfer, and the %3 -represents the zone name and class. -

XFROUT_QUERY_QUOTA_EXCCEEDED %1 client %2: request denied due to quota (%3)

-The xfr request was rejected because the server was already handling -the maximum number of allowable transfers as specified in the transfers_out -configuration parameter, which is also shown in the log message. The -request was immediately responded and terminated with an RCODE of REFUSED. -This can happen for a busy xfrout server, and you may want to increase -this parameter; if the server is being too busy due to requests from -unexpected clients you may want to restrict the legitimate clients -with ACL. -

XFROUT_QUERY_REJECTED %1 client %2: request to transfer %3 rejected

-The xfrout process rejected (by REFUSED rcode) a request to transfer zone to -given host. This is because of ACLs. The %2 represents the IP -address and port of the peer requesting the transfer, and the %3 -represents the zone name and class. -

XFROUT_RECEIVED_SHUTDOWN_COMMAND shutdown command received

-The xfrout daemon received a shutdown command from the command channel -and will now shut down. -

XFROUT_RECEIVE_FILE_DESCRIPTOR_ERROR error receiving the file descriptor for an XFR connection

-There was an error receiving the file descriptor for the transfer -request. Normally, the request is received by b10-auth, and passed on -to the xfrout daemon, so it can answer directly. However, there was a -problem receiving this file descriptor. The request will be ignored. -

XFROUT_REMOVE_OLD_UNIX_SOCKET_FILE_ERROR error removing unix socket file %1: %2

-The unix socket file xfrout needs for contact with the auth daemon -already exists, and needs to be removed first, but there is a problem -removing it. It is likely that we do not have permission to remove -this file. The specific error is show in the log message. The xfrout -daemon will shut down. -

XFROUT_REMOVE_UNIX_SOCKET_FILE_ERROR error clearing unix socket file %1: %2

-When shutting down, the xfrout daemon tried to clear the unix socket -file used for communication with the auth daemon. It failed to remove -the file. The reason for the failure is given in the error message. -

XFROUT_SOCKET_SELECT_ERROR error while calling select() on request socket: %1

-There was an error while calling select() on the socket that informs -the xfrout daemon that a new xfrout request has arrived. This should -be a result of rare local error such as memory allocation failure and -shouldn't happen under normal conditions. The error is included in the -log message. -

XFROUT_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down

-There was a keyboard interrupt signal to stop the xfrout daemon. The -daemon will now shut down. -

XFROUT_STOPPING the xfrout daemon is shutting down

-The current transfer is aborted, as the xfrout daemon is shutting down. -

XFROUT_UNIX_SOCKET_FILE_IN_USE another xfrout process seems to be using the unix socket file %1

-While starting up, the xfrout daemon tried to clear the unix domain -socket needed for contacting the b10-auth daemon to pass requests -on, but the file is in use. The most likely cause is that another -xfrout daemon process is still running. This xfrout daemon (the one -printing this message) will not start. -

XFROUT_XFR_TRANSFER_CHECK_ERROR %1 client %2: check for transfer of %3 failed: %4

-Pre-response check for an incomding XFR request failed unexpectedly. -The most likely cause of this is that some low level error in the data -source, but it may also be other general (more unlikely) errors such -as memory shortage. Some detail of the error is also included in the -message. The xfrout server tries to return a SERVFAIL response in this case. -

XFROUT_XFR_TRANSFER_DONE %1 client %2: transfer of %3 complete

-The transfer of the given zone has been completed successfully, or was -aborted due to a shutdown event. -

XFROUT_XFR_TRANSFER_ERROR %1 client %2: error transferring zone %3: %4

-An uncaught exception was encountered while sending the response to -an AXFR query. The error message of the exception is included in the -log message, but this error most likely points to incomplete exception -handling in the code. -

XFROUT_XFR_TRANSFER_FAILED %1 client %2: transfer of %3 failed, rcode: %4

-A transfer out for the given zone failed. An error response is sent -to the client. The given rcode is the rcode that is set in the error -response. This is either NOTAUTH (we are not authoritative for the -zone), SERVFAIL (our internal database is missing the SOA record for -the zone), or REFUSED (the limit of simultaneous outgoing AXFR -transfers, as specified by the configuration value -Xfrout/max_transfers_out, has been reached). -

XFROUT_XFR_TRANSFER_STARTED %1 client %2: transfer of zone %3 has started

-A transfer out of the given zone has started. -

ZONEMGR_CCSESSION_ERROR command channel session error: %1

-An error was encountered on the command channel. The message indicates -the nature of the error. -

ZONEMGR_JITTER_TOO_BIG refresh_jitter is too big, setting to 0.5

-The value specified in the configuration for the refresh jitter is too large -so its value has been set to the maximum of 0.5. -

ZONEMGR_KEYBOARD_INTERRUPT exiting zonemgr process as result of keyboard interrupt

-An informational message output when the zone manager was being run at a -terminal and it was terminated via a keyboard interrupt signal. -

ZONEMGR_LOAD_ZONE loading zone %1 (class %2)

-This is a debug message indicating that the zone of the specified class -is being loaded. -

ZONEMGR_NO_MASTER_ADDRESS internal BIND 10 command did not contain address of master

-A command received by the zone manager from the Auth module did not -contain the address of the master server from which a NOTIFY message -was received. This may be due to an internal programming error; please -submit a bug report. -

ZONEMGR_NO_SOA zone %1 (class %2) does not have an SOA record

-When loading the named zone of the specified class the zone manager -discovered that the data did not contain an SOA record. The load has -been abandoned. -

ZONEMGR_NO_TIMER_THREAD trying to stop zone timer thread but it is not running

-An attempt was made to stop the timer thread (used to track when zones -should be refreshed) but it was not running. This may indicate an -internal program error. Please submit a bug report. -

ZONEMGR_NO_ZONE_CLASS internal BIND 10 command did not contain class of zone

-A command received by the zone manager from another BIND 10 module did -not contain the class of the zone on which the zone manager should act. -This may be due to an internal programming error; please submit a -bug report. -

ZONEMGR_NO_ZONE_NAME internal BIND 10 command did not contain name of zone

-A command received by the zone manager from another BIND 10 module did -not contain the name of the zone on which the zone manager should act. -This may be due to an internal programming error; please submit a -bug report. -

ZONEMGR_RECEIVE_NOTIFY received NOTIFY command for zone %1 (class %2)

-This is a debug message indicating that the zone manager has received a -NOTIFY command over the command channel. The command is sent by the Auth -process when it is acting as a slave server for the zone and causes the -zone manager to record the master server for the zone and start a timer; -when the timer expires, the master will be polled to see if it contains -new data. -

ZONEMGR_RECEIVE_SHUTDOWN received SHUTDOWN command

-This is a debug message indicating that the zone manager has received -a SHUTDOWN command over the command channel from the Boss process. -It will act on this command and shut down. -

ZONEMGR_RECEIVE_UNKNOWN received unknown command '%1'

-This is a warning message indicating that the zone manager has received -the stated command over the command channel. The command is not known -to the zone manager and although the command is ignored, its receipt -may indicate an internal error. Please submit a bug report. -

ZONEMGR_RECEIVE_XFRIN_FAILED received XFRIN FAILED command for zone %1 (class %2)

-This is a debug message indicating that the zone manager has received -an XFRIN FAILED command over the command channel. The command is sent -by the Xfrin process when a transfer of zone data into the system has -failed, and causes the zone manager to schedule another transfer attempt. -

ZONEMGR_RECEIVE_XFRIN_SUCCESS received XFRIN SUCCESS command for zone %1 (class %2)

-This is a debug message indicating that the zone manager has received -an XFRIN SUCCESS command over the command channel. The command is sent -by the Xfrin process when the transfer of zone data into the system has -succeeded, and causes the data to be loaded and served by BIND 10. -

ZONEMGR_REFRESH_ZONE refreshing zone %1 (class %2)

-The zone manager is refreshing the named zone of the specified class -with updated information. -

ZONEMGR_SELECT_ERROR error with select(): %1

-An attempt to wait for input from a socket failed. The failing operation -is a call to the operating system's select() function, which failed for -the given reason. -

ZONEMGR_SEND_FAIL failed to send command to %1, session has been closed

-The zone manager attempted to send a command to the named BIND 10 module, -but the send failed. The session between the modules has been closed. -

ZONEMGR_SESSION_ERROR unable to establish session to command channel daemon

-The zonemgr process was not able to be started because it could not -connect to the command channel daemon. The most usual cause of this -problem is that the daemon is not running. -

ZONEMGR_SESSION_TIMEOUT timeout on session to command channel daemon

-The zonemgr process was not able to be started because it timed out when -connecting to the command channel daemon. The most usual cause of this -problem is that the daemon is not running. -

ZONEMGR_SHUTDOWN zone manager has shut down

-A debug message, output when the zone manager has shut down completely. -

ZONEMGR_STARTING zone manager starting

-A debug message output when the zone manager starts up. -

ZONEMGR_TIMER_THREAD_RUNNING trying to start timer thread but one is already running

-This message is issued when an attempt is made to start the timer -thread (which keeps track of when zones need a refresh) but one is -already running. It indicates either an error in the program logic or -a problem with stopping a previous instance of the timer. Please submit -a bug report. -

ZONEMGR_UNKNOWN_ZONE_FAIL zone %1 (class %2) is not known to the zone manager

-An XFRIN operation has failed but the zone that was the subject of the -operation is not being managed by the zone manager. This may indicate -an error in the program (as the operation should not have been initiated -if this were the case). Please submit a bug report. -

ZONEMGR_UNKNOWN_ZONE_NOTIFIED notified zone %1 (class %2) is not known to the zone manager

-A NOTIFY was received but the zone that was the subject of the operation -is not being managed by the zone manager. This may indicate an error -in the program (as the operation should not have been initiated if this -were the case). Please submit a bug report. -

ZONEMGR_UNKNOWN_ZONE_SUCCESS zone %1 (class %2) is not known to the zone manager

-An XFRIN operation has succeeded but the zone received is not being -managed by the zone manager. This may indicate an error in the program -(as the operation should not have been initiated if this were the case). -Please submit a bug report. -

-

diff --git a/doc/guide/bind10-messages.xml b/doc/guide/bind10-messages.xml deleted file mode 100644 index c085cb14b9..0000000000 --- a/doc/guide/bind10-messages.xml +++ /dev/null @@ -1,5896 +0,0 @@ - - - -%version; -]> - - - - - - BIND 10 Messages Manual - - - 2011-2012Internet Systems Consortium, Inc. - - - - 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 &__VERSION__;. - The most up-to-date version of this document, along with - other documents for BIND 10, can be found at - . - - - - This is the messages manual for BIND 10 version - &__VERSION__;. - - - - Introduction - - This document lists each message that can be logged by the - programs in the BIND 10 package. Each entry in this manual - is of the form: - IDENTIFICATION message-text - ... where "IDENTIFICATION" is the message identification included - in each message logged and "message-text" is the accompanying - message text. The "message-text" may include placeholders of the - form "%1", "%2" etc.; these parameters are replaced by relevant - values when the message is logged. - - - Each entry is also accompanied by a description giving more - information about the circumstances that result in the message - being logged. - - - For information on configuring and using BIND 10 logging, - refer to the BIND 10 Guide. - - - - - BIND 10 Messages - - - - -ASIODNS_FD_ADD_TCP adding a new TCP server by opened fd %1 - -A debug message informing about installing a file descriptor as a server. -The file descriptor number is noted. - - - - -ASIODNS_FD_ADD_UDP adding a new UDP server by opened fd %1 - -A debug message informing about installing a file descriptor as a server. -The file descriptor number is noted. - - - - -ASIODNS_FETCH_COMPLETED upstream fetch to %1(%2) has now completed - -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. - - - - -ASIODNS_FETCH_STOPPED upstream fetch to %1(%2) has been stopped - -An external component has requested the halting of an upstream fetch. This -is an allowed operation, and the message should only appear if debug is -enabled. - - - - -ASIODNS_OPEN_SOCKET error %1 opening %2 socket to %3(%4) - -The asynchronous I/O code encountered an error when trying to open a socket -of the specified protocol in order to send a message to the target address. -The number of the system error that caused the problem is given in the -message. - - - - -ASIODNS_READ_DATA error %1 reading %2 data from %3(%4) - -The asynchronous I/O code encountered an error when trying to read data from -the specified address on the given protocol. The number of the system -error that caused the problem is given in the message. - - - - -ASIODNS_READ_TIMEOUT receive timeout while waiting for data from %1(%2) - -An upstream fetch from the specified address timed out. This may happen for -any number of reasons and is most probably a problem at the remote server -or a problem on the network. The message will only appear if debug is -enabled. - - - - -ASIODNS_SEND_DATA error %1 sending data using %2 to %3(%4) - -The asynchronous I/O code encountered an error when trying to send data to -the specified address on the given protocol. The number of the system -error that caused the problem is given in the message. - - - - -ASIODNS_UNKNOWN_ORIGIN unknown origin for ASIO error code %1 (protocol: %2, address %3) - -An internal consistency check on the origin of a message from the -asynchronous I/O module failed. This may indicate an internal error; -please submit a bug report. - - - - -ASIODNS_UNKNOWN_RESULT unknown result (%1) when IOFetch::stop() was executed for I/O to %2(%3) - -An internal error indicating that the termination method of the resolver's -upstream fetch class was called with an unknown result code (which is -given in the message). Please submit a bug report. - - - - -AUTH_AXFR_ERROR error handling AXFR request: %1 - -This is a debug message produced by the authoritative server when it -has encountered an error processing an AXFR request. The message gives -the reason for the error, and the server will return a SERVFAIL code to -the sender. - - - - -AUTH_AXFR_UDP AXFR query received over UDP - -This is a debug message output when the authoritative server has received -an AXFR query over UDP. Use of UDP for AXFRs is not permitted by the -protocol, so the server will return a FORMERR error to the sender. - - - - -AUTH_COMMAND_FAILED execution of command channel instruction '%1' failed: %2 - -Execution of the specified command by the authoritative server failed. The -message contains the reason for the failure. - - - - -AUTH_CONFIG_CHANNEL_CREATED configuration session channel created - -This is a debug message indicating that authoritative server has created -the channel to the configuration manager. It is issued during server -startup is an indication that the initialization is proceeding normally. - - - - -AUTH_CONFIG_CHANNEL_ESTABLISHED configuration session channel established - -This is a debug message indicating that authoritative server -has established communication the configuration manager over the -previously-created channel. It is issued during server startup is an -indication that the initialization is proceeding normally. - - - - -AUTH_CONFIG_CHANNEL_STARTED configuration session channel started - -This is a debug message, issued when the authoritative server has -posted a request to be notified when new configuration information is -available. It is issued during server startup is an indication that -the initialization is proceeding normally. - - - - -AUTH_CONFIG_LOAD_FAIL load of configuration failed: %1 - -An attempt to configure the server with information from the configuration -database during the startup sequence has failed. (The reason for -the failure is given in the message.) The server will continue its -initialization although it may not be configured in the desired way. - - - - -AUTH_CONFIG_UPDATE_FAIL update of configuration failed: %1 - -At attempt to update the configuration the server with information -from the configuration database has failed, the reason being given in -the message. - - - - -AUTH_DATA_SOURCE data source database file: %1 - -This is a debug message produced by the authoritative server when it accesses a -datebase data source, listing the file that is being accessed. - - - - -AUTH_DNS_SERVICES_CREATED DNS services created - -This is a debug message indicating that the component that will handling -incoming queries for the authoritative server (DNSServices) has been -successfully created. It is issued during server startup is an indication -that the initialization is proceeding normally. - - - - -AUTH_HEADER_PARSE_FAIL unable to parse header in received DNS packet: %1 - -This is a debug message, generated by the authoritative server when an -attempt to parse the header of a received DNS packet has failed. (The -reason for the failure is given in the message.) The server will drop the -packet. - - - - -AUTH_INVALID_STATISTICS_DATA invalid specification of statistics data specified - -An error was encountered when the authoritiative server specified -statistics data which is invalid for the auth specification file. - - - - -AUTH_LOAD_TSIG loading TSIG keys - -This is a debug message indicating that the authoritative server -has requested the keyring holding TSIG keys from the configuration -database. It is issued during server startup is an indication that the -initialization is proceeding normally. - - - - -AUTH_LOAD_ZONE loaded zone %1/%2 - -This debug message is issued during the processing of the 'loadzone' command -when the authoritative server has successfully loaded the named zone of the -named class. - - - - -AUTH_MEM_DATASRC_DISABLED memory data source is disabled for class %1 - -This is a debug message reporting that the authoritative server has -discovered that the memory data source is disabled for the given class. - - - - -AUTH_MEM_DATASRC_ENABLED memory data source is enabled for class %1 - -This is a debug message reporting that the authoritative server has -discovered that the memory data source is enabled for the given class. - - - - -AUTH_NOTIFY_QUESTIONS invalid number of questions (%1) in incoming NOTIFY - -This debug message is logged by the authoritative server when it receives -a NOTIFY packet that contains zero or more than one question. (A valid -NOTIFY packet contains one question.) The server will return a FORMERR -error to the sender. - - - - -AUTH_NOTIFY_RRTYPE invalid question RR type (%1) in incoming NOTIFY - -This debug message is logged by the authoritative server when it receives -a NOTIFY packet that an RR type of something other than SOA in the -question section. (The RR type received is included in the message.) The -server will return a FORMERR error to the sender. - - - - -AUTH_NO_STATS_SESSION session interface for statistics is not available - -The authoritative server had no session with the statistics module at the -time it attempted to send it data: the attempt has been abandoned. This -could be an error in configuration. - - - - -AUTH_NO_XFRIN received NOTIFY but XFRIN session is not running - -This is a debug message produced by the authoritative server when it receives -a NOTIFY packet but the XFRIN process is not running. The packet will be -dropped and nothing returned to the sender. - - - - -AUTH_PACKET_PARSE_ERROR unable to parse received DNS packet: %1 - -This is a debug message, generated by the authoritative server when an -attempt to parse a received DNS packet has failed due to something other -than a protocol error. The reason for the failure is given in the message; -the server will return a SERVFAIL error code to the sender. - - - - -AUTH_PACKET_PROTOCOL_ERROR DNS packet protocol error: %1. Returning %2 - -This is a debug message, generated by the authoritative server when an -attempt to parse a received DNS packet has failed due to a protocol error. -The reason for the failure is given in the message, as is the error code -that will be returned to the sender. - - - - -AUTH_PACKET_RECEIVED message received:\n%1 - -This is a debug message output by the authoritative server when it -receives a valid DNS packet. - -Note: This message includes the packet received, rendered in the form of -multiple lines of text. For this reason, it is suggested that this log message -not be routed to the syslog file, where the multiple lines could confuse -programs that expect a format of one message per line. - - - - -AUTH_PROCESS_FAIL message processing failure: %1 - -This message is generated by the authoritative server when it has -encountered an internal error whilst processing a received packet: -the cause of the error is included in the message. - -The server will return a SERVFAIL error code to the sender of the packet. -This message indicates a potential error in the server. Please open a -bug ticket for this issue. - - - - -AUTH_RECEIVED_COMMAND command '%1' received - -This is a debug message issued when the authoritative server has received -a command on the command channel. - - - - -AUTH_RECEIVED_SENDSTATS command 'sendstats' received - -This is a debug message issued when the authoritative server has received -a command from the statistics module to send it data. The 'sendstats' -command is handled differently to other commands, which is why the debug -message associated with it has its own code. - - - - -AUTH_RESPONSE_RECEIVED received response message, ignoring - -This is a debug message, this is output if the authoritative server -receives a DNS packet with the QR bit set, i.e. a DNS response. The -server ignores the packet as it only responds to question packets. - - - - -AUTH_SEND_ERROR_RESPONSE sending an error response (%1 bytes):\n%2 - -This is a debug message recording that the authoritative server is sending -an error response to the originator of the query. A previous message will -have recorded details of the failure. - -Note: This message includes the packet sent, rendered in the form of -multiple lines of text. For this reason, it is suggested that this log message -not be routed to the syslog file, where the multiple lines could confuse -programs that expect a format of one message per line. - - - - -AUTH_SEND_NORMAL_RESPONSE sending an error response (%1 bytes):\n%2 - -This is a debug message recording that the authoritative server is sending -a response to the originator of a query. - -Note: This message includes the packet sent, rendered in the form of -multiple lines of text. For this reason, it is suggested that this log message -not be routed to the syslog file, where the multiple lines could confuse -programs that expect a format of one message per line. - - - - -AUTH_SERVER_CREATED server created - -An informational message indicating that the authoritative server process has -been created and is initializing. The AUTH_SERVER_STARTED message will be -output when initialization has successfully completed and the server starts -accepting queries. - - - - -AUTH_SERVER_FAILED server failed: %1 - -The authoritative server has encountered a fatal error and is terminating. The -reason for the failure is included in the message. - - - - -AUTH_SERVER_STARTED server started - -Initialization of the authoritative server has completed successfully -and it is entering the main loop, waiting for queries to arrive. - - - - -AUTH_SQLITE3 nothing to do for loading sqlite3 - -This is a debug message indicating that the authoritative server has -found that the data source it is loading is an SQLite3 data source, -so no further validation is needed. - - - - -AUTH_STATS_CHANNEL_CREATED STATS session channel created - -This is a debug message indicating that the authoritative server has -created a channel to the statistics process. It is issued during server -startup is an indication that the initialization is proceeding normally. - - - - -AUTH_STATS_CHANNEL_ESTABLISHED STATS session channel established - -This is a debug message indicating that the authoritative server -has established communication over the previously created statistics -channel. It is issued during server startup is an indication that the -initialization is proceeding normally. - - - - -AUTH_STATS_COMMS communication error in sending statistics data: %1 - -An error was encountered when the authoritative server tried to send data -to the statistics daemon. The message includes additional information -describing the reason for the failure. - - - - -AUTH_STATS_TIMEOUT timeout while sending statistics data: %1 - -The authoritative server sent data to the statistics daemon but received -no acknowledgement within the specified time. The message includes -additional information describing the reason for the failure. - - - - -AUTH_STATS_TIMER_DISABLED statistics timer has been disabled - -This is a debug message indicating that the statistics timer has been -disabled in the authoritative server and no statistics information is -being produced. - - - - -AUTH_STATS_TIMER_SET statistics timer set to %1 second(s) - -This is a debug message indicating that the statistics timer has been -enabled and that the authoritative server will produce statistics data -at the specified interval. - - - - -AUTH_UNSUPPORTED_OPCODE unsupported opcode: %1 - -This is a debug message, produced when a received DNS packet being -processed by the authoritative server has been found to contain an -unsupported opcode. (The opcode is included in the message.) The server -will return an error code of NOTIMPL to the sender. - - - - -AUTH_XFRIN_CHANNEL_CREATED XFRIN session channel created - -This is a debug message indicating that the authoritative server has -created a channel to the XFRIN (Transfer-in) process. It is issued -during server startup is an indication that the initialization is -proceeding normally. - - - - -AUTH_XFRIN_CHANNEL_ESTABLISHED XFRIN session channel established - -This is a debug message indicating that the authoritative server has -established communication over the previously-created channel to the -XFRIN (Transfer-in) process. It is issued during server startup is an -indication that the initialization is proceeding normally. - - - - -AUTH_ZONEMGR_COMMS error communicating with zone manager: %1 - -This is a debug message output during the processing of a NOTIFY request. -An error (listed in the message) has been encountered whilst communicating -with the zone manager. The NOTIFY request will not be honored. - - - - -AUTH_ZONEMGR_ERROR received error response from zone manager: %1 - -This is a debug message output during the processing of a NOTIFY -request. The zone manager component has been informed of the request, -but has returned an error response (which is included in the message). The -NOTIFY request will not be honored. - - - - -BIND10_CHECK_MSGQ_ALREADY_RUNNING checking if msgq is already running - -The boss process is starting up and will now check if the message bus -daemon is already running. If so, it will not be able to start, as it -needs a dedicated message bus. - - - - -BIND10_COMPONENT_FAILED component %1 (pid %2) failed with %3 exit status - -The process terminated, but the bind10 boss didn't expect it to, which means -it must have failed. - - - - -BIND10_COMPONENT_RESTART component %1 is about to restart - -The named component failed previously and we will try to restart it to provide -as flawless service as possible, but it should be investigated what happened, -as it could happen again. - - - - -BIND10_COMPONENT_START component %1 is starting - -The named component is about to be started by the boss process. - - - - -BIND10_COMPONENT_START_EXCEPTION component %1 failed to start: %2 - -An exception (mentioned in the message) happened during the startup of the -named component. The componet is not considered started and further actions -will be taken about it. - - - - -BIND10_COMPONENT_STOP component %1 is being stopped - -A component is about to be asked to stop willingly by the boss. - - - - -BIND10_COMPONENT_UNSATISFIED component %1 is required to run and failed - -A component failed for some reason (see previous messages). It is either a core -component or needed component that was just started. In any case, the system -can't continue without it and will terminate. - - - - -BIND10_CONFIGURATOR_BUILD building plan '%1' -> '%2' - -A debug message. This indicates that the configurator is building a plan -how to change configuration from the older one to newer one. This does no -real work yet, it just does the planning what needs to be done. - - - - -BIND10_CONFIGURATOR_PLAN_INTERRUPTED configurator plan interrupted, only %1 of %2 done - -There was an exception during some planned task. The plan will not continue and -only some tasks of the plan were completed. The rest is aborted. The exception -will be propagated. - - - - -BIND10_CONFIGURATOR_RECONFIGURE reconfiguring running components - -A different configuration of which components should be running is being -installed. All components that are no longer needed will be stopped and -newly introduced ones started. This happens at startup, when the configuration -is read the first time, or when an operator changes configuration of the boss. - - - - -BIND10_CONFIGURATOR_RUN running plan of %1 tasks - -A debug message. The configurator is about to execute a plan of actions it -computed previously. - - - - -BIND10_CONFIGURATOR_START bind10 component configurator is starting up - -The part that cares about starting and stopping the right component from the -boss process is starting up. This happens only once at the startup of the -boss process. It will start the basic set of processes now (the ones boss -needs to read the configuration), the rest will be started after the -configuration is known. - - - - -BIND10_CONFIGURATOR_STOP bind10 component configurator is shutting down - -The part that cares about starting and stopping processes in the boss is -shutting down. All started components will be shut down now (more precisely, -asked to terminate by their own, if they fail to comply, other parts of -the boss process will try to force them). - - - - -BIND10_CONFIGURATOR_TASK performing task %1 on %2 - -A debug message. The configurator is about to perform one task of the plan it -is currently executing on the named component. - - - - -BIND10_INVALID_STATISTICS_DATA invalid specification of statistics data specified - -An error was encountered when the boss module specified -statistics data which is invalid for the boss specification file. - - - - -BIND10_INVALID_USER invalid user: %1 - -The boss process was started with the -u option, to drop root privileges -and continue running as the specified user, but the user is unknown. - - - - -BIND10_KILLING_ALL_PROCESSES killing all started processes - -The boss module was not able to start every process it needed to start -during startup, and will now kill the processes that did get started. - - - - -BIND10_KILL_PROCESS killing process %1 - -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 - - - - -BIND10_LOST_SOCKET_CONSUMER consumer %1 of sockets disconnected, considering all its sockets closed - -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. - - - - -BIND10_MSGQ_ALREADY_RUNNING msgq daemon already running, cannot start - -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 -another instance of BIND10, with the same msgq domain socket, is -running, which needs to be stopped. - - - - -BIND10_MSGQ_DISAPPEARED msgq channel disappeared - -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. - - - - -BIND10_NO_SOCKET couldn't send a socket for token %1 because of error: %2 - -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. - - - - -BIND10_PROCESS_ENDED process %2 of %1 ended with status %3 - -This indicates a process started previously terminated. The process id -and component owning the process are indicated, as well as the exit code. -This doesn't distinguish if the process was supposed to terminate or not. - - - - -BIND10_READING_BOSS_CONFIGURATION reading boss configuration - -The boss process is starting up, and will now process the initial -configuration, as received from the configuration manager. - - - - -BIND10_RECEIVED_COMMAND received command: %1 - -The boss module received a command and shall now process it. The command -is printed. - - - - -BIND10_RECEIVED_NEW_CONFIGURATION received new configuration: %1 - -The boss module received a configuration update and is going to apply -it now. The new configuration is printed. - - - - -BIND10_RECEIVED_SIGNAL received signal %1 - -The boss module received the given signal. - - - - -BIND10_RESURRECTED_PROCESS resurrected %1 (PID %2) - -The given process has been restarted successfully, and is now running -with the given process id. - - - - -BIND10_RESURRECTING_PROCESS resurrecting dead %1 process... - -The given process has ended unexpectedly, and is now restarted. - - - - -BIND10_SELECT_ERROR error in select() call: %1 - -There was a fatal error in the call to select(), used to see if a child -process has ended or if there is a message on the message bus. This -should not happen under normal circumstances and is considered fatal, -so BIND 10 will now shut down. The specific error is printed. - - - - -BIND10_SEND_SIGKILL sending SIGKILL to %1 (PID %2) - -The boss module is sending a SIGKILL signal to the given process. - - - - -BIND10_SEND_SIGTERM sending SIGTERM to %1 (PID %2) - -The boss module is sending a SIGTERM signal to the given process. - - - - -BIND10_SETUID setting UID to %1 - -The boss switches the user it runs as to the given UID. - - - - -BIND10_SHUTDOWN stopping the server - -The boss process received a command or signal telling it to shut down. -It will send a shutdown command to each process. The processes that do -not shut down will then receive a SIGTERM signal. If that doesn't work, -it shall send SIGKILL signals to the processes still alive. - - - - -BIND10_SHUTDOWN_COMPLETE all processes ended, shutdown complete - -All child processes have been stopped, and the boss process will now -stop itself. - - - - -BIND10_SOCKCREATOR_BAD_CAUSE unknown error cause from socket creator: %1 - -The socket creator reported an error when creating a socket. But the function -which failed is unknown (not one of 'S' for socket or 'B' for bind). - - - - -BIND10_SOCKCREATOR_BAD_RESPONSE unknown response for socket request: %1 - -The boss requested a socket from the creator, but the answer is unknown. This -looks like a programmer error. - - - - -BIND10_SOCKCREATOR_EOF eof while expecting data from socket creator - -There should be more data from the socket creator, but it closed the socket. -It probably crashed. - - - - -BIND10_SOCKCREATOR_INIT initializing socket creator parser - -The boss module initializes routines for parsing the socket creator -protocol. - - - - -BIND10_SOCKCREATOR_KILL killing the socket creator - -The socket creator is being terminated the aggressive way, by sending it -sigkill. This should not happen usually. - - - - -BIND10_SOCKCREATOR_TERMINATE terminating socket creator - -The boss module sends a request to terminate to the socket creator. - - - - -BIND10_SOCKCREATOR_TRANSPORT_ERROR transport error when talking to the socket creator: %1 - -Either sending or receiving data from the socket creator failed with the given -error. The creator probably crashed or some serious OS-level problem happened, -as the communication happens only on local host. - - - - -BIND10_SOCKET_CREATED successfully created socket %1 - -The socket creator successfully created and sent a requested socket, it has -the given file number. - - - - -BIND10_SOCKET_ERROR error on %1 call in the creator: %2/%3 - -The socket creator failed to create the requested socket. It failed on the -indicated OS API function with given error. - - - - -BIND10_SOCKET_GET requesting socket [%1]:%2 of type %3 from the creator - -The boss forwards a request for a socket to the socket creator. - - - - -BIND10_STARTED_CC started configuration/command session - -Debug message given when BIND 10 has successfull started the object that -handles configuration and commands. - - - - -BIND10_STARTED_PROCESS started %1 - -The given process has successfully been started. - - - - -BIND10_STARTED_PROCESS_PID started %1 (PID %2) - -The given process has successfully been started, and has the given PID. - - - - -BIND10_STARTING starting BIND10: %1 - -Informational message on startup that shows the full version. - - - - -BIND10_STARTING_CC starting configuration/command session - -Informational message given when BIND 10 is starting the session object -that handles configuration and commands. - - - - -BIND10_STARTING_PROCESS starting process %1 - -The boss module is starting the given process. - - - - -BIND10_STARTING_PROCESS_PORT starting process %1 (to listen on port %2) - -The boss module is starting the given process, which will listen on the -given port number. - - - - -BIND10_STARTING_PROCESS_PORT_ADDRESS starting process %1 (to listen on %2#%3) - -The boss module is starting the given process, which will listen on the -given address and port number (written as <address>#<port>). - - - - -BIND10_STARTUP_COMPLETE BIND 10 started - -All modules have been successfully started, and BIND 10 is now running. - - - - -BIND10_STARTUP_ERROR error during startup: %1 - -There was a fatal error when BIND10 was trying to start. The error is -shown, and BIND10 will now shut down. - - - - -BIND10_STARTUP_UNEXPECTED_MESSAGE unrecognised startup message %1 - -During the startup process, a number of messages are exchanged between the -Boss process and the processes it starts. This error is output when a -message received by the Boss process is recognised as being of the -correct format but is unexpected. It may be that processes are starting -of sequence. - - - - -BIND10_STARTUP_UNRECOGNISED_MESSAGE unrecognised startup message %1 - -During the startup process, a number of messages are exchanged between the -Boss process and the processes it starts. This error is output when a -message received by the Boss process is not recognised. - - - - -BIND10_START_AS_NON_ROOT_AUTH starting b10-auth as a user, not root. This might fail. - -The authoritative server is being started or restarted without root privileges. -If the module needs these privileges, it may have problems starting. -Note that this issue should be resolved by the pending 'socket-creator' -process; once that has been implemented, modules should not need root -privileges anymore. See tickets #800 and #801 for more information. - - - - -BIND10_START_AS_NON_ROOT_RESOLVER starting b10-resolver as a user, not root. This might fail. - -The resolver is being started or restarted without root privileges. -If the module needs these privileges, it may have problems starting. -Note that this issue should be resolved by the pending 'socket-creator' -process; once that has been implemented, modules should not need root -privileges anymore. See tickets #800 and #801 for more information. - - - - -BIND10_STOP_PROCESS asking %1 to shut down - -The boss module is sending a shutdown command to the given module over -the message channel. - - - - -BIND10_UNKNOWN_CHILD_PROCESS_ENDED unknown child pid %1 exited - -An unknown child process has exited. The PID is printed, but no further -action will be taken by the boss process. - - - - -BIND10_WAIT_CFGMGR waiting for configuration manager process to initialize - -The configuration manager process is so critical to operation of BIND 10 -that after starting it, the Boss module will wait for it to initialize -itself before continuing. This debug message is produced during the -wait and may be output zero or more times depending on how long it takes -the configuration manager to start up. The total length of time Boss -will wait for the configuration manager before reporting an error is -set with the command line --wait switch, which has a default value of -ten seconds. - - - - -CACHE_ENTRY_MISSING_RRSET missing RRset to generate message for %1 - -The cache tried to generate the complete answer message. It knows the structure -of the message, but some of the RRsets to be put there are not in cache (they -probably expired already). Therefore it pretends the message was not found. - - - - -CACHE_LOCALZONE_FOUND found entry with key %1 in local zone data - -Debug message, noting that the requested data was successfully found in the -local zone data of the cache. - - - - -CACHE_LOCALZONE_UNKNOWN entry with key %1 not found in local zone data - -Debug message. The requested data was not found in the local zone data. - - - - -CACHE_LOCALZONE_UPDATE updating local zone element at key %1 - -Debug message issued when there's update to the local zone section of cache. - - - - -CACHE_MESSAGES_DEINIT deinitialized message cache - -Debug message. It is issued when the server deinitializes the message cache. - - - - -CACHE_MESSAGES_EXPIRED found an expired message entry for %1 in the message cache - -Debug message. The requested data was found in the message cache, but it -already expired. Therefore the cache removes the entry and pretends it found -nothing. - - - - -CACHE_MESSAGES_FOUND found a message entry for %1 in the message cache - -Debug message. We found the whole message in the cache, so it can be returned -to user without any other lookups. - - - - -CACHE_MESSAGES_INIT initialized message cache for %1 messages of class %2 - -Debug message issued when a new message cache is issued. It lists the class -of messages it can hold and the maximum size of the cache. - - - - -CACHE_MESSAGES_REMOVE removing old instance of %1/%2/%3 first - -Debug message. This may follow CACHE_MESSAGES_UPDATE and indicates that, while -updating, the old instance is being removed prior of inserting a new one. - - - - -CACHE_MESSAGES_UNCACHEABLE not inserting uncacheable message %1/%2/%3 - -Debug message, noting that the given message can not be cached. This is because -there's no SOA record in the message. See RFC 2308 section 5 for more -information. - - - - -CACHE_MESSAGES_UNKNOWN no entry for %1 found in the message cache - -Debug message. The message cache didn't find any entry for the given key. - - - - -CACHE_MESSAGES_UPDATE updating message entry %1/%2/%3 - -Debug message issued when the message cache is being updated with a new -message. Either the old instance is removed or, if none is found, new one -is created. - - - - -CACHE_RESOLVER_DEEPEST looking up deepest NS for %1/%2 - -Debug message. The resolver cache is looking up the deepest known nameserver, -so the resolution doesn't have to start from the root. - - - - -CACHE_RESOLVER_INIT initializing resolver cache for class %1 - -Debug message. The resolver cache is being created for this given class. - - - - -CACHE_RESOLVER_INIT_INFO initializing resolver cache for class %1 - -Debug message, the resolver cache is being created for this given class. The -difference from CACHE_RESOLVER_INIT is only in different format of passed -information, otherwise it does the same. - - - - -CACHE_RESOLVER_LOCAL_MSG message for %1/%2 found in local zone data - -Debug message. The resolver cache found a complete message for the user query -in the zone data. - - - - -CACHE_RESOLVER_LOCAL_RRSET RRset for %1/%2 found in local zone data - -Debug message. The resolver cache found a requested RRset in the local zone -data. - - - - -CACHE_RESOLVER_LOOKUP_MSG looking up message in resolver cache for %1/%2 - -Debug message. The resolver cache is trying to find a message to answer the -user query. - - - - -CACHE_RESOLVER_LOOKUP_RRSET looking up RRset in resolver cache for %1/%2 - -Debug message. The resolver cache is trying to find an RRset (which usually -originates as internally from resolver). - - - - -CACHE_RESOLVER_NO_QUESTION answer message for %1/%2 has empty question section - -The cache tried to fill in found data into the response message. But it -discovered the message contains no question section, which is invalid. -This is likely a programmer error, please submit a bug report. - - - - -CACHE_RESOLVER_UNKNOWN_CLASS_MSG no cache for class %1 - -Debug message. While trying to lookup a message in the resolver cache, it was -discovered there's no cache for this class at all. Therefore no message is -found. - - - - -CACHE_RESOLVER_UNKNOWN_CLASS_RRSET no cache for class %1 - -Debug message. While trying to lookup an RRset in the resolver cache, it was -discovered there's no cache for this class at all. Therefore no data is found. - - - - -CACHE_RESOLVER_UPDATE_MSG updating message for %1/%2/%3 - -Debug message. The resolver is updating a message in the cache. - - - - -CACHE_RESOLVER_UPDATE_RRSET updating RRset for %1/%2/%3 - -Debug message. The resolver is updating an RRset in the cache. - - - - -CACHE_RESOLVER_UPDATE_UNKNOWN_CLASS_MSG no cache for class %1 - -Debug message. While trying to insert a message into the cache, it was -discovered that there's no cache for the class of message. Therefore -the message will not be cached. - - - - -CACHE_RESOLVER_UPDATE_UNKNOWN_CLASS_RRSET no cache for class %1 - -Debug message. While trying to insert an RRset into the cache, it was -discovered that there's no cache for the class of the RRset. Therefore -the message will not be cached. - - - - -CACHE_RRSET_EXPIRED found expired RRset %1/%2/%3 - -Debug message. The requested data was found in the RRset cache. However, it is -expired, so the cache removed it and is going to pretend nothing was found. - - - - -CACHE_RRSET_INIT initializing RRset cache for %1 RRsets of class %2 - -Debug message. The RRset cache to hold at most this many RRsets for the given -class is being created. - - - - -CACHE_RRSET_LOOKUP looking up %1/%2/%3 in RRset cache - -Debug message. The resolver is trying to look up data in the RRset cache. - - - - -CACHE_RRSET_NOT_FOUND no RRset found for %1/%2/%3 in cache - -Debug message which can follow CACHE_RRSET_LOOKUP. This means the data is not -in the cache. - - - - -CACHE_RRSET_REMOVE_OLD removing old RRset for %1/%2/%3 to make space for new one - -Debug message which can follow CACHE_RRSET_UPDATE. During the update, the cache -removed an old instance of the RRset to replace it with the new one. - - - - -CACHE_RRSET_UNTRUSTED not replacing old RRset for %1/%2/%3, it has higher trust level - -Debug message which can follow CACHE_RRSET_UPDATE. The cache already holds the -same RRset, but from more trusted source, so the old one is kept and new one -ignored. - - - - -CACHE_RRSET_UPDATE updating RRset %1/%2/%3 in the cache - -Debug message. The RRset is updating its data with this given RRset. - - - - -CC_ASYNC_READ_FAILED asynchronous read failed - -This marks a low level error, we tried to read data from the message queue -daemon asynchronously, but the ASIO library returned an error. - - - - -CC_CONN_ERROR error connecting to message queue (%1) - -It is impossible to reach the message queue daemon for the reason given. It -is unlikely there'll be reason for whatever program this currently is to -continue running, as the communication with the rest of BIND 10 is vital -for the components. - - - - -CC_DISCONNECT disconnecting from message queue daemon - -The library is disconnecting from the message queue daemon. This debug message -indicates that the program is trying to shut down gracefully. - - - - -CC_ESTABLISH trying to establish connection with message queue daemon at %1 - -This debug message indicates that the command channel library is about to -connect to the message queue daemon, which should be listening on the UNIX-domain -socket listed in the output. - - - - -CC_ESTABLISHED successfully connected to message queue daemon - -This debug message indicates that the connection was successfully made, this -should follow CC_ESTABLISH. - - - - -CC_GROUP_RECEIVE trying to receive a message - -Debug message, noting that a message is expected to come over the command -channel. - - - - -CC_GROUP_RECEIVED message arrived ('%1', '%2') - -Debug message, noting that we successfully received a message (its envelope and -payload listed). This follows CC_GROUP_RECEIVE, but might happen some time -later, depending if we waited for it or just polled. - - - - -CC_GROUP_SEND sending message '%1' to group '%2' - -Debug message, we're about to send a message over the command channel. - - - - -CC_INVALID_LENGTHS invalid length parameters (%1, %2) - -This happens when garbage comes over the command channel or some kind of -confusion happens in the program. The data received from the socket make no -sense if we interpret it as lengths of message. The first one is total length -of the message; the second is the length of the header. The header -and its length (2 bytes) is counted in the total length. - - - - -CC_LENGTH_NOT_READY length not ready - -There should be data representing the length of message on the socket, but it -is not there. - - - - -CC_NO_MESSAGE no message ready to be received yet - -The program polled for incoming messages, but there was no message waiting. -This is a debug message which may happen only after CC_GROUP_RECEIVE. - - - - -CC_NO_MSGQ unable to connect to message queue (%1) - -It isn't possible to connect to the message queue daemon, for reason listed. -It is unlikely any program will be able continue without the communication. - - - - -CC_READ_ERROR error reading data from command channel (%1) - -A low level error happened when the library tried to read data from the -command channel socket. The reason is listed. - - - - -CC_READ_EXCEPTION error reading data from command channel (%1) - -We received an exception while trying to read data from the command -channel socket. The reason is listed. - - - - -CC_REPLY replying to message from '%1' with '%2' - -Debug message, noting we're sending a response to the original message -with the given envelope. - - - - -CC_SET_TIMEOUT setting timeout to %1ms - -Debug message. A timeout for which the program is willing to wait for a reply -is being set. - - - - -CC_START_READ starting asynchronous read - -Debug message. From now on, when a message (or command) comes, it'll wake the -program and the library will automatically pass it over to correct place. - - - - -CC_SUBSCRIBE subscribing to communication group %1 - -Debug message. The program wants to receive messages addressed to this group. - - - - -CC_TIMEOUT timeout reading data from command channel - -The program waited too long for data from the command channel (usually when it -sent a query to different program and it didn't answer for whatever reason). - - - - -CC_UNSUBSCRIBE unsubscribing from communication group %1 - -Debug message. The program no longer wants to receive messages addressed to -this group. - - - - -CC_WRITE_ERROR error writing data to command channel (%1) - -A low level error happened when the library tried to write data to the command -channel socket. - - - - -CC_ZERO_LENGTH invalid message length (0) - -The library received a message length being zero, which makes no sense, since -all messages must contain at least the envelope. - - - - -CFGMGR_AUTOMATIC_CONFIG_DATABASE_UPDATE Updating configuration database from version %1 to %2 - -An older version of the configuration database has been found, from which -there was an automatic upgrade path to the current version. These changes -are now applied, and no action from the administrator is necessary. - - - - -CFGMGR_BAD_UPDATE_RESPONSE_FROM_MODULE Unable to parse response from module %1: %2 - -The configuration manager sent a configuration update to a module, but -the module responded with an answer that could not be parsed. The answer -message appears to be invalid JSON data, or not decodable to a string. -This is likely to be a problem in the module in question. The update is -assumed to have failed, and will not be stored. - - - - -CFGMGR_CC_SESSION_ERROR Error connecting to command channel: %1 - -The configuration manager daemon was unable to connect to the messaging -system. The most likely cause is that msgq is not running. - - - - -CFGMGR_DATA_READ_ERROR error reading configuration database from disk: %1 - -There was a problem reading the persistent configuration data as stored -on disk. The file may be corrupted, or it is of a version from where -there is no automatic upgrade path. The file needs to be repaired or -removed. The configuration manager daemon will now shut down. - - - - -CFGMGR_IOERROR_WHILE_WRITING_CONFIGURATION Unable to write configuration file; configuration not stored: %1 - -There was an IO error from the system while the configuration manager -was trying to write the configuration database to disk. The specific -error is given. The most likely cause is that the directory where -the file is stored does not exist, or is not writable. The updated -configuration is not stored. - - - - -CFGMGR_OSERROR_WHILE_WRITING_CONFIGURATION Unable to write configuration file; configuration not stored: %1 - -There was an OS error from the system while the configuration manager -was trying to write the configuration database to disk. The specific -error is given. The most likely cause is that the system does not have -write access to the configuration database file. The updated -configuration is not stored. - - - - -CFGMGR_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down - -There was a keyboard interrupt signal to stop the cfgmgr daemon. The -daemon will now shut down. - - - - -CMDCTL_BAD_CONFIG_DATA error in config data: %1 - -There was an error reading the updated configuration data. The specific -error is printed. - - - - -CMDCTL_BAD_PASSWORD bad password for user: %1 - -A login attempt was made to b10-cmdctl, but the password was wrong. -Users can be managed with the tool b10-cmdctl-usermgr. - - - - -CMDCTL_CC_SESSION_ERROR error reading from cc channel: %1 - -There was a problem reading from the command and control channel. The -most likely cause is that the message bus daemon is not running. - - - - -CMDCTL_CC_SESSION_TIMEOUT timeout on cc channel - -A timeout occurred when waiting for essential data from the cc session. -This usually occurs when b10-cfgmgr is not running or not responding. -Since we are waiting for essential information, this is a fatal error, -and the cmdctl daemon will now shut down. - - - - -CMDCTL_COMMAND_ERROR error in command %1 to module %2: %3 - -An error was encountered sending the given command to the given module. -Either there was a communication problem with the module, or the module -was not able to process the command, and sent back an error. The -specific error is printed in the message. - - - - -CMDCTL_COMMAND_SENT command '%1' to module '%2' was sent - -This debug message indicates that the given command has been sent to -the given module. - - - - -CMDCTL_NO_SUCH_USER username not found in user database: %1 - -A login attempt was made to b10-cmdctl, but the username was not known. -Users can be added with the tool b10-cmdctl-usermgr. - - - - -CMDCTL_NO_USER_ENTRIES_READ failed to read user information, all users will be denied - -The b10-cmdctl daemon was unable to find any user data in the user -database file. Either it was unable to read the file (in which case -this message follows a message CMDCTL_USER_DATABASE_READ_ERROR -containing a specific error), or the file was empty. Users can be added -with the tool b10-cmdctl-usermgr. - - - - -CMDCTL_SEND_COMMAND sending command %1 to module %2 - -This debug message indicates that the given command is being sent to -the given module. - - - - -CMDCTL_SSL_SETUP_FAILURE_USER_DENIED failed to create an SSL connection (user denied): %1 - -The user was denied because the SSL connection could not successfully -be set up. The specific error is given in the log message. Possible -causes may be that the ssl request itself was bad, or the local key or -certificate file could not be read. - - - - -CMDCTL_STARTED cmdctl is listening for connections on %1:%2 - -The cmdctl daemon has started and is now listening for connections. - - - - -CMDCTL_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down - -There was a keyboard interrupt signal to stop the cmdctl daemon. The -daemon will now shut down. - - - - -CMDCTL_UNCAUGHT_EXCEPTION uncaught exception: %1 - -The b10-cmdctl daemon 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 message -is printed. - - - - -CMDCTL_USER_DATABASE_READ_ERROR failed to read user database file %1: %2 - -The b10-cmdctl daemon was unable to read the user database file. The -file may be unreadable for the daemon, or it may be corrupted. In the -latter case, it can be recreated with b10-cmdctl-usermgr. The specific -error is printed in the log message. - - - - -CONFIG_CCSESSION_MSG error in CC session message: %1 - -There was a problem with an incoming message on the command and control -channel. The message does not appear to be a valid command, and is -missing a required element or contains an unknown data format. This -most likely means that another BIND10 module is sending a bad message. -The message itself is ignored by this module. - - - - -CONFIG_CCSESSION_MSG_INTERNAL error handling CC session message: %1 - -There was an internal problem handling an incoming message on the command -and control channel. An unexpected exception was thrown, details of -which are appended to the message. The module will continue to run, -but will not send back an answer. - -The most likely cause of this error is a programming error. Please raise -a bug report. - - - - -CONFIG_GET_FAIL error getting configuration from cfgmgr: %1 - -The configuration manager returned an error when this module requested -the configuration. The full error message answer from the configuration -manager is appended to the log error. The most likely cause is that -the module is of a different (command specification) version than the -running configuration manager. - - - - -CONFIG_GET_FAILED error getting configuration from cfgmgr: %1 - -The configuration manager returned an error response when the module -requested its configuration. The full error message answer from the -configuration manager is appended to the log error. - - - - -CONFIG_JSON_PARSE JSON parse error in %1: %2 - -There was an error parsing the JSON file. The given file does not appear -to be in valid JSON format. Please verify that the filename is correct -and that the contents are valid JSON. - - - - -CONFIG_LOG_CONFIG_ERRORS error(s) in logging configuration: %1 - -There was a logging configuration update, but the internal validator -for logging configuration found that it contained errors. The errors -are shown, and the update is ignored. - - - - -CONFIG_LOG_EXPLICIT will use logging configuration for explicitly-named logger %1 - -This is a debug message. When processing the "loggers" part of the -configuration file, the configuration library found an entry for the named -logger that matches the logger specification for the program. The logging -configuration for the program will be updated with the information. - - - - -CONFIG_LOG_IGNORE_EXPLICIT ignoring logging configuration for explicitly-named logger %1 - -This is a debug message. When processing the "loggers" part of the -configuration file, the configuration library found an entry for the -named logger. As this does not match the logger specification for the -program, it has been ignored. - - - - -CONFIG_LOG_IGNORE_WILD ignoring logging configuration for wildcard logger %1 - -This is a debug message. When processing the "loggers" part of the -configuration file, the configuration library found the named wildcard -entry (one containing the "*" character) that matched a logger already -matched by an explicitly named entry. The configuration is ignored. - - - - -CONFIG_LOG_WILD_MATCH will use logging configuration for wildcard logger %1 - -This is a debug message. When processing the "loggers" part of -the configuration file, the configuration library found the named -wildcard entry (one containing the "*" character) that matches a logger -specification in the program. The logging configuration for the program -will be updated with the information. - - - - -CONFIG_MOD_SPEC_FORMAT module specification error in %1: %2 - -The given file does not appear to be a valid specification file: details -are included in the message. Please verify that the filename is correct -and that its contents are a valid BIND10 module specification. - - - - -CONFIG_MOD_SPEC_REJECT module specification rejected by cfgmgr: %1 - -The specification file for this module was rejected by the configuration -manager. The full error message answer from the configuration manager is -appended to the log error. The most likely cause is that the module is of -a different (specification file) version than the running configuration -manager. - - - - -CONFIG_OPEN_FAIL error opening %1: %2 - -There was an error opening the given file. The reason for the failure -is included in the message. - - - - -DATASRC_CACHE_CREATE creating the hotspot cache - -This is a debug message issued during startup when the hotspot cache -is created. - - - - -DATASRC_CACHE_DESTROY destroying the hotspot cache - -Debug information. The hotspot cache is being destroyed. - - - - -DATASRC_CACHE_DISABLE disabling the hotspot cache - -A debug message issued when the hotspot cache is disabled. - - - - -DATASRC_CACHE_ENABLE enabling the hotspot cache - -A debug message issued when the hotspot cache is enabled. - - - - -DATASRC_CACHE_EXPIRED item '%1' in the hotspot cache has expired - -A debug message issued when a hotspot cache lookup located the item but it -had expired. The item was removed and the program proceeded as if the item -had not been found. - - - - -DATASRC_CACHE_FOUND the item '%1' was found - -Debug information. An item was successfully located in the hotspot cache. - - - - -DATASRC_CACHE_FULL hotspot cache is full, dropping oldest - -Debug information. After inserting an item into the hotspot cache, the -maximum number of items was exceeded, so the least recently used item will -be dropped. This should be directly followed by CACHE_REMOVE. - - - - -DATASRC_CACHE_INSERT inserting item '%1' into the hotspot cache - -A debug message indicating that a new item is being inserted into the hotspot -cache. - - - - -DATASRC_CACHE_NOT_FOUND the item '%1' was not found in the hotspot cache - -A debug message issued when hotspot cache was searched for the specified -item but it was not found. - - - - -DATASRC_CACHE_OLD_FOUND older instance of hotspot cache item '%1' found, replacing - -Debug information. While inserting an item into the hotspot cache, an older -instance of an item with the same name was found; the old instance will be -removed. This will be directly followed by CACHE_REMOVE. - - - - -DATASRC_CACHE_REMOVE removing '%1' from the hotspot cache - -Debug information. An item is being removed from the hotspot cache. - - - - -DATASRC_CACHE_SLOTS setting the hotspot cache size to '%1', dropping '%2' items - -The maximum allowed number of items of the hotspot cache is set to the given -number. If there are too many, some of them will be dropped. The size of 0 -means no limit. - - - - -DATASRC_DATABASE_COVER_NSEC_UNSUPPORTED %1 doesn't support DNSSEC when asked for NSEC data covering %2 - -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. - - - - -DATASRC_DATABASE_FIND_RECORDS looking in datasource %1 for record %2/%3/%4 - -Debug information. The database data source is looking up records with the given -name and type in the database. - - - - -DATASRC_DATABASE_FIND_TTL_MISMATCH TTL values differ in %1 for elements of %2/%3/%4, setting to %5 - -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. - - - - -DATASRC_DATABASE_FOUND_ANY search in datasource %1 resulted in returning all records of %2 - -The data returned by the database backend contained data for the given domain -name, so all the RRsets of the domain are returned. - - - - -DATASRC_DATABASE_FOUND_CNAME search in datasource %1 for %2/%3/%4 found CNAME, resulting in %5 - -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.) - - - - -DATASRC_DATABASE_FOUND_DELEGATION Found delegation at %2 in %1 - -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. - - - - -DATASRC_DATABASE_FOUND_DELEGATION_EXACT search in datasource %1 for %2/%3/%4 found delegation at %5 - -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. - - - - -DATASRC_DATABASE_FOUND_DNAME Found DNAME at %2 in %1 - -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. - - - - -DATASRC_DATABASE_FOUND_EMPTY_NONTERMINAL empty non-terminal %2 in %1 - -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. - - - - -DATASRC_DATABASE_FOUND_NXDOMAIN search in datasource %1 resulted in NXDOMAIN for %2/%3/%4 - -The data returned by the database backend did not contain any data for the given -domain name, class and type. - - - - -DATASRC_DATABASE_FOUND_NXRRSET search in datasource %1 for %2/%3/%4 resulted in NXRRSET - -The data returned by the database backend contained data for the given domain -name and class, but not for the given type. - - - - -DATASRC_DATABASE_FOUND_NXRRSET_NSEC search in datasource %1 for %2/%3/%4 resulted in RRset %5 - -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. - - - - -DATASRC_DATABASE_FOUND_RRSET search in datasource %1 resulted in RRset %5 - -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. - - - - -DATASRC_DATABASE_ITERATE iterating zone %1 - -The program is reading the whole zone, eg. not searching for data, but going -through each of the RRsets there. - - - - -DATASRC_DATABASE_ITERATE_END iterating zone finished - -While iterating through the zone, the program reached end of the data. - - - - -DATASRC_DATABASE_ITERATE_NEXT next RRset in zone is %1/%2 - -While iterating through the zone, the program extracted next RRset from it. -The name and RRtype of the RRset is indicated in the message. - - - - -DATASRC_DATABASE_ITERATE_TTL_MISMATCH TTL values differ for RRs of %1/%2/%3, setting to %4 - -While iterating through the zone, the time to live for RRs of the given RRset -were found to be different. 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. - - - - -DATASRC_DATABASE_JOURNALREADER_END %1/%2 on %3 from %4 to %5 - -This is a debug message indicating that the program (successfully) -reaches the end of sequences of a zone's differences. The zone's name -and class, database name, and the start and end serials are shown in -the message. - - - - -DATASRC_DATABASE_JOURNALREADER_NEXT %1/%2 in %3/%4 on %5 - -This is a debug message indicating that the program retrieves one -difference in difference sequences of a zone and successfully converts -it to an RRset. The zone's name and class, database name, and the -name and RR type of the retrieved diff are shown in the message. - - - - -DATASRC_DATABASE_JOURNALREADER_START %1/%2 on %3 from %4 to %5 - -This is a debug message indicating that the program starts reading -a zone's difference sequences from a database-based data source. The -zone's name and class, database name, and the start and end serials -are shown in the message. - - - - -DATASRC_DATABASE_JOURNALREADR_BADDATA failed to convert a diff to RRset in %1/%2 on %3 between %4 and %5: %6 - -This is an error message indicating that a zone's diff is broken and -the data source library failed to convert it to a valid RRset. The -most likely cause of this is that someone has manually modified the -zone's diff in the database and inserted invalid data as a result. -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. - - - - -DATASRC_DATABASE_NO_MATCH not match for %2/%3/%4 in %1 - -No match (not even a wildcard) was found in the named data source for the given -name/type/class in the data source. - - - - -DATASRC_DATABASE_UPDATER_COMMIT updates committed for '%1/%2' on %3 - -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. - - - - -DATASRC_DATABASE_UPDATER_COMMIT (1) updates committed for '%1/%2' on %3 - -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. - - - - -DATASRC_DATABASE_UPDATER_CREATED zone updater created for '%1/%2' on %3 - -Debug information. A zone updater object is created to make updates to -the shown zone on the shown backend database. - - - - -DATASRC_DATABASE_UPDATER_CREATED (1) zone updater created for '%1/%2' on %3 - -Debug information. A zone updater object is created to make updates to -the shown zone on the shown backend database. - - - - -DATASRC_DATABASE_UPDATER_DESTROYED zone updater destroyed for '%1/%2' on %3 - -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. - - - - -DATASRC_DATABASE_UPDATER_DESTROYED (1) zone updater destroyed for '%1/%2' on %3 - -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. - - - - -DATASRC_DATABASE_UPDATER_ROLLBACK zone updates roll-backed for '%1/%2' on %3 - -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. - - - - -DATASRC_DATABASE_UPDATER_ROLLBACK (1) zone updates roll-backed for '%1/%2' on %3 - -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. - - - - -DATASRC_DATABASE_UPDATER_ROLLBACKFAIL failed to roll back zone updates for '%1/%2' on %3: %4 - -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. - - - - -DATASRC_DATABASE_UPDATER_ROLLBACKFAIL (1) failed to roll back zone updates for '%1/%2' on %3: %4 - -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. - - - - -DATASRC_DATABASE_WILDCARD_ANY search in datasource %1 resulted in wildcard match type ANY on %2 - -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. - - - - -DATASRC_DATABASE_WILDCARD_CANCEL_NS canceled wildcard match on %3 because %2 contains NS (data source %1) - -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 -instead. - - - - -DATASRC_DATABASE_WILDCARD_CANCEL_SUB wildcard %2 can't be used to construct %3 because %4 exists in %1 - -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). - - - - -DATASRC_DATABASE_WILDCARD_CNAME search in datasource %1 for %2/%3/%4 found wildcard CNAME at %5, resulting in %6 - -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. - - - - -DATASRC_DATABASE_WILDCARD_EMPTY found subdomains of %2 which is a wildcard match for %3 in %1 - -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. - - - - -DATASRC_DATABASE_WILDCARD_MATCH search in datasource %1 resulted in wildcard match at %5 with RRset %6 - -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. - - - - -DATASRC_DATABASE_WILDCARD_NS search in datasource %1 for %2/%3/%4 found wildcard delegation at %5, resulting in %6 - -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. - - - - -DATASRC_DATABASE_WILDCARD_NXRRSET search in datasource %1 for %2/%3/%4 resulted in wildcard NXRRSET at %5 - -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. - - - - -DATASRC_DO_QUERY handling query for '%1/%2' - -A debug message indicating that a query for the given name and RR type is being -processed. - - - - -DATASRC_MEM_ADD_RRSET adding RRset '%1/%2' into zone '%3' - -Debug information. An RRset is being added to the in-memory data source. - - - - -DATASRC_MEM_ADD_WILDCARD adding wildcards for '%1' - -This is a debug message issued during the processing of a wildcard -name. The internal domain name tree is scanned and some nodes are -specially marked to allow the wildcard lookup to succeed. - - - - -DATASRC_MEM_ADD_ZONE adding zone '%1/%2' - -Debug information. A zone is being added into the in-memory data source. - - - - -DATASRC_MEM_ANY_SUCCESS ANY query for '%1' successful - -Debug information. The domain was found and an ANY type query is being answered -by providing everything found inside the domain. - - - - -DATASRC_MEM_CNAME CNAME at the domain '%1' - -Debug information. The requested domain is an alias to a different domain, -returning the CNAME instead. - - - - -DATASRC_MEM_CNAME_COEXIST can't add data to CNAME in domain '%1' - -This is the same problem as in MEM_CNAME_TO_NONEMPTY, but it happened the -other way around -- adding some other data to CNAME. - - - - -DATASRC_MEM_CNAME_TO_NONEMPTY can't add CNAME to domain with other data in '%1' - -Someone or something tried to add a CNAME into a domain that already contains -some other data. But the protocol forbids coexistence of CNAME with anything -(RFC 1034, section 3.6.2). This indicates a problem with provided data. - - - - -DATASRC_MEM_CREATE creating zone '%1' in '%2' class - -Debug information. A representation of a zone for the in-memory data source is -being created. - - - - -DATASRC_MEM_DELEG_FOUND delegation found at '%1' - -Debug information. A delegation point was found above the requested record. - - - - -DATASRC_MEM_DESTROY destroying zone '%1' in '%2' class - -Debug information. A zone from in-memory data source is being destroyed. - - - - -DATASRC_MEM_DNAME_ENCOUNTERED encountered a DNAME - -Debug information. While searching for the requested domain, a DNAME was -encountered on the way. This may lead to redirection to a different domain and -stop the search. - - - - -DATASRC_MEM_DNAME_FOUND DNAME found at '%1' - -Debug information. A DNAME was found instead of the requested information. - - - - -DATASRC_MEM_DNAME_NS DNAME and NS can't coexist in non-apex domain '%1' - -A request was made for DNAME and NS records to be put into the same -domain which is not the apex (the top of the zone). This is forbidden -by RFC 2672 (section 3) and indicates a problem with provided data. - - - - -DATASRC_MEM_DOMAIN_EMPTY requested domain '%1' is empty - -Debug information. The requested domain exists in the tree of domains, but -it is empty. Therefore it doesn't contain the requested resource type. - - - - -DATASRC_MEM_DUP_RRSET duplicate RRset '%1/%2' - -An RRset is being inserted into in-memory data source for a second time. The -original version must be removed first. Note that loading master files where an -RRset is split into multiple locations is not supported yet. - - - - -DATASRC_MEM_EXACT_DELEGATION delegation at the exact domain '%1' - -Debug information. There's a NS record at the requested domain. This means -this zone is not authoritative for the requested domain, but a delegation -should be followed. The requested domain is an apex of some zone. - - - - -DATASRC_MEM_FIND find '%1/%2' - -Debug information. A search for the requested RRset is being started. - - - - -DATASRC_MEM_FIND_ZONE looking for zone '%1' - -Debug information. A zone object for this zone is being searched for in the -in-memory data source. - - - - -DATASRC_MEM_LOAD loading zone '%1' from file '%2' - -Debug information. The content of master file is being loaded into the memory. - - - - -DATASRC_MEM_NOT_FOUND requested domain '%1' not found - -Debug information. The requested domain does not exist. - - - - -DATASRC_MEM_NS_ENCOUNTERED encountered a NS - -Debug information. While searching for the requested domain, a NS was -encountered on the way (a delegation). This may lead to stop of the search. - - - - -DATASRC_MEM_NXRRSET no such type '%1' at '%2' - -Debug information. The domain exists, but it doesn't hold any record of the -requested type. - - - - -DATASRC_MEM_OUT_OF_ZONE domain '%1' doesn't belong to zone '%2' - -It was attempted to add the domain into a zone that shouldn't have it -(eg. the domain is not subdomain of the zone origin). This indicates a -problem with provided data. - - - - -DATASRC_MEM_RENAME renaming RRset from '%1' to '%2' - -Debug information. A RRset is being generated from a different RRset (most -probably a wildcard). So it must be renamed to whatever the user asked for. In -fact, it's impossible to rename RRsets with our libraries, so a new one is -created and all resource records are copied over. - - - - -DATASRC_MEM_SINGLETON trying to add multiple RRs for domain '%1' and type '%2' - -Some resource types are singletons -- only one is allowed in a domain -(for example CNAME or SOA). This indicates a problem with provided data. - - - - -DATASRC_MEM_SUCCESS query for '%1/%2' successful - -Debug information. The requested record was found. - - - - -DATASRC_MEM_SUPER_STOP stopped at superdomain '%1', domain '%2' is empty - -Debug information. The search stopped at a superdomain of the requested -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). - - - - -DATASRC_MEM_SWAP swapping contents of two zone representations ('%1' and '%2') - -Debug information. The contents of two in-memory zones are being exchanged. -This is usual practice to do some manipulation in exception-safe manner -- the -new data are prepared in a different zone object and when it works, they are -swapped. The old one contains the new data and the other one can be safely -destroyed. - - - - -DATASRC_MEM_WILDCARD_CANCEL wildcard match canceled for '%1' - -Debug information. A domain above wildcard was reached, but there's something -below the requested domain. Therefore the wildcard doesn't apply here. This -behaviour is specified by RFC 1034, section 4.3.3 - - - - -DATASRC_MEM_WILDCARD_DNAME DNAME record in wildcard domain '%1' - -The software refuses to load DNAME records into a wildcard domain. It isn't -explicitly forbidden, but the protocol is ambiguous about how this should -behave and BIND 9 refuses that as well. Please describe your intention using -different tools. - - - - -DATASRC_MEM_WILDCARD_NS NS record in wildcard domain '%1' - -The software refuses to load NS records into a wildcard domain. It isn't -explicitly forbidden, but the protocol is ambiguous about how this should -behave and BIND 9 refuses that as well. Please describe your intention using -different tools. - - - - -DATASRC_META_ADD adding a data source into meta data source - -This is a debug message issued during startup or reconfiguration. -Another data source is being added into the meta data source. - - - - -DATASRC_META_ADD_CLASS_MISMATCH mismatch between classes '%1' and '%2' - -It was attempted to add a data source into a meta data source, but their -classes do not match. - - - - -DATASRC_META_REMOVE removing data source from meta data source - -Debug information. A data source is being removed from meta data source. - - - - -DATASRC_QUERY_ADD_NSEC adding NSEC record for '%1' - -Debug information. A NSEC record covering this zone is being added. - - - - -DATASRC_QUERY_ADD_NSEC3 adding NSEC3 record of zone '%1' - -Debug information. A NSEC3 record for the given zone is being added to the -response message. - - - - -DATASRC_QUERY_ADD_RRSET adding RRset '%1/%2' to message - -Debug information. An RRset is being added to the response message. - - - - -DATASRC_QUERY_ADD_SOA adding SOA of '%1' - -Debug information. A SOA record of the given zone is being added to the -authority section of the response message. - - - - -DATASRC_QUERY_AUTH_FAIL the underlying data source failed with %1 - -The underlying data source failed to answer the authoritative query. 1 means -some error, 2 is not implemented. The data source should have logged the -specific error already. - - - - -DATASRC_QUERY_BAD_REFERRAL bad referral to '%1' - -The domain lives in another zone. But it is not possible to generate referral -information for it. - - - - -DATASRC_QUERY_CACHED data for %1/%2 found in hotspot cache - -Debug information. The requested data were found in the hotspot cache, so -no query is sent to the real data source. - - - - -DATASRC_QUERY_CHECK_CACHE checking hotspot cache for '%1/%2' - -Debug information. While processing a query, lookup to the hotspot cache -is being made. - - - - -DATASRC_QUERY_COPY_AUTH copying authoritative section into message - -Debug information. The whole referral information is being copied into the -response message. - - - - -DATASRC_QUERY_DELEGATION looking for delegation on the path to '%1' - -Debug information. The software is trying to identify delegation points on the -way down to the given domain. - - - - -DATASRC_QUERY_EMPTY_CNAME CNAME at '%1' is empty - -A CNAME chain was being followed and an entry was found that pointed -to a domain name that had no RRsets associated with it. As a result, -the query cannot be answered. This indicates a problem with supplied data. - - - - -DATASRC_QUERY_EMPTY_DNAME the DNAME on '%1' is empty - -During an attempt to synthesize CNAME from this DNAME it was discovered the -DNAME is empty (it has no records). This indicates problem with supplied data. - - - - -DATASRC_QUERY_FAIL query failed - -Some subtask of query processing failed. The reason should have been reported -already and a SERVFAIL will be returned to the querying system. - - - - -DATASRC_QUERY_FOLLOW_CNAME following CNAME at '%1' - -Debug information. The domain is a CNAME (or a DNAME and a CNAME for it -has already been created) and the search is following this chain. - - - - -DATASRC_QUERY_GET_MX_ADDITIONAL addition of A/AAAA for '%1' requested by MX '%2' - -Debug information. While processing a query, a MX record was met. It -references the mentioned address, so A/AAAA records for it are looked up -and put it into the additional section. - - - - -DATASRC_QUERY_GET_NS_ADDITIONAL addition of A/AAAA for '%1' requested by NS '%2' - -Debug information. While processing a query, a NS record was met. It -references the mentioned address, so A/AAAA records for it are looked up -and put it into the additional section. - - - - -DATASRC_QUERY_GLUE_FAIL the underlying data source failed with %1 - -The underlying data source failed to answer the glue query. 1 means some error, -2 is not implemented. The data source should have logged the specific error -already. - - - - -DATASRC_QUERY_INVALID_OP invalid query operation requested - -This indicates a programmer error. The DO_QUERY was called with unknown -operation code. - - - - -DATASRC_QUERY_IS_AUTH auth query (%1/%2) - -Debug information. The last DO_QUERY is an auth query. - - - - -DATASRC_QUERY_IS_GLUE glue query (%1/%2) - -Debug information. The last DO_QUERY is a query for glue addresses. - - - - -DATASRC_QUERY_IS_NOGLUE query for non-glue addresses (%1/%2) - -Debug information. The last DO_QUERY is a query for addresses that are not -glue. - - - - -DATASRC_QUERY_IS_REF query for referral (%1/%2) - -Debug information. The last DO_QUERY is a query for referral information. - - - - -DATASRC_QUERY_IS_SIMPLE simple query (%1/%2) - -Debug information. The last DO_QUERY is a simple query. - - - - -DATASRC_QUERY_MISPLACED_TASK task of this type should not be here - -This indicates a programming error. A task was found in the internal task -queue, but this kind of task wasn't designed to be inside the queue (it should -be handled right away, not queued). - - - - -DATASRC_QUERY_MISSING_NS missing NS records for '%1' - -NS records should have been put into the authority section. However, this zone -has none. This indicates problem with provided data. - - - - -DATASRC_QUERY_MISSING_SOA the zone '%1' has no SOA - -The answer should have been a negative one (eg. of nonexistence of something). -To do so, a SOA record should be put into the authority section, but the zone -does not have one. This indicates problem with provided data. - - - - -DATASRC_QUERY_NOGLUE_FAIL the underlying data source failed with %1 - -The underlying data source failed to answer the no-glue query. 1 means some -error, 2 is not implemented. The data source should have logged the specific -error already. - - - - -DATASRC_QUERY_NO_CACHE_ANY_AUTH ignoring hotspot cache for ANY query (%1/%2 in %3 class) - -Debug information. The hotspot cache is ignored for authoritative ANY queries -for consistency reasons. - - - - -DATASRC_QUERY_NO_CACHE_ANY_SIMPLE ignoring hotspot cache for ANY query (%1/%2 in %3 class) - -Debug information. The hotspot cache is ignored for ANY queries for consistency -reasons. - - - - -DATASRC_QUERY_NO_DS_NSEC there's no DS record in the '%1' zone - -An attempt to add a NSEC record into the message failed, because the zone does -not have any DS record. This indicates problem with the provided data. - - - - -DATASRC_QUERY_NO_DS_NSEC3 there's no DS record in the '%1' zone - -An attempt to add a NSEC3 record into the message failed, because the zone does -not have any DS record. This indicates problem with the provided data. - - - - -DATASRC_QUERY_NO_ZONE no zone containing '%1' in class '%2' - -Lookup of domain failed because the data have no zone that contain the -domain. Maybe someone sent a query to the wrong server for some reason. - - - - -DATASRC_QUERY_PROCESS processing query '%1/%2' in the '%3' class - -Debug information. A sure query is being processed now. - - - - -DATASRC_QUERY_PROVE_NX_FAIL unable to prove nonexistence of '%1' - -The user wants DNSSEC and we discovered the entity doesn't exist (either -domain or the record). But there was an error getting NSEC/NSEC3 record -to prove the nonexistence. - - - - -DATASRC_QUERY_REF_FAIL the underlying data source failed with %1 - -The underlying data source failed to answer the query for referral information. -1 means some error, 2 is not implemented. The data source should have logged -the specific error already. - - - - -DATASRC_QUERY_RRSIG unable to answer RRSIG query - -The server is unable to answer a direct query for RRSIG type, but was asked -to do so. - - - - -DATASRC_QUERY_SIMPLE_FAIL the underlying data source failed with %1 - -The underlying data source failed to answer the simple query. 1 means some -error, 2 is not implemented. The data source should have logged the specific -error already. - - - - -DATASRC_QUERY_SYNTH_CNAME synthesizing CNAME from DNAME on '%1' - -This is a debug message. While answering a query, a DNAME was encountered. The -DNAME itself will be returned, along with a synthesized CNAME for clients that -do not understand the DNAME RR. - - - - -DATASRC_QUERY_TASK_FAIL task failed with %1 - -The query subtask failed. The reason should have been reported by the subtask -already. The code is 1 for error, 2 for not implemented. - - - - -DATASRC_QUERY_TOO_MANY_CNAMES CNAME chain limit exceeded at '%1' - -A CNAME led to another CNAME and it led to another, and so on. After 16 -CNAMEs, the software gave up. Long CNAME chains are discouraged, and this -might possibly be a loop as well. Note that some of the CNAMEs might have -been synthesized from DNAMEs. This indicates problem with supplied data. - - - - -DATASRC_QUERY_UNKNOWN_RESULT unknown result of subtask - -This indicates a programmer error. The answer of subtask doesn't look like -anything known. - - - - -DATASRC_QUERY_WILDCARD looking for a wildcard covering '%1' - -Debug information. A direct match wasn't found, so a wildcard covering the -domain is being looked for now. - - - - -DATASRC_QUERY_WILDCARD_FAIL error processing wildcard for '%1' - -During an attempt to cover the domain by a wildcard an error happened. The -exact kind was hopefully already reported. - - - - -DATASRC_QUERY_WILDCARD_PROVE_NX_FAIL unable to prove nonexistence of '%1' (%2) - -While processing a wildcard, it wasn't possible to prove nonexistence of the -given domain or record. The code is 1 for error and 2 for not implemented. - - - - -DATASRC_QUERY_WILDCARD_REFERRAL unable to find referral info for '%1' (%2) - -While processing a wildcard, a referral was met. But it wasn't possible to get -enough information for it. The code is 1 for error, 2 for not implemented. - - - - -DATASRC_SQLITE_CLOSE closing SQLite database - -Debug information. The SQLite data source is closing the database file. - - - - -DATASRC_SQLITE_CONNCLOSE Closing sqlite database - -The database file is no longer needed and is being closed. - - - - -DATASRC_SQLITE_CONNOPEN Opening sqlite database file '%1' - -The database file is being opened so it can start providing data. - - - - -DATASRC_SQLITE_CREATE SQLite data source created - -Debug information. An instance of SQLite data source is being created. - - - - -DATASRC_SQLITE_DESTROY SQLite data source destroyed - -Debug information. An instance of SQLite data source is being destroyed. - - - - -DATASRC_SQLITE_DROPCONN SQLite3Database is being deinitialized - -The object around a database connection is being destroyed. - - - - -DATASRC_SQLITE_ENCLOSURE looking for zone containing '%1' - -Debug information. The SQLite data source is trying to identify which zone -should hold this domain. - - - - -DATASRC_SQLITE_ENCLOSURE_NOT_FOUND no zone contains '%1' - -Debug information. The last SQLITE_ENCLOSURE query was unsuccessful; there's -no such zone in our data. - - - - -DATASRC_SQLITE_FIND looking for RRset '%1/%2' - -Debug information. The SQLite data source is looking up a resource record -set. - - - - -DATASRC_SQLITE_FINDADDRS looking for A/AAAA addresses for '%1' - -Debug information. The data source is looking up the addresses for given -domain name. - - - - -DATASRC_SQLITE_FINDADDRS_BAD_CLASS class mismatch looking for addresses ('%1' and '%2') - -The SQLite data source was looking up A/AAAA addresses, but the data source -contains different class than the query was for. - - - - -DATASRC_SQLITE_FINDEXACT looking for exact RRset '%1/%2' - -Debug information. The SQLite data source is looking up an exact resource -record. - - - - -DATASRC_SQLITE_FINDEXACT_BAD_CLASS class mismatch looking for an RRset ('%1' and '%2') - -The SQLite data source was looking up an exact RRset, but the data source -contains different class than the query was for. - - - - -DATASRC_SQLITE_FINDREC looking for record '%1/%2' - -Debug information. The SQLite data source is looking up records of given name -and type in the database. - - - - -DATASRC_SQLITE_FINDREF looking for referral at '%1' - -Debug information. The SQLite data source is identifying if this domain is -a referral and where it goes. - - - - -DATASRC_SQLITE_FINDREF_BAD_CLASS class mismatch looking for referral ('%1' and '%2') - -The SQLite data source was trying to identify if there's a referral. But -it contains different class than the query was for. - - - - -DATASRC_SQLITE_FIND_BAD_CLASS class mismatch looking for an RRset ('%1' and '%2') - -The SQLite data source was looking up an RRset, but the data source contains -different class than the query was for. - - - - -DATASRC_SQLITE_FIND_NSEC3 looking for NSEC3 in zone '%1' for hash '%2' - -Debug information. We're trying to look up a NSEC3 record in the SQLite data -source. - - - - -DATASRC_SQLITE_FIND_NSEC3_NO_ZONE no such zone '%1' - -The SQLite data source was asked to provide a NSEC3 record for given zone. -But it doesn't contain that zone. - - - - -DATASRC_SQLITE_NEWCONN SQLite3Database is being initialized - -A wrapper object to hold database connection is being initialized. - - - - -DATASRC_SQLITE_OPEN opening SQLite database '%1' - -Debug information. The SQLite data source is loading an SQLite database in -the provided file. - - - - -DATASRC_SQLITE_PREVIOUS looking for name previous to '%1' - -This is a debug message. The name given was not found, so the program -is searching for the next name higher up the hierarchy (e.g. if -www.example.com were queried for and not found, the software searches -for the "previous" name, example.com). - - - - -DATASRC_SQLITE_PREVIOUS_NO_ZONE no zone containing '%1' - -The name given was not found, so the program is searching for the next -name higher up the hierarchy (e.g. if www.example.com were queried -for and not found, the software searches for the "previous" name, -example.com). However, this name is not contained in any zone in the -data source. This is an error since it indicates a problem in the earlier -processing of the query. - - - - -DATASRC_SQLITE_SETUP setting up SQLite database - -The database for SQLite data source was found empty. It is assumed this is the -first run and it is being initialized with current schema. It'll still contain -no data, but it will be ready for use. - - - - -DATASRC_STATIC_CLASS_NOT_CH static data source can handle CH class only - -An error message indicating that a query requesting a RR for a class other -that CH was sent to the static data source (which only handles CH queries). - - - - -DATASRC_STATIC_CREATE creating the static datasource - -Debug information. The static data source (the one holding stuff like -version.bind) is being created. - - - - -DATASRC_STATIC_FIND looking for '%1/%2' - -Debug information. This resource record set is being looked up in the static -data source. - - - - -DATASRC_UNEXPECTED_QUERY_STATE unexpected query state - -This indicates a programming error. An internal task of unknown type was -generated. - - - - -DDNS_CC_SESSION_ERROR error reading from cc channel: %1 - -There was a problem reading from the command and control channel. The -most likely cause is that the msgq process is not running. - - - - -DDNS_CC_SESSION_TIMEOUT_ERROR timeout waiting for cc response - -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. - - - - -DDNS_CONFIG_ERROR error found in configuration data: %1 - -The ddns process encountered an error when installing the configuration at -startup time. Details of the error are included in the log message. - - - - -DDNS_MODULECC_SESSION_ERROR error encountered by configuration/command module: %1 - -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. - - - - -DDNS_RECEIVED_SHUTDOWN_COMMAND shutdown command received - -The ddns process received a shutdown command from the command channel -and will now shut down. - - - - -DDNS_RUNNING ddns server is running and listening for updates - -The ddns process has successfully started and is now ready to receive commands -and updates. - - - - -DDNS_SHUTDOWN ddns server shutting down - -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. - - - - -DDNS_STOPPED ddns server has stopped - -The ddns process has successfully stopped and is no longer listening for or -handling commands or updates, and will now exit. - - - - -DDNS_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down - -There was a keyboard interrupt signal to stop the ddns process. The -process will now shut down. - - - - -DDNS_UNCAUGHT_EXCEPTION uncaught exception of type %1: %2 - -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. - - - - -LIBXFRIN_DIFFERENT_TTL multiple data with different TTLs (%1, %2) on %3/%4/%5. Adjusting %2 -> %1. - -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 latter one gets overwritten to the earlier one in the sequence. - - - - -LIBXFRIN_NO_JOURNAL disabled journaling for updates to %1 on %2 - -An attempt was made to create a Diff object with journaling enabled, but -the underlying data source didn't support journaling (while still allowing -updates) and so the created object has it disabled. At a higher level this -means that the updates will be applied to the zone but subsequent IXFR requests -will result in a full zone transfer (i.e., an AXFR-style IXFR). Unless the -overhead of the full transfer is an issue this message can be ignored; -otherwise you may want to check why the journaling wasn't allowed on the -data source and either fix the issue or use a different type of data source. - - - - -LOGIMPL_ABOVE_MAX_DEBUG debug level of %1 is too high and will be set to the maximum of %2 - -A message from the interface to the underlying logger implementation reporting -that the debug level (as set by an internally-created string DEBUGn, where n -is an integer, e.g. DEBUG22) is above the maximum allowed value and has -been reduced to that value. The appearance of this message may indicate -a programming error - please submit a bug report. - - - - -LOGIMPL_BAD_DEBUG_STRING debug string '%1' has invalid format - -A message from the interface to the underlying logger implementation -reporting that an internally-created string used to set the debug level -is not of the correct format (it should be of the form DEBUGn, where n -is an integer, e.g. DEBUG22). The appearance of this message indicates -a programming error - please submit a bug report. - - - - -LOGIMPL_BELOW_MIN_DEBUG debug level of %1 is too low and will be set to the minimum of %2 - -A message from the interface to the underlying logger implementation reporting -that the debug level (as set by an internally-created string DEBUGn, where n -is an integer, e.g. DEBUG22) is below the minimum allowed value and has -been increased to that value. The appearance of this message may indicate -a programming error - please submit a bug report. - - - - -LOG_BAD_DESTINATION unrecognized log destination: %1 - -A logger destination value was given that was not recognized. The -destination should be one of "console", "file", or "syslog". - - - - -LOG_BAD_SEVERITY unrecognized log severity: %1 - -A logger severity value was given that was not recognized. The severity -should be one of "DEBUG", "INFO", "WARN", "ERROR", "FATAL" or "NONE". - - - - -LOG_BAD_STREAM bad log console output stream: %1 - -Logging has been configured so that output is written to the terminal -(console) but the stream on which it is to be written is not recognised. -Allowed values are "stdout" and "stderr". - - - - -LOG_DUPLICATE_MESSAGE_ID duplicate message ID (%1) in compiled code - -During start-up, BIND 10 detected that the given message identification -had been defined multiple times in the BIND 10 code. This indicates a -programming error; please submit a bug report. - - - - -LOG_DUPLICATE_NAMESPACE line %1: duplicate $NAMESPACE directive found - -When reading a message file, more than one $NAMESPACE directive was found. -(This directive is used to set a C++ namespace when generating header -files during software development.) Such a condition is regarded as an -error and the read will be abandoned. - - - - -LOG_INPUT_OPEN_FAIL unable to open message file %1 for input: %2 - -The program was not able to open the specified input message file for -the reason given. - - - - -LOG_INVALID_MESSAGE_ID line %1: invalid message identification '%2' - -An invalid message identification (ID) has been found during the read of -a message file. Message IDs should comprise only alphanumeric characters -and the underscore, and should not start with a digit. - - - - -LOG_NAMESPACE_EXTRA_ARGS line %1: $NAMESPACE directive has too many arguments - -The $NAMESPACE directive in a message file takes a single argument, a -namespace in which all the generated symbol names are placed. This error -is generated when the compiler finds a $NAMESPACE directive with more -than one argument. - - - - -LOG_NAMESPACE_INVALID_ARG line %1: $NAMESPACE directive has an invalid argument ('%2') - -The $NAMESPACE argument in a message file should be a valid C++ namespace. -This message is output if the simple check on the syntax of the string -carried out by the reader fails. - - - - -LOG_NAMESPACE_NO_ARGS line %1: no arguments were given to the $NAMESPACE directive - -The $NAMESPACE directive in a message file takes a single argument, -a C++ namespace in which all the generated symbol names are placed. -This error is generated when the compiler finds a $NAMESPACE directive -with no arguments. - - - - -LOG_NO_MESSAGE_ID line %1: message definition line found without a message ID - -Within a message file, message are defined by lines starting with a "%". -The rest of the line should comprise the message ID and text describing -the message. This error indicates the message compiler found a line in -the message file comprising just the "%" and nothing else. - - - - -LOG_NO_MESSAGE_TEXT line %1: line found containing a message ID ('%2') and no text - -Within a message file, message are defined by lines starting with a "%". -The rest of the line should comprise the message ID and text describing -the message. This error indicates the message compiler found a line -in the message file comprising just the "%" and message identification, -but no text. - - - - -LOG_NO_SUCH_MESSAGE could not replace message text for '%1': no such message - -During start-up a local message file was read. A line with the listed -message identification was found in the file, but the identification is -not one contained in the compiled-in message dictionary. This message -may appear a number of times in the file, once for every such unknown -message identification. - -There may be several reasons why this message may appear: - -- The message ID has been mis-spelled in the local message file. - -- The program outputting the message may not use that particular message -(e.g. it originates in a module not used by the program.) - -- The local file was written for an earlier version of the BIND 10 software -and the later version no longer generates that message. - -Whatever the reason, there is no impact on the operation of BIND 10. - - - - -LOG_OPEN_OUTPUT_FAIL unable to open %1 for output: %2 - -Originating within the logging code, the program was not able to open -the specified output file for the reason given. - - - - -LOG_PREFIX_EXTRA_ARGS line %1: $PREFIX directive has too many arguments - -Within a message file, the $PREFIX directive takes a single argument, -a prefix to be added to the symbol names when a C++ file is created. -This error is generated when the compiler finds a $PREFIX directive with -more than one argument. - -Note: the $PREFIX directive is deprecated and will be removed in a future -version of BIND 10. - - - - -LOG_PREFIX_INVALID_ARG line %1: $PREFIX directive has an invalid argument ('%2') - -Within a message file, the $PREFIX directive takes a single argument, -a prefix to be added to the symbol names when a C++ file is created. -As such, it must adhere to restrictions on C++ symbol names (e.g. may -only contain alphanumeric characters or underscores, and may nor start -with a digit). A $PREFIX directive was found with an argument (given -in the message) that violates those restrictions. - -Note: the $PREFIX directive is deprecated and will be removed in a future -version of BIND 10. - - - - -LOG_READING_LOCAL_FILE reading local message file %1 - -This is an informational message output by BIND 10 when it starts to read -a local message file. (A local message file may replace the text of -one of more messages; the ID of the message will not be changed though.) - - - - -LOG_READ_ERROR error reading from message file %1: %2 - -The specified error was encountered reading from the named message file. - - - - -LOG_UNRECOGNISED_DIRECTIVE line %1: unrecognised directive '%2' - -Within a message file, a line starting with a dollar symbol was found -(indicating the presence of a directive) but the first word on the line -(shown in the message) was not recognised. - - - - -LOG_WRITE_ERROR error writing to %1: %2 - -The specified error was encountered by the message compiler when writing -to the named output file. - - - - -NOTIFY_OUT_DATASRC_ACCESS_FAILURE failed to get access to data source: %1 - -notify_out failed to get access to one of configured data sources. -Detailed error is shown in the log message. This can be either a -configuration error or installation setup failure. - - - - -NOTIFY_OUT_DATASRC_ZONE_NOT_FOUND Zone %1 is not found - -notify_out attempted to get slave information of a zone but the zone -isn't found in the expected data source. This shouldn't happen, -because notify_out first identifies a list of available zones before -this process. So this means some critical inconsistency in the data -source or software bug. - - - - -NOTIFY_OUT_INVALID_ADDRESS invalid address %1#%2: %3 - -The notify_out library tried to send a notify message to the given -address, but it appears to be an invalid address. The configuration -for secondary nameservers might contain a typographic error, or a -different BIND 10 module has forgotten to validate its data before -sending this module a notify command. As such, this should normally -not happen, and points to an oversight in a different module. - - - - -NOTIFY_OUT_REPLY_BAD_OPCODE bad opcode in notify reply from %1#%2: %3 - -The notify_out library sent a notify message to the nameserver at -the given address, but the response did not have the opcode set to -NOTIFY. The opcode in the response is printed. Since there was a -response, no more notifies will be sent to this server for this -notification event. - - - - -NOTIFY_OUT_REPLY_BAD_QID bad QID in notify reply from %1#%2: got %3, should be %4 - -The notify_out library sent a notify message to the nameserver at -the given address, but the query id in the response does not match -the one we sent. Since there was a response, no more notifies will -be sent to this server for this notification event. - - - - -NOTIFY_OUT_REPLY_BAD_QUERY_NAME bad query name in notify reply from %1#%2: got %3, should be %4 - -The notify_out library sent a notify message to the nameserver at -the given address, but the query name in the response does not match -the one we sent. Since there was a response, no more notifies will -be sent to this server for this notification event. - - - - -NOTIFY_OUT_REPLY_QR_NOT_SET QR flags set to 0 in reply to notify from %1#%2 - -The notify_out library sent a notify message to the namesever at the -given address, but the reply did not have the QR bit set to one. -Since there was a response, no more notifies will be sent to this -server for this notification event. - - - - -NOTIFY_OUT_REPLY_UNCAUGHT_EXCEPTION uncaught exception: %1 - -There was an uncaught exception in the handling of a notify reply -message, either in the message parser, or while trying to extract data -from the parsed message. The error is printed, and notify_out will -treat the response as a bad message, but this does point to a -programming error, since all exceptions should have been caught -explicitly. Please file a bug report. Since there was a response, -no more notifies will be sent to this server for this notification -event. - - - - -NOTIFY_OUT_RETRY_EXCEEDED notify to %1#%2: number of retries (%3) exceeded - -The maximum number of retries for the notify target has been exceeded. -Either the address of the secondary nameserver is wrong, or it is not -responding. - - - - -NOTIFY_OUT_SENDING_NOTIFY sending notify to %1#%2 - -A notify message is sent to the secondary nameserver at the given -address. - - - - -NOTIFY_OUT_SOCKET_ERROR socket error sending notify to %1#%2: %3 - -There was a network error while trying to send a notify message to -the given address. The address might be unreachable. The socket -error is printed and should provide more information. - - - - -NOTIFY_OUT_SOCKET_RECV_ERROR socket error reading notify reply from %1#%2: %3 - -There was a network error while trying to read a notify reply -message from the given address. The socket error is printed and should -provide more information. - - - - -NOTIFY_OUT_TIMEOUT retry notify to %1#%2 - -The notify message to the given address (noted as address#port) has -timed out, and the message will be resent until the max retry limit -is reached. - - - - -NOTIFY_OUT_ZONE_BAD_SOA Zone %1 is invalid in terms of SOA - -This is a warning issued when the notify_out module finds a zone that -doesn't have an SOA RR or has multiple SOA RRs. Notify message won't -be sent to such a zone. - - - - -NOTIFY_OUT_ZONE_NO_NS Zone %1 doesn't have NS RR - -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. - - - - -NSAS_EMPTY_RESPONSE response to query for %1 returned an empty answer section - -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. - - - - -NSAS_ERROR_RESPONSE error response of %1 returned in query for %2 - -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. - - - - -NSAS_FIND_NS_ADDRESS asking resolver to obtain A and AAAA records for %1 - -A debug message issued when the NSAS (nameserver address store - part -of the resolver) is making a callback into the resolver to retrieve the -address records for the specified nameserver. - - - - -NSAS_FOUND_ADDRESS found address %1 for %2 - -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. - - - - -NSAS_LOOKUP_CANCEL lookup for zone %1 has been canceled - -A debug message issued when an NSAS (nameserver address store - part of -the resolver) lookup for a zone has been canceled. - - - - -NSAS_NS_LOOKUP_FAIL failed to lookup any %1 for %2 - -A debug message issued when the NSAS (nameserver address store - part of -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. - - - - -NSAS_NULL_RESPONSE got null message in success callback for query for %1 - -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. - -This message indicates an internal error in the NSAS. Please raise a -bug report. - - - - -NSAS_SEARCH_ZONE_NS searching NSAS for nameservers for zone %1 - -A debug message output when a call is made to the NSAS (nameserver -address store - part of the resolver) to obtain the nameservers for -the specified zone. - - - - -NSAS_UPDATE_RTT update RTT for %1: was %2 ms, is now %3 ms - -A NSAS (nameserver address store - part of the resolver) debug message -reporting the update of a round-trip time (RTT) for a query made to the -specified nameserver. The RTT has been updated using the value given -and the new RTT is displayed. (The RTT is subject to a calculation that -damps out sudden changes. As a result, the new RTT used by the NSAS in -future decisions of which nameserver to use is not necessarily equal to -the RTT reported.) - - - - -NSAS_WRONG_ANSWER queried for %1 RR of type/class %2/%3, received response %4/%5 - -A NSAS (nameserver address store - part of the resolver) made a query for -a resource record of a particular type and class, but instead received -an answer with a different given type and class. - -This message indicates an internal error in the NSAS. Please raise a -bug report. - - - - -RESLIB_ANSWER answer received in response to query for <%1> - -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. - - - - -RESLIB_CNAME CNAME received in response to query for <%1> - -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. - - - - -RESLIB_DEEPEST did not find <%1> in cache, deepest delegation found is %2 - -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. - - - - -RESLIB_EMPTY_RESPONSE empty response received to query for <%1> - -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. - - - - -RESLIB_ERROR_RESPONSE unspecified error received in response to query for <%1> - -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. - - - - -RESLIB_EXTRADATA_RESPONSE extra data in response to query for <%1> - -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. - - - - -RESLIB_FOLLOW_CNAME following CNAME chain to <%1> - -A debug message, a CNAME response was received and another query is -being issued for the <name, class, type> tuple. - - - - -RESLIB_INVALID_NAMECLASS_RESPONSE invalid name or class in response to query for <%1> - -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. - - - - -RESLIB_INVALID_QNAME_RESPONSE invalid name or class in response to query for <%1> - -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. - - - - -RESLIB_INVALID_TYPE_RESPONSE invalid name or class in response to query for <%1> - -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. - - - - -RESLIB_LONG_CHAIN CNAME received in response to query for <%1>: CNAME chain length exceeded - -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. - - - - -RESLIB_MULTIPLE_CLASS_RESPONSE response to query for <%1> contained multiple RRsets with different classes - -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. - - - - -RESLIB_NOTSINGLE_RESPONSE response to query for <%1> was not a response - -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. - - - - -RESLIB_NOT_ONE_QNAME_RESPONSE not one question in response to query for <%1> - -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. - - - - -RESLIB_NOT_RESPONSE response to query for <%1> was not a response - -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. - - - - -RESLIB_NO_NS_RRSET no NS RRSet in referral response received to query for <%1> - -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 -not contain any NS RRsets. This may indicate a programming error in the -response classification code. - - - - -RESLIB_NSAS_LOOKUP looking up nameserver for zone %1 in the NSAS - -A debug message, the RunningQuery object is querying the NSAS for the -nameservers for the specified zone. - - - - -RESLIB_NXDOM_NXRR NXDOMAIN/NXRRSET received in response to query for <%1> - -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. - - - - -RESLIB_OPCODE_RESPONSE response to query for <%1> did not have query opcode - -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. - - - - -RESLIB_PROTOCOL protocol error in answer for %1: %3 - -A debug message indicating that a protocol error was received. As there -are no retries left, an error will be reported. - - - - -RESLIB_PROTOCOL_RETRY protocol error in answer for %1: %2 (retries left: %3) - -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. - - - - -RESLIB_RCODE_ERROR response to query for <%1> returns RCODE of %2 - -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. - - - - -RESLIB_RECQ_CACHE_FIND found <%1> in the cache (resolve() instance %2) - -This is a debug message and indicates that a RecursiveQuery object found the -the specified <name, class, type> tuple in the cache. The instance number -at the end of the message indicates which of the two resolve() methods has -been called. - - - - -RESLIB_RECQ_CACHE_NO_FIND did not find <%1> in the cache, starting RunningQuery (resolve() instance %2) - -This is a debug message and indicates that the look in the cache made by the -RecursiveQuery::resolve() method did not find an answer, so a new RunningQuery -object has been created to resolve the question. The instance number at -the end of the message indicates which of the two resolve() methods has -been called. - - - - -RESLIB_REFERRAL referral received in response to query for <%1> - -A debug message recording that a referral 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. - - - - -RESLIB_REFER_ZONE referred to zone %1 - -A debug message indicating that the last referral message was to the specified -zone. - - - - -RESLIB_RESOLVE asked to resolve <%1> (resolve() instance %2) - -A debug message, the RecursiveQuery::resolve method has been called to resolve -the specified <name, class, type> tuple. The first action will be to lookup -the specified tuple in the cache. The instance number at the end of the -message indicates which of the two resolve() methods has been called. - - - - -RESLIB_RRSET_FOUND found single RRset in the cache when querying for <%1> (resolve() instance %2) - -A debug message, indicating that when RecursiveQuery::resolve queried the -cache, a single RRset was found which was put in the answer. The instance -number at the end of the message indicates which of the two resolve() -methods has been called. - - - - -RESLIB_RTT round-trip time of last query calculated as %1 ms - -A debug message giving the round-trip time of the last query and response. - - - - -RESLIB_RUNQ_CACHE_FIND found <%1> in the cache - -This is a debug message and indicates that a RunningQuery object found -the specified <name, class, type> tuple in the cache. - - - - -RESLIB_RUNQ_CACHE_LOOKUP looking up up <%1> in the cache - -This is a debug message and indicates that a RunningQuery object has made -a call to its doLookup() method to look up the specified <name, class, type> -tuple, the first action of which will be to examine the cache. - - - - -RESLIB_RUNQ_FAIL failure callback - nameservers are unreachable - -A debug message indicating that a RunningQuery's failure callback has been -called because all nameservers for the zone in question are unreachable. - - - - -RESLIB_RUNQ_SUCCESS success callback - sending query to %1 - -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. - - - - -RESLIB_TCP_TRUNCATED TCP response to query for %1 was truncated - -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. - - - - -RESLIB_TEST_SERVER setting test server to %1(%2) - -This is a warning message only generated in unit tests. It indicates -that all upstream queries from the resolver are being routed to the -specified server, regardless of the address of the nameserver to which -the query would normally be routed. If seen during normal operation, -please submit a bug report. - - - - -RESLIB_TEST_UPSTREAM sending upstream query for <%1> to test server at %2 - -This is a debug message and should only be seen in unit tests. A query for -the specified <name, class, type> tuple is being sent to a test nameserver -whose address is given in the message. - - - - -RESLIB_TIMEOUT query <%1> to %2 timed out - -A debug message indicating that the specified upstream query has timed out and -there are no retries left. - - - - -RESLIB_TIMEOUT_RETRY query <%1> to %2 timed out, re-trying (retries left: %3) - -A debug message indicating that the specified query has timed out 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. - - - - -RESLIB_TRUNCATED response to query for <%1> was truncated, re-querying over TCP - -A debug message, this indicates that the response to the specified query was -truncated and that the resolver will be re-querying over TCP. There are -various reasons why responses may be truncated, so this message is normal and -gives no cause for concern. - - - - -RESLIB_UPSTREAM sending upstream query for <%1> to %2 - -A debug message indicating that a query for the specified <name, class, type> -tuple is being sent to a nameserver whose address is given in the message. - - - - -RESOLVER_AXFR_TCP AXFR request received over TCP - -This is a debug message output when the resolver received a request for -an AXFR (full transfer of a zone) over TCP. Only authoritative servers -are able to handle AXFR requests, so the resolver will return an error -message to the sender with the RCODE set to NOTIMP. - - - - -RESOLVER_AXFR_UDP AXFR request received over UDP - -This is a debug message output when the resolver received a request for -an AXFR (full transfer of a zone) over UDP. Only authoritative servers -are able to handle AXFR requests (and in any case, an AXFR request should -be sent over TCP), so the resolver will return an error message to the -sender with the RCODE set to NOTIMP. - - - - -RESOLVER_CLIENT_TIME_SMALL client timeout of %1 is too small - -During the update of the resolver's configuration parameters, the value -of the client timeout was found to be too small. The configuration -update was abandoned and the parameters were not changed. - - - - -RESOLVER_CONFIG_CHANNEL configuration channel created - -This is a debug message output when the resolver has successfully -established a connection to the configuration channel. - - - - -RESOLVER_CONFIG_ERROR error in configuration: %1 - -An error was detected in a configuration update received by the -resolver. This may be in the format of the configuration message (in -which case this is a programming error) or it may be in the data supplied -(in which case it is a user error). The reason for the error, included -in the message, will give more details. The configuration update is -not applied and the resolver parameters were not changed. - - - - -RESOLVER_CONFIG_LOADED configuration loaded - -This is a debug message output when the resolver configuration has been -successfully loaded. - - - - -RESOLVER_CONFIG_UPDATED configuration updated: %1 - -This is a debug message output when the resolver configuration is being -updated with the specified information. - - - - -RESOLVER_CREATED main resolver object created - -This is a debug message indicating that the main resolver object has -been created. - - - - -RESOLVER_DNS_MESSAGE_RECEIVED DNS message received: %1 - -This is a debug message from the resolver listing the contents of a -received DNS message. - - - - -RESOLVER_DNS_MESSAGE_SENT DNS message of %1 bytes sent: %2 - -This is a debug message containing details of the response returned by -the resolver to the querying system. - - - - -RESOLVER_FAILED resolver failed, reason: %1 - -This is an error message output when an unhandled exception is caught -by the resolver. After this, the resolver will shut itself down. -Please submit a bug report. - - - - -RESOLVER_FORWARD_ADDRESS setting forward address %1(%2) - -If the resolver is running in forward mode, this message will appear -during startup to list the forward address. If multiple addresses are -specified, it will appear once for each address. - - - - -RESOLVER_FORWARD_QUERY processing forward query - -This is a debug message indicating that a query received by the resolver -has passed a set of checks (message is well-formed, it is allowed by the -ACL, it is a supported opcode, etc.) and is being forwarded to upstream -servers. - - - - -RESOLVER_HEADER_ERROR message received, exception when processing header: %1 - -This is a debug message from the resolver noting that an exception -occurred during the processing of a received packet. The packet has -been dropped. - - - - -RESOLVER_IXFR IXFR request received - -This is a debug message indicating that the resolver received a request -for an IXFR (incremental transfer of a zone). Only authoritative servers -are able to handle IXFR requests, so the resolver will return an error -message to the sender with the RCODE set to NOTIMP. - - - - -RESOLVER_LOOKUP_TIME_SMALL lookup timeout of %1 is too small - -During the update of the resolver's configuration parameters, the value -of the lookup timeout was found to be too small. The configuration -update will not be applied. - - - - -RESOLVER_MESSAGE_ERROR error parsing received message: %1 - returning %2 - -This is a debug message noting that parsing of the body of a received -message by the resolver failed due to some error (although the parsing of -the header succeeded). The message parameters give a textual description -of the problem and the RCODE returned. - - - - -RESOLVER_NEGATIVE_RETRIES negative number of retries (%1) specified in the configuration - -This error is issued when a resolver configuration update has specified -a negative retry count: only zero or positive values are valid. The -configuration update was abandoned and the parameters were not changed. - - - - -RESOLVER_NON_IN_PACKET non-IN class request received, returning REFUSED message - -This debug message is issued when resolver has received a DNS packet that -was not IN (Internet) class. The resolver cannot handle such packets, -so is returning a REFUSED response to the sender. - - - - -RESOLVER_NORMAL_QUERY processing normal query - -This is a debug message indicating that the query received by the resolver -has passed a set of checks (message is well-formed, it is allowed by the -ACL, it is a supported opcode, etc.) and is being processed by the resolver. - - - - -RESOLVER_NOTIFY_RECEIVED NOTIFY arrived but server is not authoritative - -The resolver has received a NOTIFY message. As the server is not -authoritative it cannot process it, so it returns an error message to -the sender with the RCODE set to NOTAUTH. - - - - -RESOLVER_NOT_ONE_QUESTION query contained %1 questions, exactly one question was expected - -This debug message indicates that the resolver received a query that -contained the number of entries in the question section detailed in -the message. This is a malformed message, as a DNS query must contain -only one question. The resolver will return a message to the sender -with the RCODE set to FORMERR. - - - - -RESOLVER_NO_ROOT_ADDRESS no root addresses available - -A warning message issued during resolver startup, this indicates that -no root addresses have been set. This may be because the resolver will -get them from a priming query. - - - - -RESOLVER_PARSE_ERROR error parsing received message: %1 - returning %2 - -This is a debug message noting that the resolver received a message and -the parsing of the body of the message failed due to some non-protocol -related reason (although the parsing of the header succeeded). -The message parameters give a textual description of the problem and -the RCODE returned. - - - - -RESOLVER_PRINT_COMMAND print message command, arguments are: %1 - -This debug message is logged when a "print_message" command is received -by the resolver over the command channel. - - - - -RESOLVER_PROTOCOL_ERROR protocol error parsing received message: %1 - returning %2 - -This is a debug message noting that the resolver received a message and -the parsing of the body of the message failed due to some protocol error -(although the parsing of the header succeeded). The message parameters -give a textual description of the problem and the RCODE returned. - - - - -RESOLVER_QUERY_ACCEPTED query accepted: '%1/%2/%3' from %4 - -This debug message is produced by the resolver when an incoming query -is accepted in terms of the query ACL. The log message shows the query -in the form of <query name>/<query type>/<query class>, and the client -that sends the query in the form of <Source IP address>#<source port>. - - - - -RESOLVER_QUERY_DROPPED query dropped: '%1/%2/%3' from %4 - -This is an informational message that indicates an incoming query has -been dropped by the resolver because of the query ACL. Unlike the -RESOLVER_QUERY_REJECTED case, the server does not return any response. -The log message shows the query in the form of <query name>/<query -type>/<query class>, and the client that sends the query in the form of -<Source IP address>#<source port>. - - - - -RESOLVER_QUERY_REJECTED query rejected: '%1/%2/%3' from %4 - -This is an informational message that indicates an incoming query has -been rejected by the resolver because of the query ACL. This results -in a response with an RCODE of REFUSED. The log message shows the query -in the form of <query name>/<query type>/<query class>, and the client -that sends the query in the form of <Source IP address>#<source port>. - - - - -RESOLVER_QUERY_SETUP query setup - -This is a debug message noting that the resolver is creating a -RecursiveQuery object. - - - - -RESOLVER_QUERY_SHUTDOWN query shutdown - -This is a debug message noting that the resolver is destroying a -RecursiveQuery object. - - - - -RESOLVER_QUERY_TIME_SMALL query timeout of %1 is too small - -During the update of the resolver's configuration parameters, the value -of the query timeout was found to be too small. The configuration -parameters were not changed. - - - - -RESOLVER_RECEIVED_MESSAGE resolver has received a DNS message - -This is a debug message indicating that the resolver has received a -DNS message. Depending on the debug settings, subsequent log output -will indicate the nature of the message. - - - - -RESOLVER_RECURSIVE running in recursive mode - -This is an informational message that appears at startup noting that -the resolver is running in recursive mode. - - - - -RESOLVER_SERVICE_CREATED service object created - -This debug message is output when resolver creates the main service object -(which handles the received queries). - - - - -RESOLVER_SET_PARAMS query timeout: %1, client timeout: %2, lookup timeout: %3, retry count: %4 - -This debug message lists the parameters being set for the resolver. These are: -query timeout: the timeout (in ms) used for queries originated by the resolver -to upstream servers. Client timeout: the interval to resolve a query by -a client: after this time, the resolver sends back a SERVFAIL to the client -whilst continuing to resolve the query. Lookup timeout: the time at which the -resolver gives up trying to resolve a query. Retry count: the number of times -the resolver will retry a query to an upstream server if it gets a timeout. - -The client and lookup timeouts require a bit more explanation. The -resolution of the client query might require a large number of queries to -upstream nameservers. Even if none of these queries timeout, the total time -taken to perform all the queries may exceed the client timeout. When this -happens, a SERVFAIL is returned to the client, but the resolver continues -with the resolution process; data received is added to the cache. However, -there comes a time - the lookup timeout - when even the resolver gives up. -At this point it will wait for pending upstream queries to complete or -timeout and drop the query. - - - - -RESOLVER_SET_QUERY_ACL query ACL is configured - -This debug message is generated when a new query ACL is configured for -the resolver. - - - - -RESOLVER_SET_ROOT_ADDRESS setting root address %1(%2) - -This message gives the address of one of the root servers used by the -resolver. It is output during startup and may appear multiple times, -once for each root server address. - - - - -RESOLVER_SHUTDOWN resolver shutdown complete - -This informational message is output when the resolver has shut down. - - - - -RESOLVER_STARTED resolver started - -This informational message is output by the resolver when all initialization -has been completed and it is entering its main loop. - - - - -RESOLVER_STARTING starting resolver with command line '%1' - -An informational message, this is output when the resolver starts up. - - - - -RESOLVER_UNEXPECTED_RESPONSE received unexpected response, ignoring - -This is a debug message noting that the resolver received a DNS response -packet on the port on which is it listening for queries. The packet -has been ignored. - - - - -RESOLVER_UNSUPPORTED_OPCODE opcode %1 not supported by the resolver - -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. - - - - -SOCKETREQUESTOR_CREATED Socket requestor created - -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. - - - - -SOCKETREQUESTOR_DESTROYED Socket requestor destoryed - -Debug message. The socket requestor created at SOCKETREQUESTOR_CREATED -has been destroyed. This event is generally unexpected other than in -test cases. - - - - -SOCKETREQUESTOR_GETSOCKET Received a %1 socket for [%2]:%3, FD=%4, token=%5, path=%6 - -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. - - - - -SOCKETREQUESTOR_RELEASESOCKET Released a socket of token %1 - -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. - - - - -SRVCOMM_ADDRESSES_NOT_LIST the address and port specification is not a list in %1 - -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. - - - - -SRVCOMM_ADDRESS_FAIL failed to listen on addresses (%1) - -The server failed to bind to one of the address/port pair it should according -to configuration, for reason listed in the message (usually because that pair -is already used by other service or missing privileges). The server will try -to recover and bind the address/port pairs it was listening to before (if any). - - - - -SRVCOMM_ADDRESS_MISSING address specification is missing "address" or "port" element in %1 - -This points to an error in configuration. An address specification in the -configuration is missing either an address or port and so cannot be used. The -specification causing the error is given in the message. - - - - -SRVCOMM_ADDRESS_TYPE address specification type is invalid in %1 - -This points to an error in configuration. An address specification in the -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). - - - - -SRVCOMM_ADDRESS_UNRECOVERABLE failed to recover original addresses also (%1) - -The recovery of old addresses after SRVCOMM_ADDRESS_FAIL also failed for -the reason listed. - -The condition indicates problems with the server and/or the system on -which it is running. The server will continue running to allow -reconfiguration, but will not be listening on any address or port until -an administrator does so. - - - - -SRVCOMM_ADDRESS_VALUE address to set: %1#%2 - -Debug message. This lists one address and port value of the set of -addresses we are going to listen on (eg. there will be one log message -per pair). This appears only after SRVCOMM_SET_LISTEN, but might -be hidden, as it has higher debug level. - - - - -SRVCOMM_KEYS_DEINIT deinitializing TSIG keyring - -Debug message indicating that the server is deinitializing the TSIG keyring. - - - - -SRVCOMM_KEYS_INIT initializing TSIG keyring - -Debug message indicating that the server is initializing the global TSIG -keyring. This should be seen only at server start. - - - - -SRVCOMM_KEYS_UPDATE updating TSIG keyring - -Debug message indicating new keyring is being loaded from configuration (either -on startup or as a result of configuration update). - - - - -SRVCOMM_PORT_RANGE port out of valid range (%1 in %2) - -This points to an error in configuration. The port in an address -specification is outside the valid range of 0 to 65535. - - - - -SRVCOMM_SET_LISTEN setting addresses to listen to - -Debug message, noting that the server is about to start listening on a -different set of IP addresses and ports than before. - - - - -STATHTTPD_BAD_OPTION_VALUE bad command line argument: %1 - -The stats-httpd module was called with a bad command-line argument -and will not start. - - - - -STATHTTPD_CC_SESSION_ERROR error connecting to message bus: %1 - -The stats-httpd module was unable to connect to the BIND 10 command -and control bus. A likely problem is that the message bus daemon -(b10-msgq) is not running. The stats-httpd module will now shut down. - - - - -STATHTTPD_CLOSING closing %1#%2 - -The stats-httpd daemon will stop listening for requests on the given -address and port number. - - - - -STATHTTPD_CLOSING_CC_SESSION stopping cc session - -Debug message indicating that the stats-httpd module is disconnecting -from the command and control bus. - - - - -STATHTTPD_HANDLE_CONFIG reading configuration: %1 - -The stats-httpd daemon has received new configuration data and will now -process it. The (changed) data is printed. - - - - -STATHTTPD_RECEIVED_SHUTDOWN_COMMAND shutdown command received - -A shutdown command was sent to the stats-httpd module, and it will -now shut down. - - - - -STATHTTPD_RECEIVED_STATUS_COMMAND received command to return status - -A status command was sent to the stats-httpd module, and it will -respond with 'Stats Httpd is up.' and its PID. - - - - -STATHTTPD_RECEIVED_UNKNOWN_COMMAND received unknown command: %1 - -An unknown command has been sent to the stats-httpd module. The -stats-httpd module will respond with an error, and the command will -be ignored. - - - - -STATHTTPD_SERVER_DATAERROR HTTP server data error: %1 - -An internal error occurred while handling an HTTP request. An HTTP 404 -response will be sent back, and the specific error is printed. This -is an error condition that likely points the specified data -corresponding to the requested URI is incorrect. - - - - -STATHTTPD_SERVER_ERROR HTTP server error: %1 - -An internal error occurred while handling an HTTP request. An HTTP 500 -response will be sent back, and the specific error is printed. This -is an error condition that likely points to a module that is not -responding correctly to statistic requests. - - - - -STATHTTPD_SERVER_INIT_ERROR HTTP server initialization error: %1 - -There was a problem initializing the HTTP server in the stats-httpd -module upon receiving its configuration data. The most likely cause -is a port binding problem or a bad configuration value. The specific -error is printed in the message. The new configuration is ignored, -and an error is sent back. - - - - -STATHTTPD_SHUTDOWN shutting down - -The stats-httpd daemon is shutting down. - - - - -STATHTTPD_STARTED listening on %1#%2 - -The stats-httpd daemon will now start listening for requests on the -given address and port number. - - - - -STATHTTPD_STARTING_CC_SESSION starting cc session - -Debug message indicating that the stats-httpd module is connecting to -the command and control bus. - - - - -STATHTTPD_START_SERVER_INIT_ERROR HTTP server initialization error: %1 - -There was a problem initializing the HTTP server in the stats-httpd -module upon startup. The most likely cause is that it was not able -to bind to the listening port. The specific error is printed, and the -module will shut down. - - - - -STATHTTPD_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down - -There was a keyboard interrupt signal to stop the stats-httpd -daemon. The daemon will now shut down. - - - - -STATHTTPD_UNKNOWN_CONFIG_ITEM unknown configuration item: %1 - -The stats-httpd daemon received a configuration update from the -configuration manager. However, one of the items in the -configuration is unknown. The new configuration is ignored, and an -error is sent back. As possible cause is that there was an upgrade -problem, and the stats-httpd version is out of sync with the rest of -the system. - - - - -STATS_BAD_OPTION_VALUE bad command line argument: %1 - -The stats module was called with a bad command-line argument and will -not start. - - - - -STATS_CC_SESSION_ERROR error connecting to message bus: %1 - -The stats module was unable to connect to the BIND 10 command and -control bus. A likely problem is that the message bus daemon -(b10-msgq) is not running. The stats module will now shut down. - - - - -STATS_RECEIVED_NEW_CONFIG received new configuration: %1 - -This debug message is printed when the stats module has received a -configuration update from the configuration manager. - - - - -STATS_RECEIVED_SHOWSCHEMA_ALL_COMMAND received command to show all statistics schema - -The stats module received a command to show all statistics schemas of all modules. - - - - -STATS_RECEIVED_SHOWSCHEMA_NAME_COMMAND received command to show statistics schema for %1 - -The stats module received a command to show the specified statistics schema of the specified module. - - - - -STATS_RECEIVED_SHOW_ALL_COMMAND received command to show all statistics - -The stats module received a command to show all statistics that it has -collected. - - - - -STATS_RECEIVED_SHOW_NAME_COMMAND received command to show statistics for %1 - -The stats module received a command to show the statistics that it has -collected for the given item. - - - - -STATS_RECEIVED_SHUTDOWN_COMMAND shutdown command received - -A shutdown command was sent to the stats module and it will now shut down. - - - - -STATS_RECEIVED_STATUS_COMMAND received command to return status - -A status command was sent to the stats module. It will return a -response indicating that it is running normally. - - - - -STATS_RECEIVED_UNKNOWN_COMMAND received unknown command: %1 - -An unknown command has been sent to the stats module. The stats module -will respond with an error and the command will be ignored. - - - - -STATS_SEND_REQUEST_BOSS requesting boss to send statistics - -This debug message is printed when a request is sent to the boss module -to send its data to the stats module. - - - - -STATS_STARTING starting - -The stats module will be now starting. - - - - -STATS_START_ERROR stats module error: %1 - -An internal error occurred while starting the stats module. The stats -module will be now shutting down. - - - - -STATS_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down - -There was a keyboard interrupt signal to stop the stats module. The -daemon will now shut down. - - - - -STATS_UNKNOWN_COMMAND_IN_SPEC unknown command in specification file: %1 - -The specification file for the stats module contains a command that -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. - - - - -XFRIN_AXFR_INCONSISTENT_SOA AXFR SOAs are inconsistent for %1: %2 expected, %3 received - -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 -"same" (not only for the serial), but it is still not clear what the -receiver should do if this condition does not hold. There was a discussion -about this at the IETF dnsext wg: -http://www.ietf.org/mail-archive/web/dnsext/current/msg07908.html -and the general feeling seems that it would be better to reject the -transfer if a mismatch is detected. On the other hand, also as noted -in that email thread, neither BIND 9 nor NSD performs any comparison -on the SOAs. For now, we only check the serials (ignoring other fields) -and only leave a warning log message when a mismatch is found. If it -turns out to happen with a real world primary server implementation -and that server actually feeds broken data (e.g. mixed versions of -zone), we can consider a stricter action. - - - - -XFRIN_BAD_MASTER_ADDR_FORMAT bad format for master address: %1 - -The given master address is not a valid IP address. - - - - -XFRIN_BAD_MASTER_PORT_FORMAT bad format for master port: %1 - -The master port as read from the configuration is not a valid port number. - - - - -XFRIN_BAD_TSIG_KEY_STRING bad TSIG key string: %1 - -The TSIG key string as read from the configuration does not represent -a valid TSIG key. - - - - -XFRIN_BAD_ZONE_CLASS Invalid zone class: %1 - -The zone class as read from the configuration is not a valid DNS class. - - - - -XFRIN_CC_SESSION_ERROR error reading from cc channel: %1 - -There was a problem reading from the command and control channel. The -most likely cause is that xfrin the msgq daemon is not running. - - - - -XFRIN_COMMAND_ERROR error while executing command '%1': %2 - -There was an error while the given command was being processed. The -error is given in the log message. - - - - -XFRIN_CONNECT_MASTER error connecting to master at %1: %2 - -There was an error opening a connection to the master. The error is -shown in the log message. - - - - -XFRIN_GOT_INCREMENTAL_RESP got incremental response for %1 - -In an attempt of IXFR processing, the begenning SOA of the first difference -(following the initial SOA that specified the final SOA for all the -differences) was found. This means a connection for xfrin tried IXFR -and really aot a response for incremental updates. - - - - -XFRIN_GOT_NONINCREMENTAL_RESP got nonincremental response for %1 - -Non incremental transfer was detected at the "first data" of a transfer, -which is the RR following the initial SOA. Non incremental transfer is -either AXFR or AXFR-style IXFR. In the latter case, it means that -in a response to IXFR query the first data is not SOA or its SOA serial -is not equal to the requested SOA serial. - - - - -XFRIN_IMPORT_DNS error importing python DNS module: %1 - -There was an error importing the python DNS module pydnspp. The most -likely cause is a PYTHONPATH problem. - - - - -XFRIN_IXFR_UPTODATE IXFR requested serial for %1 is %2, master has %3, not updating - -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. - - - - -XFRIN_MSGQ_SEND_ERROR error while contacting %1 and %2 - -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 -was killed. - - - - -XFRIN_MSGQ_SEND_ERROR_ZONE_MANAGER error while contacting %1 - -There was a problem sending a message to the zone manager. This most -likely means that the msgq daemon has quit or was killed. - - - - -XFRIN_NOTIFY_UNKNOWN_MASTER got notification to retransfer zone %1 from %2, expected %3 - -The system received a notify for the given zone, but the address it came -from does not match the master address in the Xfrin configuration. The notify -is ignored. This may indicate that the configuration for the master is wrong, -that a wrong machine is sending notifies, or that fake notifies are being sent. - - - - -XFRIN_RETRANSFER_UNKNOWN_ZONE got notification to retransfer unknown zone %1 - -There was an internal command to retransfer the given zone, but the -zone is not known to the system. This may indicate that the configuration -for xfrin is incomplete, or there was a typographical error in the -zone name in the configuration. - - - - -XFRIN_STARTING starting resolver with command line '%1' - -An informational message, this is output when the resolver starts up. - - - - -XFRIN_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down - -There was a keyboard interrupt signal to stop the xfrin daemon. The -daemon will now shut down. - - - - -XFRIN_UNKNOWN_ERROR unknown error: %1 - -An uncaught exception was raised while running the xfrin daemon. The -exception message is printed in the log message. - - - - -XFRIN_XFR_OTHER_FAILURE %1 transfer of zone %2 failed: %3 - -The XFR transfer for the given zone has failed due to a problem outside -of the xfrin module. Possible reasons are a broken DNS message or failure -in database connection. The error is shown in the log message. - - - - -XFRIN_XFR_PROCESS_FAILURE %1 transfer of zone %2/%3 failed: %4 - -An XFR session failed outside the main protocol handling. This -includes an error at the data source level at the initialization -phase, unexpected failure in the network connection setup to the -master server, or even more unexpected failure due to unlikely events -such as memory allocation failure. Details of the error are shown in -the log message. In general, these errors are not really expected -ones, and indicate an installation error or a program bug. The -session handler thread tries to clean up all intermediate resources -even on these errors, but it may be incomplete. So, if this log -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. - - - - -XFRIN_XFR_TRANSFER_FAILURE %1 transfer of zone %2 with %3 failed: %4 - -The XFR transfer for the given zone has failed due to an internal error. -The error is shown in the log message. - - - - -XFRIN_XFR_TRANSFER_FALLBACK falling back from IXFR to AXFR for %1 - -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. - - - - -XFRIN_XFR_TRANSFER_PROTOCOL_ERROR %1 transfer of zone %2 with %3 failed: %4 - -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. - - - - -XFRIN_XFR_TRANSFER_STARTED %1 transfer of zone %2 started - -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. - - - - -XFRIN_XFR_TRANSFER_SUCCESS %1 transfer of zone %2 succeeded - -The XFR transfer of the given zone was successfully completed. - - - - -XFRIN_ZONE_CREATED Zone %1 not found in the given data source, newly created - -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. - - - - -XFRIN_ZONE_MULTIPLE_SOA Zone %1 has %2 SOA RRs - -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. - - - - -XFRIN_ZONE_NO_SOA Zone %1 does not have SOA - -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. - - - - -XFRIN_ZONE_SERIAL_AHEAD Serial number (%1) for %2 received from master %3 < ours (%4) - -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. - - - - -XFROUT_BAD_TSIG_KEY_STRING bad TSIG key string: %1 - -The TSIG key string as read from the configuration does not represent -a valid TSIG key. - - - - -XFROUT_CC_SESSION_ERROR error reading from cc channel: %1 - -There was a problem reading from the command and control channel. The -most likely cause is that the msgq daemon is not running. - - - - -XFROUT_CC_SESSION_TIMEOUT_ERROR timeout waiting for cc response - -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. - - - - -XFROUT_CONFIG_ERROR error found in configuration data: %1 - -The xfrout process encountered an error when installing the configuration at -startup time. Details of the error are included in the log message. - - - - -XFROUT_FETCH_REQUEST_ERROR socket error while fetching a request from the auth daemon - -There was a socket error while contacting the b10-auth daemon to -fetch a transfer request. The auth daemon may have shutdown. - - - - -XFROUT_HANDLE_QUERY_ERROR error while handling query: %1 - -There was a general error handling an xfrout query. The error is shown -in the message. In principle this error should not appear, and points -to an oversight catching exceptions in the right place. However, to -ensure the daemon keeps running, this error is caught and reported. - - - - -XFROUT_IMPORT error importing python module: %1 - -There was an error importing a python module. One of the modules needed -by xfrout could not be found. This suggests that either some libraries -are missing on the system, or the PYTHONPATH variable is not correct. -The specific place where this library needs to be depends on your -system and your specific installation. - - - - -XFROUT_IXFR_MULTIPLE_SOA IXFR client %1: authority section has multiple SOAs - -An IXFR request was received with more than one SOA RRs in the authority -section. The xfrout daemon rejects the request with an RCODE of -FORMERR. - - - - -XFROUT_IXFR_NO_JOURNAL_SUPPORT IXFR client %1, %2: journaling not supported in the data source, falling back to AXFR - -An IXFR request was received but the underlying data source did -not support journaling. The xfrout daemon fell back to AXFR-style -IXFR. - - - - -XFROUT_IXFR_NO_SOA IXFR client %1: missing SOA - -An IXFR request was received with no SOA RR in the authority section. -The xfrout daemon rejects the request with an RCODE of FORMERR. - - - - -XFROUT_IXFR_NO_VERSION IXFR client %1, %2: version (%3 to %4) not in journal, falling back to AXFR - -An IXFR request was received, but the requested range of differences -were not found in the data source. The xfrout daemon fell back to -AXFR-style IXFR. - - - - -XFROUT_IXFR_NO_ZONE IXFR client %1, %2: zone not found with journal - -The requested zone in IXFR was not found in the data source -even though the xfrout daemon sucessfully found the SOA RR of the zone -in the data source. This can happen if the administrator removed the -zone from the data source within the small duration between these -operations, but it's more likely to be a bug or broken data source. -Unless you know why this message was logged, and especially if it -happens often, it's advisable to check whether the data source is -valid for this zone. The xfrout daemon considers it a possible, -though unlikely, event, and returns a response with an RCODE of -NOTAUTH. - - - - -XFROUT_IXFR_UPTODATE IXFR client %1, %2: client version is new enough (theirs=%3, ours=%4) - -An IXFR request was received, but the client's SOA version is the same as -or newer than that of the server. The xfrout server responds to the -request with the answer section being just one SOA of that version. -Note: as of this wrting the 'newer version' cannot be identified due to -the lack of support for the serial number arithmetic. This will soon -be implemented. - - - - -XFROUT_MODULECC_SESSION_ERROR error encountered by configuration/command module: %1 - -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 xfrout -failed to start at initialization. A detailed error message from the module -will also be displayed. - - - - -XFROUT_NEW_CONFIG Update xfrout configuration - -New configuration settings have been sent from the configuration -manager. The xfrout daemon will now apply them. - - - - -XFROUT_NEW_CONFIG_DONE Update xfrout configuration done - -The xfrout daemon is now done reading the new configuration settings -received from the configuration manager. - - - - -XFROUT_NOTIFY_COMMAND received command to send notifies for %1/%2 - -The xfrout daemon received a command on the command channel that -NOTIFY packets should be sent for the given zone. - - - - -XFROUT_PARSE_QUERY_ERROR error parsing query: %1 - -There was a parse error while reading an incoming query. The parse -error is shown in the log message. A remote client sent a packet we -do not understand or support. The xfrout request will be ignored. -In general, this should only occur for unexpected problems like -memory allocation failures, as the query should already have been -parsed by the b10-auth daemon, before it was passed here. - - - - -XFROUT_PROCESS_REQUEST_ERROR error processing transfer request: %2 - -There was an error processing a transfer request. The error is included -in the log message, but at this point no specific information other -than that could be given. This points to incomplete exception handling -in the code. - - - - -XFROUT_QUERY_DROPPED %1 client %2: request to transfer %3 dropped - -The xfrout process silently dropped a request to transfer zone to -given host. This is required by the ACLs. The %2 represents the IP -address and port of the peer requesting the transfer, and the %3 -represents the zone name and class. - - - - -XFROUT_QUERY_QUOTA_EXCCEEDED %1 client %2: request denied due to quota (%3) - -The xfr request was rejected because the server was already handling -the maximum number of allowable transfers as specified in the transfers_out -configuration parameter, which is also shown in the log message. The -request was immediately responded and terminated with an RCODE of REFUSED. -This can happen for a busy xfrout server, and you may want to increase -this parameter; if the server is being too busy due to requests from -unexpected clients you may want to restrict the legitimate clients -with ACL. - - - - -XFROUT_QUERY_REJECTED %1 client %2: request to transfer %3 rejected - -The xfrout process rejected (by REFUSED rcode) a request to transfer zone to -given host. This is because of ACLs. The %2 represents the IP -address and port of the peer requesting the transfer, and the %3 -represents the zone name and class. - - - - -XFROUT_RECEIVED_SHUTDOWN_COMMAND shutdown command received - -The xfrout daemon received a shutdown command from the command channel -and will now shut down. - - - - -XFROUT_RECEIVE_FILE_DESCRIPTOR_ERROR error receiving the file descriptor for an XFR connection - -There was an error receiving the file descriptor for the transfer -request. Normally, the request is received by b10-auth, and passed on -to the xfrout daemon, so it can answer directly. However, there was a -problem receiving this file descriptor. The request will be ignored. - - - - -XFROUT_REMOVE_OLD_UNIX_SOCKET_FILE_ERROR error removing unix socket file %1: %2 - -The unix socket file xfrout needs for contact with the auth daemon -already exists, and needs to be removed first, but there is a problem -removing it. It is likely that we do not have permission to remove -this file. The specific error is show in the log message. The xfrout -daemon will shut down. - - - - -XFROUT_REMOVE_UNIX_SOCKET_FILE_ERROR error clearing unix socket file %1: %2 - -When shutting down, the xfrout daemon tried to clear the unix socket -file used for communication with the auth daemon. It failed to remove -the file. The reason for the failure is given in the error message. - - - - -XFROUT_SOCKET_SELECT_ERROR error while calling select() on request socket: %1 - -There was an error while calling select() on the socket that informs -the xfrout daemon that a new xfrout request has arrived. This should -be a result of rare local error such as memory allocation failure and -shouldn't happen under normal conditions. The error is included in the -log message. - - - - -XFROUT_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down - -There was a keyboard interrupt signal to stop the xfrout daemon. The -daemon will now shut down. - - - - -XFROUT_STOPPING the xfrout daemon is shutting down - -The current transfer is aborted, as the xfrout daemon is shutting down. - - - - -XFROUT_UNIX_SOCKET_FILE_IN_USE another xfrout process seems to be using the unix socket file %1 - -While starting up, the xfrout daemon tried to clear the unix domain -socket needed for contacting the b10-auth daemon to pass requests -on, but the file is in use. The most likely cause is that another -xfrout daemon process is still running. This xfrout daemon (the one -printing this message) will not start. - - - - -XFROUT_XFR_TRANSFER_CHECK_ERROR %1 client %2: check for transfer of %3 failed: %4 - -Pre-response check for an incomding XFR request failed unexpectedly. -The most likely cause of this is that some low level error in the data -source, but it may also be other general (more unlikely) errors such -as memory shortage. Some detail of the error is also included in the -message. The xfrout server tries to return a SERVFAIL response in this case. - - - - -XFROUT_XFR_TRANSFER_DONE %1 client %2: transfer of %3 complete - -The transfer of the given zone has been completed successfully, or was -aborted due to a shutdown event. - - - - -XFROUT_XFR_TRANSFER_ERROR %1 client %2: error transferring zone %3: %4 - -An uncaught exception was encountered while sending the response to -an AXFR query. The error message of the exception is included in the -log message, but this error most likely points to incomplete exception -handling in the code. - - - - -XFROUT_XFR_TRANSFER_FAILED %1 client %2: transfer of %3 failed, rcode: %4 - -A transfer out for the given zone failed. An error response is sent -to the client. The given rcode is the rcode that is set in the error -response. This is either NOTAUTH (we are not authoritative for the -zone), SERVFAIL (our internal database is missing the SOA record for -the zone), or REFUSED (the limit of simultaneous outgoing AXFR -transfers, as specified by the configuration value -Xfrout/max_transfers_out, has been reached). - - - - -XFROUT_XFR_TRANSFER_STARTED %1 client %2: transfer of zone %3 has started - -A transfer out of the given zone has started. - - - - -ZONEMGR_CCSESSION_ERROR command channel session error: %1 - -An error was encountered on the command channel. The message indicates -the nature of the error. - - - - -ZONEMGR_JITTER_TOO_BIG refresh_jitter is too big, setting to 0.5 - -The value specified in the configuration for the refresh jitter is too large -so its value has been set to the maximum of 0.5. - - - - -ZONEMGR_KEYBOARD_INTERRUPT exiting zonemgr process as result of keyboard interrupt - -An informational message output when the zone manager was being run at a -terminal and it was terminated via a keyboard interrupt signal. - - - - -ZONEMGR_LOAD_ZONE loading zone %1 (class %2) - -This is a debug message indicating that the zone of the specified class -is being loaded. - - - - -ZONEMGR_NO_MASTER_ADDRESS internal BIND 10 command did not contain address of master - -A command received by the zone manager from the Auth module did not -contain the address of the master server from which a NOTIFY message -was received. This may be due to an internal programming error; please -submit a bug report. - - - - -ZONEMGR_NO_SOA zone %1 (class %2) does not have an SOA record - -When loading the named zone of the specified class the zone manager -discovered that the data did not contain an SOA record. The load has -been abandoned. - - - - -ZONEMGR_NO_TIMER_THREAD trying to stop zone timer thread but it is not running - -An attempt was made to stop the timer thread (used to track when zones -should be refreshed) but it was not running. This may indicate an -internal program error. Please submit a bug report. - - - - -ZONEMGR_NO_ZONE_CLASS internal BIND 10 command did not contain class of zone - -A command received by the zone manager from another BIND 10 module did -not contain the class of the zone on which the zone manager should act. -This may be due to an internal programming error; please submit a -bug report. - - - - -ZONEMGR_NO_ZONE_NAME internal BIND 10 command did not contain name of zone - -A command received by the zone manager from another BIND 10 module did -not contain the name of the zone on which the zone manager should act. -This may be due to an internal programming error; please submit a -bug report. - - - - -ZONEMGR_RECEIVE_NOTIFY received NOTIFY command for zone %1 (class %2) - -This is a debug message indicating that the zone manager has received a -NOTIFY command over the command channel. The command is sent by the Auth -process when it is acting as a slave server for the zone and causes the -zone manager to record the master server for the zone and start a timer; -when the timer expires, the master will be polled to see if it contains -new data. - - - - -ZONEMGR_RECEIVE_SHUTDOWN received SHUTDOWN command - -This is a debug message indicating that the zone manager has received -a SHUTDOWN command over the command channel from the Boss process. -It will act on this command and shut down. - - - - -ZONEMGR_RECEIVE_UNKNOWN received unknown command '%1' - -This is a warning message indicating that the zone manager has received -the stated command over the command channel. The command is not known -to the zone manager and although the command is ignored, its receipt -may indicate an internal error. Please submit a bug report. - - - - -ZONEMGR_RECEIVE_XFRIN_FAILED received XFRIN FAILED command for zone %1 (class %2) - -This is a debug message indicating that the zone manager has received -an XFRIN FAILED command over the command channel. The command is sent -by the Xfrin process when a transfer of zone data into the system has -failed, and causes the zone manager to schedule another transfer attempt. - - - - -ZONEMGR_RECEIVE_XFRIN_SUCCESS received XFRIN SUCCESS command for zone %1 (class %2) - -This is a debug message indicating that the zone manager has received -an XFRIN SUCCESS command over the command channel. The command is sent -by the Xfrin process when the transfer of zone data into the system has -succeeded, and causes the data to be loaded and served by BIND 10. - - - - -ZONEMGR_REFRESH_ZONE refreshing zone %1 (class %2) - -The zone manager is refreshing the named zone of the specified class -with updated information. - - - - -ZONEMGR_SELECT_ERROR error with select(): %1 - -An attempt to wait for input from a socket failed. The failing operation -is a call to the operating system's select() function, which failed for -the given reason. - - - - -ZONEMGR_SEND_FAIL failed to send command to %1, session has been closed - -The zone manager attempted to send a command to the named BIND 10 module, -but the send failed. The session between the modules has been closed. - - - - -ZONEMGR_SESSION_ERROR unable to establish session to command channel daemon - -The zonemgr process was not able to be started because it could not -connect to the command channel daemon. The most usual cause of this -problem is that the daemon is not running. - - - - -ZONEMGR_SESSION_TIMEOUT timeout on session to command channel daemon - -The zonemgr process was not able to be started because it timed out when -connecting to the command channel daemon. The most usual cause of this -problem is that the daemon is not running. - - - - -ZONEMGR_SHUTDOWN zone manager has shut down - -A debug message, output when the zone manager has shut down completely. - - - - -ZONEMGR_STARTING zone manager starting - -A debug message output when the zone manager starts up. - - - - -ZONEMGR_TIMER_THREAD_RUNNING trying to start timer thread but one is already running - -This message is issued when an attempt is made to start the timer -thread (which keeps track of when zones need a refresh) but one is -already running. It indicates either an error in the program logic or -a problem with stopping a previous instance of the timer. Please submit -a bug report. - - - - -ZONEMGR_UNKNOWN_ZONE_FAIL zone %1 (class %2) is not known to the zone manager - -An XFRIN operation has failed but the zone that was the subject of the -operation is not being managed by the zone manager. This may indicate -an error in the program (as the operation should not have been initiated -if this were the case). Please submit a bug report. - - - - -ZONEMGR_UNKNOWN_ZONE_NOTIFIED notified zone %1 (class %2) is not known to the zone manager - -A NOTIFY was received but the zone that was the subject of the operation -is not being managed by the zone manager. This may indicate an error -in the program (as the operation should not have been initiated if this -were the case). Please submit a bug report. - - - - -ZONEMGR_UNKNOWN_ZONE_SUCCESS zone %1 (class %2) is not known to the zone manager - -An XFRIN operation has succeeded but the zone received is not being -managed by the zone manager. This may indicate an error in the program -(as the operation should not have been initiated if this were the case). -Please submit a bug report. - - - - - -