From: Mukund Sivaraman Date: Tue, 15 May 2012 04:53:26 +0000 (+0530) Subject: [master] Regen HTML and text versions of the guide X-Git-Tag: trac2351_base~226^2~117 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=ce461b1b1bb0bc412e92ffc41365cb86d5544736;p=thirdparty%2Fkea.git [master] Regen HTML and text versions of the guide --- diff --git a/doc/guide/bind10-guide.html b/doc/guide/bind10-guide.html index b879af5dd2..abead8b806 100644 --- a/doc/guide/bind10-guide.html +++ b/doc/guide/bind10-guide.html @@ -1,4 +1,4 @@ -BIND 10 Guide

BIND 10 Guide

Administrator Reference for BIND 10

This is the reference guide for BIND 10 version +BIND 10 Guide

BIND 10 Guide

Administrator Reference for BIND 10

This is the reference guide for BIND 10 version 20120405.

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 @@ -10,9 +10,9 @@ 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.2.1. In-memory Data Source
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 +

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.2.1. In-memory Data Source
8.2.2. In-memory Data Source With SQLite3 Backend
8.2.3. Reloading an In-memory Data Source
8.2.4. Disabling In-memory Data Sources
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
9.5. Incoming Transfers with In-memory Datasource
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

+ 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 @@ -23,7 +23,7 @@

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

1.1. Supported Platforms

+

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. @@ -162,7 +162,7 @@ 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

+

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

@@ -224,14 +224,14 @@ the Git code revision control system or as a downloadable tar file. It may also be available in pre-compiled ready-to-use packages from operating system vendors. -

2.3.1. Download Tar File

+

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

+

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. @@ -265,7 +265,7 @@ autoheader, automake, and related commands. -

2.3.3. Configure before the build

+

2.3.3. Configure before the build

BIND 10 uses the GNU Build System to discover build environment details. To generate the makefiles using the defaults, simply run: @@ -296,16 +296,16 @@

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

2.3.4. Build

+

2.3.4. Build

After the configure step is complete, to build the executables from the C++ code and prepare the Python scripts, run: 

$ make

-

2.3.5. Install

+

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

+

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/ — @@ -360,9 +360,8 @@ In its default configuration, the bind10 master process will also start up b10-cmdctl for administration tools to - communicate with the system, - b10-stats for statistics collection, and - b10-stats-httpd for statistics reporting. + communicate with the system, and + b10-stats for statistics collection.

    3.1. Starting BIND 10

    To start the BIND 10 service, simply run bind10. Run it with the --verbose switch to @@ -398,7 +397,7 @@ during startup or shutdown. Unless specified, the component is started in usual way. This is the list of components that need to be started in a special way, with the value of special used for them: -

    Table 3.1. 

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


    +

    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” @@ -626,12 +625,12 @@ shutdown 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.2.1. In-memory Data Source
    8.3. Loading Master Zones Files

    +

    Chapter 8. Authoritative Server

    Table of Contents

    8.1. Server Configurations
    8.2. Data Source Backends
    8.2.1. In-memory Data Source
    8.2.2. In-memory Data Source With SQLite3 Backend
    8.2.3. Reloading an In-memory Data Source
    8.2.4. Disabling In-memory Data Sources
    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

    +

    8.1. Server Configurations

    b10-auth is configured via the b10-cfgmgr configuration manager. The module name is “Auth”. @@ -650,9 +649,10 @@ This may be a temporary setting until then. class to optionally select the class (it defaults to “IN”); and - zones to define the - file path name and the - origin (default domain). + zones to define + the file path name, + the filetype (e.g., sqlite3), + and the origin (default domain). By default, this is empty. @@ -662,7 +662,8 @@ This may be a temporary setting until then. Only the IN class is supported at this time. By default, the memory data source is disabled. Also, currently the zone file must be canonical such as - generated by named-compilezone -D. + generated by named-compilezone -D, or + must be an SQLite3 database.

    listen_on
    @@ -711,7 +712,7 @@ This may be a temporary setting until then. if configured.)

    -

    8.2. Data Source Backends

    Note

    +

    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. @@ -743,7 +744,26 @@ This may be a temporary setting until then. The authoritative server will begin serving it immediately after it is loaded. -

    +

    8.2.2. In-memory Data Source With SQLite3 Backend

    + + The following commands to bindctl + provide an example of configuring an in-memory data + source containing the “example.org” zone + with a SQLite3 backend file named “example.org.sqlite3”: + + + + 

    > config add Auth/datasources
