This is the first release candidate for the upcoming 1.2.0 release of BIND 10. BIND 10 provides an authoritative DNS server (with in-memory and SQLite3 backends), DNSSEC support, dynamic DNS, zone transfers. Supplementary components are included for statistics collection and reporting and remote configuration and control are included, as is an experimental recursive nameserver with support for forwarding. The suite also provides DHCPv4 and DHCPv6 servers, a dynamic DNS component, and a C++ library for DHCP. Since the beta release, this DHCP project, known as Kea, introduced Rebind message support for the DHCPv6 server, an experimental PostgreSQL database backend for leases, and CSV file storage for in-memory leases. For information about the Kea project, please visit http://kea.isc.org/ All significant changes since the beta release have been in the DHCP code and are: 778. [func]* marcin libdhcpsrv: the Memfile lease storage backend now writes leases into a CSV file. Configuration parsers for b10-dhcp4 and b10-dhcp6 use the new configuration parameters to control the location of the lease file. It is possible to disable lease writes to disk using configuration for testing purposes. (Trac #3360, git 09e6e71abf8bc693e389ebd262fd149b43c1f1d4) 777. [func] tmark If b10-dhcp-ddns is configured to listen on an address other than loopback, it will issue a log message warning the user that this is insecure and is supported for testing purposes only. (Trac #3383, git 652aa4de2fa82fdf3de569d01d9f4aa618fc1972) 776. [func] tomek b10-dhcp4 and b10-dhcp6 now support using PostgreSQL as the backend for storing lease data. This backend is enabled by specifying --with-dhcp-pgsql on the "configure" command line. Without this switch the PostgreSQL backend is not compiled leaving BIND 10 able to be built on systems without PostgreSQL installed. Thanks to David Carlier who contributed the initial patches for this work. (Trac #3080, git 1aae8b1fab3008e62c4f085948b1abadad512447) 775. [func] marcin b10-dhcp4, b10-dhcp6: added a new parameter to subnet configuration. This parameter allows subnet ids to be set to arbitrary values or automatically generated values. Generated subnet ids are renumbered each time one or more subnets are removed. Setting the ids to specific values prevents this renumbering. (Trac #3281, git d90e9a0642fbb16a4e664160b4812f61fb81f1aa) 774. [doc] marcin Updated information in the BIND 10 Guide about the standards supported by Kea and its current limitations. (Trac #3258, git ff52b86206e3a256a02ca6d5cde55040550ba86a) 773. [doc] tmark Added sections to the BIND 10 guide on configuring and using the DHCP-DDNS feature of Kea. Chapter 19, describes the new DHCP-DDNS server and its configuration. Additions to chapters 17 and 18 describe configuring the DHCP servers to work with the new server. (Trac #3283, git 806eea955c61eba2d7268958a740a8e8ea63bdaf) 772. [bug] tmark b10-dhcp4 and b10-dhcp6 now both correctly support DDNS updates when honoring client requested delegation. When DDNS is enabled, and the client's FQDN indicates they will do the forward updates, the servers will now post a DDNS update request to b10-dhcp-ddns for the reverse updates. Prior to this the servers were posting no DDNS update requests when honoring client delegation. (Trac #3352, git b1a0f405463723d539b2e6ed2dcdd692d7796b88) 771. [bug] tmark Ticket #3339 (entry 760) was reverted to fix regression where components added through bindctl, could not be removed. (Trac #3374, git c641e2d0569df3ca3e5a93beaf0ecf39db07e402) 770. [bug] tmark Configuration parsing in b10-dhcp6 and b10-dhcp4 for the "dhcp-ddns" section of their configurations now supplies hard-coded default values rather than those from their spec files. This is a temporary solution to circumvent an issue in the configuration libraries which causes map-items to behave incorrectly. (Trac #3358, git 983d8acec3a7ccb1ffef662eac7518aed5f99381) 769. [func] marcin b10-dhcp6: Implemented support for Rebind message. (Trac #3232, git 3649413932857470558a6f19e0b0e181b3fc0fda) 768. [bug] tmark b10-dhcp-ddns now treats a DNS server response code of NXRRSET as a successful outcome when processing a request to remove DNS data. This corrects a defect in which b10-dhcp-ddns would incorrectly fail a request to remove DNS data when the DNS server's response was NXRRSET. (Trac #3362, git da3b0d4f364d069ffdb47723545798ac589fae42) 767. [func] tomek Unit-tests for all DHCP database backends are now shared. This improves test coverage for memfile and any future backends that may appear. (Trac #3359, git 3d6c11630ada9d0681a813cf026f6bb16aabb9fa) (For the full commit history, please see the git logs.) The bind10-1.2.0rc1 source may be downloaded from: ftp://ftp.isc.org/isc/bind10/1.2.0rc1/bind10-1.2.0rc1.tar.gz A PGP signature of the distribution is at ftp://ftp.isc.org/isc/bind10/1.2.0rc1/bind10-1.2.0rc1.tar.gz.sha512.asc The signature was generated with the ISC code signing key which is available at https://www.isc.org/about/openpgp Installation details are documented in the BIND 10 Guide. In addition, installation suggestions for various operating systems are available via our wiki http://bind10.isc.org/wiki/InstallStartPage. (Please note that there are build regressions on Solaris platforms for the DNS code.) The ./configure options --disable-dns and --disable-dhcp may be used to provide an optional DHCP- or DNS-only build and installation. This is a release candidate and we would appreciate testers providing feedback. If you have any questions or comments about working with this release, you may post them to the BIND 10 Users List https://lists.isc.org/mailman/listinfo/bind10-users, the Kea DHCP Mailing List https://lists.isc.org/mailman/listinfo/kea-users, or to the BIND 10 Jabber room. Jeremy C. Reed ISC Release Engineering