BIND 10 1.0.0
This page documents the status of the first officially supported production release of BIND 10: 1.0.0. It was released in February 2013.
Why use BIND 10?
- allows enabling/disabling extra features via different runable modules
- (semi-)interactive client to conveniently look at and set some configuration settings
- detailed log message system which provides unique log ids with corresponding paragraph explanations
- statistics available via command-line or XML over HTTP
Why use BIND 10 for DNS?
- DNS database backend supports both DNSSEC and DDNS
- DNS database backend supports IXFR (both in and out)
- can migrate DNS data from database backend to in-memory for faster performance
- maintain zone database using SQL
Why use BIND 10 for developers and advanced power users:
- RESTful interface over HTTPS for configurations and control
- detailed documentation for the implementation/public API
- meticulous test cases to help understand and extend the code
- may use the Python scripting language to extend or tweak BIND 10
- new custom or replacement modules may be used
Current BIND 10 DNS Features
- IXFR zone transfers in and out
- AXFR zone transfers in and out
- in-memory backend for zone data
- SQLite3 backend for quick startup or huge amounts of zone data
- DNSSEC: serving signed zones by authoritative server
- either in-memory or from DB backend
- including NSEC3
- DDNS (Dynamic Updates) support
- Access Control (for DDNS and outbound zone transfers)
- TSIG support:
- Part of general ACLs (DDNS uses it)
- authoritative server can verify and sign DNS messages with TSIG
- Zone transfers can have signed transfers
BIND 10 and DHCP
This version of BIND 10 also includes the latest snapshot of the BIND 10 DHCP development (KEA) which is intended for experimental use only. The snapshot includes two DHCP servers, one for IPv4 and one for IPv6. Features of these servers are:
- Able to allocate and renew addresses, and handle lease expiration and releases.
- Supports a subset of clients:
- DHCPv4 clients connected to the server via a relay.
- DHCPv6 clients on the same LAN as the server.
- Able to configure values for standard options returned to a client, either globally or on a per-subnet basis.
- Able to define new options and configure them in the same way as standard options
- Leases are stored in a MySQL database.
- Configuration, logging and process control uses the same mechanisms as the BIND 10 DNS server.
Limitations and known issues with this DHCP snapshot can be found at KeaKnownIssues.