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.5 includes several bug fixes and patches security
57 flaws described in CVE-2012-5688, CVE-2012-5689 and CVE-2013-2266.
61 BIND 9.8.4 includes several bug fixes and patches security
62 flaws described in CVE-2012-1667, CVE-2012-3817 and CVE-2012-4244.
66 BIND 9.8.3 is a maintenance release.
70 BIND 9.8.2 includes a number of bug fixes and prevents a security
71 problem described in CVE-2011-4313
75 BIND 9.8.1 includes a number of bug fixes and enhancements from
76 BIND 9.8 and earlier releases. New features include:
78 - The DLZ "dlopen" driver is now built by default.
79 - Added a new include file with function typedefs
80 for the DLZ "dlopen" driver.
81 - Made "--with-gssapi" default.
82 - More verbose error reporting from DLZ LDAP.
86 BIND 9.8.0 includes a number of changes from BIND 9.7 and earlier
87 releases. New features include:
89 - Built-in trust anchor for the root zone, which can be
90 switched on via "dnssec-validation auto;"
92 - Support for response policy zones (RPZ).
93 - Support for writable DLZ zones.
94 - Improved ease of configuration of GSS/TSIG for
95 interoperability with Active Directory
96 - Support for GOST signing algorithm for DNSSEC.
97 - Removed RTT Banding from server selection algorithm.
98 - New "static-stub" zone type.
99 - Allow configuration of resolver timeouts via
100 "resolver-query-timeout" option.
104 BIND 9.7.0 includes a number of changes from BIND 9.6 and earlier
105 releases. Most are intended to simplify DNSSEC configuration.
107 New features include:
109 - Fully automatic signing of zones by "named".
110 - Simplified configuration of DNSSEC Lookaside Validation (DLV).
111 - Simplified configuration of Dynamic DNS, using the "ddns-confgen"
112 command line tool or the "local" update-policy option. (As a side
113 effect, this also makes it easier to configure automatic zone
115 - New named option "attach-cache" that allows multiple views to
116 share a single cache.
117 - DNS rebinding attack prevention.
118 - New default values for dnssec-keygen parameters.
119 - Support for RFC 5011 automated trust anchor maintenance
120 - Smart signing: simplified tools for zone signing and key
122 - The "statistics-channels" option is now available on Windows.
123 - A new DNSSEC-aware libdns API for use by non-BIND9 applications
124 - On some platforms, named and other binaries can now print out
125 a stack backtrace on assertion failure, to aid in debugging.
126 - A "tools only" installation mode on Windows, which only installs
127 dig, host, nslookup and nsupdate.
128 - Improved PKCS#11 support, including Keyper support and explicit
129 OpenSSL engine selection.
131 Known issues in this release:
133 - In rare cases, DNSSEC validation can leak memory. When this
134 happens, it will cause an assertion failure when named exits,
135 but is otherwise harmless. A fix exists, but was too late for
136 this release; it will be included in BIND 9.7.1.
140 - If you had built BIND 9.6 with any of ALLOW_NSEC3PARAM_UPDATE,
141 ALLOW_SECURE_TO_INSECURE or ALLOW_INSECURE_TO_SECURE defined, then
142 you should ensure that all changes that are in progress have
143 completed prior to upgrading to BIND 9.7. BIND 9.7 implements
144 those features in a way which is not backwards compatible.
146 - Prior releases had a bug which caused HMAC-SHA* keys with long
147 secrets to be used incorrectly. Fixing this bug means that older
148 versions of BIND 9 may fail to interoperate with this version
149 when using TSIG keys. If this occurs, the new "isc-hmac-fixup"
150 tool will convert a key with a long secret into a form that works
151 correctly with all versions of BIND 9. See the "isc-hmac-fixup"
152 man page for additional details.
154 - Revoking a DNSSEC key with "dnssec-revoke" changes its key ID.
155 It is possible for the new key ID to collide with that of a
156 different key. Newly generated keys will not have this problem,
157 as "dnssec-keygen" looks for potential collisions before
158 generating keys, but exercise caution if using key revokation
159 with keys that were generated by older versions of BIND 9. See
160 the Administrator's Reference Manual, section 4.10 ("Dynamic
161 Trust Anchor Management") for more details.
163 - A bug was fixed in which a key's scheduled inactivity date was
164 stored incorectly. Users who participated in the 9.7.0 BETA test
165 and had DNSSEC keys with scheduled inactivity dates will need to
166 reset those keys' dates using "dnssec-settime -I".
170 BIND 9 currently requires a UNIX system with an ANSI C compiler,
171 basic POSIX support, and a 64 bit integer type.
173 We've had successful builds and tests on the following systems:
175 COMPAQ Tru64 UNIX 5.1B
177 FreeBSD 4.10, 5.2.1, 6.2
180 NetBSD 3.x, 4.0-beta, 5.0-beta
182 Solaris 8, 9, 9 (x86), 10
186 NOTE: As of BIND 9.5.1, 9.4.3, and 9.3.6, older versions of
187 Windows, including Windows NT and Windows 2000, are no longer
190 We have recent reports from the user community that a supported
191 version of BIND will build and run on the following systems:
201 Red Hat Enterprise Linux 4, 5
211 Do not use a parallel "make".
213 Several environment variables that can be set before running
214 configure will affect compilation:
217 The C compiler to use. configure tries to figure
218 out the right one for supported systems.
221 C compiler flags. Defaults to include -g and/or -O2
222 as supported by the compiler.
225 System header file directories. Can be used to specify
226 where add-on thread or IPv6 support is, for example.
227 Defaults to empty string.
230 Any additional preprocessor symbols you want defined.
231 Defaults to empty string.
234 Change the default syslog facility of named/lwresd.
235 -DISC_FACILITY=LOG_LOCAL0
236 Enable DNSSEC signature chasing support in dig.
237 -DDIG_SIGCHASE=1 (sets -DDIG_SIGCHASE_TD=1 and
239 Disable dropping queries from particular well known ports.
240 -DNS_CLIENT_DROPPORT=0
241 Sibling glue checking in named-checkzone is enabled by default.
242 To disable the default check set. -DCHECK_SIBLING=0
243 named-checkzone checks out-of-zone addresses by default.
244 To disable this default set. -DCHECK_LOCAL=0
245 To create the default pid files in ${localstatedir}/run rather
246 than ${localstatedir}/run/{named,lwresd}/ set.
248 Enable workaround for Solaris kernel bug about /dev/poll
249 -DISC_SOCKET_USE_POLLWATCH=1
250 The watch timeout is also configurable, e.g.,
251 -DISC_SOCKET_POLLWATCH_TIMEOUT=20
254 Linker flags. Defaults to empty string.
256 The following need to be set when cross compiling.
259 The native C compiler.
260 BUILD_CFLAGS (optional)
261 BUILD_CPPFLAGS (optional)
263 -DNEED_OPTARG=1 (optarg is not declared in <unistd.h>)
264 BUILD_LDFLAGS (optional)
265 BUILD_LIBS (optional)
267 To build shared libraries, specify "--with-libtool" on the
268 configure command line.
270 For the server to support DNSSEC, you need to build it
271 with crypto support. You must have OpenSSL 0.9.5a
272 or newer installed and specify "--with-openssl" on the
273 configure command line. If OpenSSL is installed under
274 a nonstandard prefix, you can tell configure where to
275 look for it using "--with-openssl=/prefix".
277 On some platforms it is necessary to explictly request large
278 file support to handle files bigger than 2GB. This can be
279 done by "--enable-largefile" on the configure command line.
281 On some platforms, BIND 9 can be built with multithreading
282 support, allowing it to take advantage of multiple CPUs.
283 You can specify whether to build a multithreaded BIND 9
284 by specifying "--enable-threads" or "--disable-threads"
285 on the configure command line. The default is operating
288 Support for the "fixed" rrset-order option can be enabled
289 or disabled by specifying "--enable-fixed-rrset" or
290 "--disable-fixed-rrset" on the configure command line.
291 The default is "disabled", to reduce memory footprint.
293 If your operating system has integrated support for IPv6, it
294 will be used automatically. If you have installed KAME IPv6
295 separately, use "--with-kame[=PATH]" to specify its location.
297 "make install" will install "named" and the various BIND 9 libraries.
298 By default, installation is into /usr/local, but this can be changed
299 with the "--prefix" option when running "configure".
301 You may specify the option "--sysconfdir" to set the directory
302 where configuration files like "named.conf" go by default,
303 and "--localstatedir" to set the default parent directory
304 of "run/named.pid". For backwards compatibility with BIND 8,
305 --sysconfdir defaults to "/etc" and --localstatedir defaults to
306 "/var" if no --prefix option is given. If there is a --prefix
307 option, sysconfdir defaults to "$prefix/etc" and localstatedir
308 defaults to "$prefix/var".
310 To see additional configure options, run "configure --help".
311 Note that the help message does not reflect the BIND 8
312 compatibility defaults for sysconfdir and localstatedir.
314 If you're planning on making changes to the BIND 9 source, you
315 should also "make depend". If you're using Emacs, you might find
318 If you need to re-run configure please run "make distclean" first.
319 This will ensure that all the option changes take.
321 Building with gcc is not supported, unless gcc is the vendor's usual
322 compiler (e.g. the various BSD systems, Linux).
324 Known compiler issues:
325 * gcc-3.2.1 and gcc-3.1.1 is known to cause problems with solaris-x86.
326 * gcc prior to gcc-3.2.3 ultrasparc generates incorrect code at -02.
327 * gcc-3.3.5 powerpc generates incorrect code at -02.
328 * Irix, MipsPRO 7.4.1m is known to cause problems.
330 A limited test suite can be run with "make test". Many of
331 the tests require you to configure a set of virtual IP addresses
332 on your system, and some require Perl; see bin/tests/system/README
335 SunOS 4 requires "printf" to be installed to make the shared
336 libraries. sh-utils-1.16 provides a "printf" which compiles
342 The BIND 9 Administrator Reference Manual is included with the
343 source distribution in DocBook XML and HTML format, in the
346 Some of the programs in the BIND 9 distribution have man pages
347 in their directories. In particular, the command line
348 options of "named" are documented in /bin/named/named.8.
349 There is now also a set of man pages for the lwres library.
351 If you are upgrading from BIND 8, please read the migration
352 notes in doc/misc/migration. If you are upgrading from
353 BIND 4, read doc/misc/migration-4to9.
355 Frequently asked questions and their answers can be found in
358 Additional information on various subjects can be found
359 in the other README files.
364 A detailed list of all changes to BIND 9 is included in the
365 file CHANGES, with the most recent changes listed first.
366 Change notes include tags indicating the category of the
367 change that was made; these categories are:
371 [bug] General bug fix
373 [security] Fix for a significant security flaw
375 [experimental] Used for new features when the syntax
376 or other aspects of the design are still
377 in flux and may change
379 [port] Portability enhancement
381 [maint] Updates to built-in data such as root
382 server addresses and keys
384 [tuning] Changes to built-in configuration defaults
385 and constants to improve performanceo
387 [protocol] Updates to the DNS protocol such as new
390 [test] Changes to the automatic tests, not
391 affecting server functionality
393 [cleanup] Minor corrections and refactoring
397 In general, [func] and [experimental] tags will only appear
398 in new-feature releases (i.e., those with version numbers
399 ending in zero). Some new functionality may be backported to
400 older releases on a case-by-case basis. All other change
401 types may be applied to all currently-supported releases.
404 Bug Reports and Mailing Lists
406 Bugs reports should be sent to
410 To join the BIND Users mailing list, send mail to
412 bind-users-request@isc.org
414 archives of which can be found via
416 http://www.isc.org/ops/lists/
418 If you're planning on making changes to the BIND 9 source
419 code, you might want to join the BIND Workers mailing list.
422 bind-workers-request@isc.org