+> config set Auth/datasources[1]/type "memory"
+> config add Auth/datasources[1]/zones
+> config set Auth/datasources[1]/zones[0]/origin "example.org"
+> config set Auth/datasources[1]/zones[0]/file "example.org.sqlite3"
+> config set Auth/datasources[1]/zones[0]/filetype "sqlite3"
+> config commit

    + + The authoritative server will begin serving it immediately + after it is loaded. +

    8.2.3. Reloading an In-memory Data Source

    Use the Auth loadzone command in bindctl to reload a changed master file into memory; for example: @@ -751,7 +771,7 @@ This may be a temporary setting until then. 

    > Auth loadzone origin="example.com"

    -

    +

    8.2.4. Disabling In-memory Data Sources

    By default, the memory data source is disabled; it must be configured explicitly. To disable all the in-memory zones, specify a null list for Auth/datasources: @@ -771,7 +791,7 @@ This may be a temporary setting until then. and/or zones[0] for the relevant zone as needed.) -

    8.3. Loading Master Zones Files

    +

    8.3. Loading Master Zones Files

    RFC 1035 style DNS master zone files may imported into a BIND 10 SQLite3 data source by using the b10-loadzone utility. @@ -800,7 +820,7 @@ This may be a temporary setting until then. If you reload a zone already existing in the database, all records from that prior zone disappear and a whole new set appears. -

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

+

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
9.5. Incoming Transfers with In-memory Datasource

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 @@ -814,11 +834,7 @@ This may be a temporary setting until then. 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

+

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 @@ -834,7 +850,7 @@ This may be a temporary setting until then. > config commit

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

9.2. Enabling IXFR

+

9.2. Enabling IXFR

As noted above, b10-xfrin uses AXFR for zone transfers by default. To enable IXFR for zone transfers for a particular zone, set the use_ixfr @@ -886,12 +902,24 @@ This may be a temporary setting until then. (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

+

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

+

9.5. Incoming Transfers with In-memory Datasource

+ In the case of an incoming zone transfer, the received zone is + first stored in the corresponding BIND 10 datasource. In + case the secondary zone is served by an in-memory datasource + with an SQLite3 backend, b10-auth is + automatically sent a loadzone command to + reload the corresponding zone into memory from the backend. +

+ The administrator doesn't have to do anything for + b10-auth to serve the new version of the + zone, except for the configuration such as the one described in + Section 8.2.2, “In-memory Data Source With SQLite3 Backend”.

Chapter 10. Outbound Zone Transfers

The b10-xfrout process is started by bind10. @@ -935,7 +963,7 @@ Xfrout/transfer_acl[0] {"action": "ACCEPT"} any (default)

TSIGs in the incoming messages and to sign responses.

Note

The way to specify zone specific configuration (ACLs, etc) is likely to be changed. -

Chapter 11. Recursive Name Server

Table of Contents

11.1. Access Control
11.2. Forwarding

+

Chapter 11. Recursive Name Server

Table of Contents

11.1. Access Control
11.2. Forwarding

The b10-resolver process is started by bind10. @@ -969,7 +997,7 @@ Xfrout/transfer_acl[0] {"action": "ACCEPT"} any (default)

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

11.1. Access Control

+ 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 @@ -1002,7 +1030,7 @@ Xfrout/transfer_acl[0] {"action": "ACCEPT"} any (default)

(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

+ syntax may be changed.

11.2. Forwarding

To enable forwarding, the upstream address and port must be configured to forward queries to, such as: @@ -1314,7 +1342,7 @@ eth0 fe80::21e:8cff:fe9b:7349 } }

-

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

