[master] Regen HTML and text versions of the guide

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