diff --git a/doc/guide/bind10-guide.xml b/doc/guide/bind10-guide.xml index 4df2659aff..48c96f8838 100644 --- a/doc/guide/bind10-guide.xml +++ b/doc/guide/bind10-guide.xml @@ -71,11 +71,12 @@ - For the Y1 prototype release, the only supported data source - backend is SQLite3. The authoritative server requires - SQLite 3.3.9 or newer, - and the b10-xfrin module requires the - Python _sqlite3.so module. + For this development prototype release, the only supported + data source backend is SQLite3. The authoritative server + requires SQLite 3.3.9 or newer. + The b10-xfrin and b10-xfrout + modules require the libboost library, libpython3 library, + and the Python _sqlite3.so module. @@ -153,11 +154,21 @@ b10-xfrin — Incoming zone transfer service. - This process is started as needed to transfer a new copy + 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. + + + @@ -257,6 +268,17 @@ var/ + + The Boost Library, Boost Python library, Python Library, + and Python _sqlite3 module are required to enable the + Xfrout and Xfrin support. + + + + The Python related libraries and modules need to be built + for Python 3.1. + + If the Boost System Library is detected at configure time, BIND 10 will be built using an alternative method for @@ -278,7 +300,7 @@ implementation in BIND 10. Building BIND 10 also requires a C++ compiler and standard development headers. BIND 10 builds have been tested with GCC g++ 3.4.3, 4.1.2, - 4.2.1, 4.3.2, and 4.4.1. + 4.1.3, 4.2.1, 4.3.2, and 4.4.1. @@ -295,7 +317,7 @@ implementation in BIND 10. - The Y1 prototype of the b10-auth server listens on + The development prototype of the b10-auth server listens on 0.0.0.0 (all interfaces) port 5300. (This is not the standard domain service port.) @@ -421,9 +443,7 @@ implementation in BIND 10. and un-reviewed code, is available via the BIND 10 code revision control system. This is powered by Subversion and all the BIND 10 development is public. - The leading development is done in the trunk - and the reviewed code is in - branches/REVIEWED. + The leading development is done in the trunk. The code can be checked out from svn://bind10.isc.org/svn/bind10; for example to check out the trunk: @@ -464,26 +484,10 @@ implementation in BIND 10. - --with-boostlib - - Define the path to find the Boost system library. - - - - - - --without-boostlib or - --with-boostlib=no - - Disable the Boost ASIO support. - - - - - --with-pythonpath - - Define the path to Python 3.1 if it is not in the - standard execution path. + --prefix + + Define the the installation location (the + default is /usr/local/). @@ -497,10 +501,44 @@ implementation in BIND 10. - --prefix - - Define the the installation location (the - default is /usr/local/). + --with-boost-lib + + Define the path to find the Boost library. + + + + + + --with-boost-python + + Define to use the Boost Python library. + + + + + + --with-boost-system + + Define to use the Boost System library. + + + + + + --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. @@ -508,15 +546,17 @@ implementation in BIND 10. - + For example, the following configures it to build with BOOST ASIO support, find the Boost headers, find the Python interpreter, and sets the installation location: - $ ./configure --with-boostlib=/usr/pkg/lib \ + $ ./configure --with-boost-lib=/usr/pkg/lib \ --with-boost-include=/usr/pkg/include \ + --with-boost-python \ + --with-boost-system \ --with-pythonpath=/usr/pkg/bin/python3.1 \ --prefix=/opt/bind10 @@ -652,7 +692,8 @@ implementation in BIND 10. The bind10 master process will also start up b10-cmdctl for admins to communicate with the system, b10-auth for Authoritative DNS service, - and b10-xfrin for inbound DNS zone transfers. + b10-xfrin for inbound DNS zone transfers. + and b10-xfrout for outbound DNS zone transfers.
@@ -691,11 +732,13 @@ implementation in BIND 10. It listens on 127.0.0.1. + - The Y1 prototype release only provides the + The development prototype release only provides the bindctl as a user interface to b10-cmdctl. Upcoming releases will provide another interactive command-line @@ -955,7 +998,7 @@ TODO Control and configure user interface - For the Y1 prototype release, bindctl + 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 @@ -1000,8 +1043,8 @@ TODO - The Y1 prototype release listens on all interfaces and the non-standard - port 5300. + This development prototype release listens on all interfaces + and the non-standard port 5300.
@@ -1061,7 +1104,7 @@ This may be a temporary setting until then. Data Source Backends - For the Y1 prototype release, b10-auth + For the development prototype release, b10-auth only supports the SQLite3 data source backend. Upcoming versions will be able to use multiple different data sources, such as MySQL, Berkeley DB, or in-memory DB. @@ -1131,7 +1174,8 @@ This may be a temporary setting until then. - In the Y1 prototype release, only the SQLite3 back end is used. + 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 switch is used to set the @@ -1161,6 +1205,69 @@ TODO + + Incoming Zone Transfers + + + The b10-xfrin process is started by + bind10. + It can be manually triggered to request an AXFR zone + transfer. When received, it is stored in the BIND 10 + data store, and its records can be served by + b10-auth. + This allows the BIND 10 server to provide + secondary service. + + + + The current development release of BIND 10 only supports + AXFR. (IXFR is not supported.) + It also does not yet support automated SOA checks. + + + + 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="" master= + + + + + + Outbound Zone Transfers + + + The b10-xfrout process is started by + bind10. + When the b10-auth authoritative DNS server + receives an AXFR request, b10-xfrout + sends the zone. + This is used to provide master DNS service to share zones + to secondary name servers. + + + + The current development release of BIND 10 only supports + AXFR. (IXFR is not supported.) + It also does not yet support NOTIFY. + Access control is not yet provided. + + + + + + +