+

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 @@ -1323,7 +1351,7 @@ eth0 fe80::21e:8cff:fe9b:7349 -

16.1.1. Loggers

+

16.1.1. Loggers

Within BIND 10, a message is logged through a component called a "logger". Different parts of BIND 10 log messages @@ -1344,7 +1372,7 @@ eth0 fe80::21e:8cff:fe9b:7349 (what to log), and the output_options (where to log). -

16.1.1.1. name (string)

+

16.1.1.1. name (string)

Each logger in the system has a name, the name being that of the component using it to log messages. For instance, if you want to configure logging for the resolver module, @@ -1417,7 +1445,7 @@ eth0 fe80::21e:8cff:fe9b:7349 “Auth.cache” logger will appear in the output with a logger name of “b10-auth.cache”). -

16.1.1.2. severity (string)

+

16.1.1.2. severity (string)

This specifies the category of messages logged. Each message is logged with an associated severity which @@ -1433,7 +1461,7 @@ eth0 fe80::21e:8cff:fe9b:7349 -

16.1.1.3. output_options (list)

+

16.1.1.3. output_options (list)

Each logger can have zero or more output_options. These specify where log @@ -1443,7 +1471,7 @@ eth0 fe80::21e:8cff:fe9b:7349 The other options for a logger are: -

16.1.1.4. debuglevel (integer)

+

16.1.1.4. debuglevel (integer)

When a logger's severity is set to DEBUG, this value specifies what debug messages should be printed. It ranges @@ -1452,7 +1480,7 @@ eth0 fe80::21e:8cff:fe9b:7349 If severity for the logger is not DEBUG, this value is ignored. -

16.1.1.5. additive (true or false)

+

16.1.1.5. additive (true or false)

If this is true, the output_options from the parent will be used. For example, if there are two @@ -1466,18 +1494,18 @@ eth0 fe80::21e:8cff:fe9b:7349 -

16.1.2. Output Options

+

16.1.2. Output Options

The main settings for an output option are the destination and a value called output, the meaning of which depends on the destination that is set. -

16.1.2.1. destination (string)

+

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)

+

  • console
  • file
  • syslog

16.1.2.2. output (string)

Depending on what is set as the output destination, this value is interpreted as follows: @@ -1507,12 +1535,12 @@ eth0 fe80::21e:8cff:fe9b:7349 The other options for output_options are: -

16.1.2.2.1. flush (true of false)

+

16.1.2.2.1. flush (true of false)

Flush buffers after each log message. Doing this will reduce performance but will ensure that if the program terminates abnormally, all messages up to the point of termination are output. -

16.1.2.2.2. maxsize (integer)

+

16.1.2.2.2. maxsize (integer)

Only relevant when destination is file, this is maximum file size of output files in bytes. When the maximum size is reached, the file is renamed and a new file opened. @@ -1521,11 +1549,11 @@ eth0 fe80::21e:8cff:fe9b:7349 etc.)

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

16.1.2.2.3. maxver (integer)

+

16.1.2.2.3. maxver (integer)

Maximum number of old log files to keep around when rolling the output file. Only relevant when destination is “file”. -

16.1.3. Example session

+

16.1.3. Example session

In this example we want to set the global logging to write to the file /var/log/my_bind10.log, @@ -1686,7 +1714,7 @@ Logging/loggers[0]/output_options[0]/maxver 8 integer (modified) And every module will now be using the values from the logger named “*”. -

16.2. Logging Message Format

+

16.2. Logging Message Format

