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