3 BIND version 9 is a major rewrite of nearly all aspects of the
4 underlying BIND architecture. Some of the important features of
9 TSIG (signed DNS requests)
12 Answers DNS queries on IPv6 sockets
13 IPv6 resource records (AAAA)
14 Experimental IPv6 Resolver Library
16 - DNS Protocol Enhancements
17 IXFR, DDNS, Notify, EDNS0
18 Improved standards conformance
21 One server process can provide multiple "views" of
22 the DNS namespace, e.g. an "inside" view to certain
23 clients, and an "outside" view to others.
25 - Multiprocessor Support
27 - Improved Portability Architecture
30 BIND version 9 development has been underwritten by the following
33 Sun Microsystems, Inc.
35 Compaq Computer Corporation
37 Process Software Corporation
38 Silicon Graphics, Inc.
39 Network Associates, Inc.
40 U.S. Defense Information Systems Agency
42 Stichting NLnet - NLnet Foundation
45 For a summary of functional enhancements in previous
46 releases, see the HISTORY file.
48 For a detailed list of user-visible changes from
49 previous releases, see the CHANGES file.
51 For up-to-date release notes and errata, see
52 http://www.isc.org/software/bind9/releasenotes
56 BIND 9.8.7 includes several bug fixes and patches the security
57 flaws described in CVE-2013-6320 and CVE-2014-0591. It also
58 includes the following functional enhancements:
60 - "named" now preserves the capitalization of names when
61 responding to queries.
62 - "named-checkconf -px" will print the contents of configuration
63 files with the shared secrets obscured, making it easier to
64 share configuration (e.g. when submitting a bug report)
65 without revealing private information.
69 BIND 9.8.6 includes several bug fixes and patches the security
70 flaws described in CVE-2013-3919 and CVE-2013-4854.
74 BIND 9.8.5 includes several bug fixes and patches security
75 flaws described in CVE-2012-5688, CVE-2012-5689 and CVE-2013-2266.
79 BIND 9.8.4 includes several bug fixes and patches security
80 flaws described in CVE-2012-1667, CVE-2012-3817 and CVE-2012-4244.
84 BIND 9.8.3 is a maintenance release.
88 BIND 9.8.2 includes a number of bug fixes and prevents a security
89 problem described in CVE-2011-4313
93 BIND 9.8.1 includes a number of bug fixes and enhancements from
94 BIND 9.8 and earlier releases. New features include:
96 - The DLZ "dlopen" driver is now built by default.
97 - Added a new include file with function typedefs
98 for the DLZ "dlopen" driver.
99 - Made "--with-gssapi" default.
100 - More verbose error reporting from DLZ LDAP.
104 BIND 9.8.0 includes a number of changes from BIND 9.7 and earlier
105 releases. New features include:
107 - Built-in trust anchor for the root zone, which can be
108 switched on via "dnssec-validation auto;"
110 - Support for response policy zones (RPZ).
111 - Support for writable DLZ zones.
112 - Improved ease of configuration of GSS/TSIG for
113 interoperability with Active Directory
114 - Support for GOST signing algorithm for DNSSEC.
115 - Removed RTT Banding from server selection algorithm.
116 - New "static-stub" zone type.
117 - Allow configuration of resolver timeouts via
118 "resolver-query-timeout" option.
122 BIND 9.7.0 includes a number of changes from BIND 9.6 and earlier
123 releases. Most are intended to simplify DNSSEC configuration.
125 New features include:
127 - Fully automatic signing of zones by "named".
128 - Simplified configuration of DNSSEC Lookaside Validation (DLV).
129 - Simplified configuration of Dynamic DNS, using the "ddns-confgen"
130 command line tool or the "local" update-policy option. (As a side
131 effect, this also makes it easier to configure automatic zone
133 - New named option "attach-cache" that allows multiple views to
134 share a single cache.
135 - DNS rebinding attack prevention.
136 - New default values for dnssec-keygen parameters.
137 - Support for RFC 5011 automated trust anchor maintenance
138 - Smart signing: simplified tools for zone signing and key
140 - The "statistics-channels" option is now available on Windows.
141 - A new DNSSEC-aware libdns API for use by non-BIND9 applications
142 - On some platforms, named and other binaries can now print out
143 a stack backtrace on assertion failure, to aid in debugging.
144 - A "tools only" installation mode on Windows, which only installs
145 dig, host, nslookup and nsupdate.
146 - Improved PKCS#11 support, including Keyper support and explicit
147 OpenSSL engine selection.
149 Known issues in this release:
151 - In rare cases, DNSSEC validation can leak memory. When this
152 happens, it will cause an assertion failure when named exits,
153 but is otherwise harmless. A fix exists, but was too late for
154 this release; it will be included in BIND 9.7.1.
158 - If you had built BIND 9.6 with any of ALLOW_NSEC3PARAM_UPDATE,
159 ALLOW_SECURE_TO_INSECURE or ALLOW_INSECURE_TO_SECURE defined, then
160 you should ensure that all changes that are in progress have
161 completed prior to upgrading to BIND 9.7. BIND 9.7 implements
162 those features in a way which is not backwards compatible.
164 - Prior releases had a bug which caused HMAC-SHA* keys with long
165 secrets to be used incorrectly. Fixing this bug means that older
166 versions of BIND 9 may fail to interoperate with this version
167 when using TSIG keys. If this occurs, the new "isc-hmac-fixup"
168 tool will convert a key with a long secret into a form that works
169 correctly with all versions of BIND 9. See the "isc-hmac-fixup"
170 man page for additional details.
172 - Revoking a DNSSEC key with "dnssec-revoke" changes its key ID.
173 It is possible for the new key ID to collide with that of a
174 different key. Newly generated keys will not have this problem,
175 as "dnssec-keygen" looks for potential collisions before
176 generating keys, but exercise caution if using key revokation
177 with keys that were generated by older versions of BIND 9. See
178 the Administrator's Reference Manual, section 4.10 ("Dynamic
179 Trust Anchor Management") for more details.
181 - A bug was fixed in which a key's scheduled inactivity date was
182 stored incorectly. Users who participated in the 9.7.0 BETA test
183 and had DNSSEC keys with scheduled inactivity dates will need to
184 reset those keys' dates using "dnssec-settime -I".
188 BIND 9 currently requires a UNIX system with an ANSI C compiler,
189 basic POSIX support, and a 64 bit integer type.
191 We've had successful builds and tests on the following systems:
193 COMPAQ Tru64 UNIX 5.1B
195 FreeBSD 4.10, 5.2.1, 6.2
198 NetBSD 3.x, 4.0-beta, 5.0-beta
200 Solaris 8, 9, 9 (x86), 10
204 NOTE: As of BIND 9.5.1, 9.4.3, and 9.3.6, older versions of
205 Windows, including Windows NT and Windows 2000, are no longer
208 We have recent reports from the user community that a supported
209 version of BIND will build and run on the following systems:
219 Red Hat Enterprise Linux 4, 5
229 Do not use a parallel "make".
231 Several environment variables that can be set before running
232 configure will affect compilation:
235 The C compiler to use. configure tries to figure
236 out the right one for supported systems.
239 C compiler flags. Defaults to include -g and/or -O2
240 as supported by the compiler.
243 System header file directories. Can be used to specify
244 where add-on thread or IPv6 support is, for example.
245 Defaults to empty string.
248 Any additional preprocessor symbols you want defined.
249 Defaults to empty string.
252 Change the default syslog facility of named/lwresd.
253 -DISC_FACILITY=LOG_LOCAL0
254 Enable DNSSEC signature chasing support in dig.
255 -DDIG_SIGCHASE=1 (sets -DDIG_SIGCHASE_TD=1 and
257 Disable dropping queries from particular well known ports.
258 -DNS_CLIENT_DROPPORT=0
259 Sibling glue checking in named-checkzone is enabled by default.
260 To disable the default check set. -DCHECK_SIBLING=0
261 named-checkzone checks out-of-zone addresses by default.
262 To disable this default set. -DCHECK_LOCAL=0
263 To create the default pid files in ${localstatedir}/run rather
264 than ${localstatedir}/run/{named,lwresd}/ set.
266 Enable workaround for Solaris kernel bug about /dev/poll
267 -DISC_SOCKET_USE_POLLWATCH=1
268 The watch timeout is also configurable, e.g.,
269 -DISC_SOCKET_POLLWATCH_TIMEOUT=20
272 Linker flags. Defaults to empty string.
274 The following need to be set when cross compiling.
277 The native C compiler.
278 BUILD_CFLAGS (optional)
279 BUILD_CPPFLAGS (optional)
281 -DNEED_OPTARG=1 (optarg is not declared in <unistd.h>)
282 BUILD_LDFLAGS (optional)
283 BUILD_LIBS (optional)
285 To build shared libraries, specify "--with-libtool" on the
286 configure command line.
288 For the server to support DNSSEC, you need to build it
289 with crypto support. You must have OpenSSL 0.9.5a
290 or newer installed and specify "--with-openssl" on the
291 configure command line. If OpenSSL is installed under
292 a nonstandard prefix, you can tell configure where to
293 look for it using "--with-openssl=/prefix".
295 On some platforms it is necessary to explictly request large
296 file support to handle files bigger than 2GB. This can be
297 done by "--enable-largefile" on the configure command line.
299 On some platforms, BIND 9 can be built with multithreading
300 support, allowing it to take advantage of multiple CPUs.
301 You can specify whether to build a multithreaded BIND 9
302 by specifying "--enable-threads" or "--disable-threads"
303 on the configure command line. The default is operating
306 Support for the "fixed" rrset-order option can be enabled
307 or disabled by specifying "--enable-fixed-rrset" or
308 "--disable-fixed-rrset" on the configure command line.
309 The default is "disabled", to reduce memory footprint.
311 If your operating system has integrated support for IPv6, it
312 will be used automatically. If you have installed KAME IPv6
313 separately, use "--with-kame[=PATH]" to specify its location.
315 "make install" will install "named" and the various BIND 9 libraries.
316 By default, installation is into /usr/local, but this can be changed
317 with the "--prefix" option when running "configure".
319 You may specify the option "--sysconfdir" to set the directory
320 where configuration files like "named.conf" go by default,
321 and "--localstatedir" to set the default parent directory
322 of "run/named.pid". For backwards compatibility with BIND 8,
323 --sysconfdir defaults to "/etc" and --localstatedir defaults to
324 "/var" if no --prefix option is given. If there is a --prefix
325 option, sysconfdir defaults to "$prefix/etc" and localstatedir
326 defaults to "$prefix/var".
328 To see additional configure options, run "configure --help".
329 Note that the help message does not reflect the BIND 8
330 compatibility defaults for sysconfdir and localstatedir.
332 If you're planning on making changes to the BIND 9 source, you
333 should also "make depend". If you're using Emacs, you might find
336 If you need to re-run configure please run "make distclean" first.
337 This will ensure that all the option changes take.
339 Building with gcc is not supported, unless gcc is the vendor's usual
340 compiler (e.g. the various BSD systems, Linux).
342 Known compiler issues:
343 * gcc-3.2.1 and gcc-3.1.1 is known to cause problems with solaris-x86.
344 * gcc prior to gcc-3.2.3 ultrasparc generates incorrect code at -02.
345 * gcc-3.3.5 powerpc generates incorrect code at -02.
346 * Irix, MipsPRO 7.4.1m is known to cause problems.
348 A limited test suite can be run with "make test". Many of
349 the tests require you to configure a set of virtual IP addresses
350 on your system, and some require Perl; see bin/tests/system/README
353 SunOS 4 requires "printf" to be installed to make the shared
354 libraries. sh-utils-1.16 provides a "printf" which compiles
360 The BIND 9 Administrator Reference Manual is included with the
361 source distribution in DocBook XML and HTML format, in the
364 Some of the programs in the BIND 9 distribution have man pages
365 in their directories. In particular, the command line
366 options of "named" are documented in /bin/named/named.8.
367 There is now also a set of man pages for the lwres library.
369 If you are upgrading from BIND 8, please read the migration
370 notes in doc/misc/migration. If you are upgrading from
371 BIND 4, read doc/misc/migration-4to9.
373 Frequently asked questions and their answers can be found in
376 Additional information on various subjects can be found
377 in the other README files.
382 A detailed list of all changes to BIND 9 is included in the
383 file CHANGES, with the most recent changes listed first.
384 Change notes include tags indicating the category of the
385 change that was made; these categories are:
389 [bug] General bug fix
391 [security] Fix for a significant security flaw
393 [experimental] Used for new features when the syntax
394 or other aspects of the design are still
395 in flux and may change
397 [port] Portability enhancement
399 [maint] Updates to built-in data such as root
400 server addresses and keys
402 [tuning] Changes to built-in configuration defaults
403 and constants to improve performanceo
405 [protocol] Updates to the DNS protocol such as new
408 [test] Changes to the automatic tests, not
409 affecting server functionality
411 [cleanup] Minor corrections and refactoring
415 In general, [func] and [experimental] tags will only appear
416 in new-feature releases (i.e., those with version numbers
417 ending in zero). Some new functionality may be backported to
418 older releases on a case-by-case basis. All other change
419 types may be applied to all currently-supported releases.
422 Bug Reports and Mailing Lists
424 Bugs reports should be sent to
428 To join the BIND Users mailing list, send mail to
430 bind-users-request@isc.org
432 archives of which can be found via
434 http://www.isc.org/ops/lists/
436 If you're planning on making changes to the BIND 9 source
437 code, you might want to join the BIND Workers mailing list.
440 bind-workers-request@isc.org