Each message written by BIND 10 to the configured logging destinations comprises a number of components that identify the origin of the message and, if the message indicates diff --git a/doc/guide/bind10-guide.txt b/doc/guide/bind10-guide.txt index cf81af6b3f..d1095be48a 100644 --- a/doc/guide/bind10-guide.txt +++ b/doc/guide/bind10-guide.txt @@ -81,6 +81,13 @@ Administrator Reference for BIND 10 8.2.1. In-memory Data Source + 8.2.2. In-memory Data Source With SQLite3 + Backend + + 8.2.3. Reloading an In-memory Data Source + + 8.2.4. Disabling In-memory Data Sources + 8.3. Loading Master Zones Files 9. Incoming Zone Transfers @@ -93,6 +100,8 @@ Administrator Reference for BIND 10 9.4. Trigger an Incoming Zone Transfer Manually + 9.5. Incoming Transfers with In-memory Datasource + 10. Outbound Zone Transfers 11. Recursive Name Server @@ -497,9 +506,8 @@ Chapter 3. Starting BIND10 with bind10 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 administration tools to communicate with the system, - b10-stats for statistics collection, and b10-stats-httpd for statistics - reporting. + b10-cmdctl for administration tools to communicate with the system, and + b10-stats for statistics collection. 3.1. Starting BIND 10 @@ -755,6 +763,12 @@ Chapter 8. Authoritative Server 8.2.1. In-memory Data Source + 8.2.2. In-memory Data Source With SQLite3 Backend + + 8.2.3. Reloading an In-memory Data Source + + 8.2.4. Disabling In-memory Data Sources + 8.3. Loading Master Zones Files The b10-auth is the authoritative DNS server. It supports EDNS0 and @@ -775,8 +789,8 @@ Chapter 8. Authoritative Server datasources configures data sources. The list items include: type to define the required data source type (such as “memory”); class to optionally select the class (it defaults to “IN”); and zones to - define the file path name and the origin (default domain). By - default, this is empty. + define the file path name, the filetype (e.g., sqlite3), and the + origin (default domain). By default, this is empty. Note @@ -784,7 +798,7 @@ Chapter 8. Authoritative Server memory data source. Only the IN class is supported at this time. By default, the memory data source is disabled. Also, currently the zone file must be canonical such as generated by - named-compilezone -D. + named-compilezone -D, or must be an SQLite3 database. listen_on listen_on is a list of addresses and ports for b10-auth to listen @@ -851,11 +865,32 @@ Chapter 8. Authoritative Server The authoritative server will begin serving it immediately after it is loaded. + 8.2.2. In-memory Data Source With SQLite3 Backend + + The following commands to bindctl provide an example of configuring an + in-memory data source containing the “example.org” zone with a SQLite3 + backend file named “example.org.sqlite3”: + + > config add Auth/datasources + > config set Auth/datasources[1]/type "memory" + > config add Auth/datasources[1]/zones + > config set Auth/datasources[1]/zones[0]/origin "example.org" + > config set Auth/datasources[1]/zones[0]/file "example.org.sqlite3" + > config set Auth/datasources[1]/zones[0]/filetype "sqlite3" + > config commit + + The authoritative server will begin serving it immediately after it is + loaded. + + 8.2.3. Reloading an In-memory Data Source + Use the Auth loadzone command in bindctl to reload a changed master file into memory; for example: > Auth loadzone origin="example.com" + 8.2.4. Disabling In-memory Data Sources + By default, the memory data source is disabled; it must be configured explicitly. To disable all the in-memory zones, specify a null list for Auth/datasources: @@ -914,6 +949,8 @@ Chapter 9. Incoming Zone Transfers 9.4. Trigger an Incoming Zone Transfer Manually + 9.5. Incoming Transfers with In-memory Datasource + 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 @@ -924,12 +961,6 @@ Chapter 9. Incoming Zone Transfers 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 @@ -1003,6 +1034,18 @@ Chapter 9. Incoming Zone Transfers > Xfrin retransfer zone_name="foo.example.org" master=192.0.2.99 +9.5. Incoming Transfers with In-memory Datasource + + In the case of an incoming zone transfer, the received zone is first + stored in the corresponding BIND 10 datasource. In case the secondary zone + is served by an in-memory datasource with an SQLite3 backend, b10-auth is + automatically sent a loadzone command to reload the corresponding zone + into memory from the backend. + + The administrator doesn't have to do anything for b10-auth to serve the + new version of the zone, except for the configuration such as the one + described in Section 8.2.2, “In-memory Data Source With SQLite3 Backend”. + Chapter 10. Outbound Zone Transfers The b10-xfrout process is started by bind10. When the b10-auth