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.9.3 is a maintenance release and patches the security
57 flaws described in CVE-2012-5688, CVE-2012-5689 and CVE-2013-2266.
61 BIND 9.9.2 is a maintenance release and patches the security
62 flaw described in CVE-2012-4244.
66 BIND 9.9.1 is a maintenance release.
70 BIND 9.9.0 includes a number of changes from BIND 9.8 and earlier
71 releases. New features include:
73 - Inline signing, allowing automatic DNSSEC signing of
74 master zones without modification of the zonefile, or
75 "bump in the wire" signing in slaves.
76 - NXDOMAIN redirection.
77 - New 'rndc flushtree' command clears all data under a given
78 name from the DNS cache.
79 - New 'rndc sync' command dumps pending changes in a dynamic
80 zone to disk without a freeze/thaw cycle.
81 - New 'rndc signing' command displays or clears signing status
82 records in 'auto-dnssec' zones.
83 - NSEC3 parameters for 'auto-dnssec' zones can now be set prior
84 to signing, eliminating the need to initially sign with NSEC.
85 - Startup time improvements on large authoritative servers.
86 - Slave zones are now saved in raw format by default.
87 - Several improvements to response policy zones (RPZ).
88 - Improved hardware scalability by using multiple threads
89 to listen for queries and using finer-grained client locking
90 - The 'also-notify' option now takes the same syntax as
91 'masters', so it can used named masterlists and TSIG keys.
92 - 'dnssec-signzone -D' writes an output file containing only DNSSEC
93 data, which can be included by the primary zone file.
94 - 'dnssec-signzone -R' forces removal of signatures that are
95 not expired but were created by a key which no longer exists.
96 - 'dnssec-signzone -X' allows a separate expiration date to
97 be specified for DNSKEY signatures from other signatures.
98 - New '-L' option to dnssec-keygen, dnssec-settime, and
99 dnssec-keyfromlabel sets the default TTL for the key.
100 - dnssec-dsfromkey now supports reading from standard input,
101 to make it easier to convert DNSKEY to DS.
102 - RFC 1918 reverse zones have been added to the empty-zones
104 - Dynamic updates can now optionally set the zone's SOA serial
105 number to the current UNIX time.
106 - DLZ modules can now retrieve the source IP address of
108 - 'request-ixfr' option can now be set at the per-zone level.
109 - 'dig +rrcomments' turns on comments about DNSKEY records,
110 indicating their key ID, algorithm and function
111 - Simplified nsupdate syntax and added readline support
115 BIND 9 currently requires a UNIX system with an ANSI C compiler,
116 basic POSIX support, and a 64 bit integer type.
118 We've had successful builds and tests on the following systems:
120 COMPAQ Tru64 UNIX 5.1B
122 FreeBSD 4.10, 5.2.1, 6.2
125 NetBSD 3.x, 4.0-beta, 5.0-beta
127 Solaris 8, 9, 9 (x86), 10
131 NOTE: As of BIND 9.5.1, 9.4.3, and 9.3.6, older versions of
132 Windows, including Windows NT and Windows 2000, are no longer
135 We have recent reports from the user community that a supported
136 version of BIND will build and run on the following systems:
145 MacOS X 10.5, 10.6, 10.7
146 Red Hat Enterprise Linux 4, 5, 6
156 Do not use a parallel "make".
158 Several environment variables that can be set before running
159 configure will affect compilation:
162 The C compiler to use. configure tries to figure
163 out the right one for supported systems.
166 C compiler flags. Defaults to include -g and/or -O2
167 as supported by the compiler. Please include '-g'
168 if you need to set CFLAGS.
171 System header file directories. Can be used to specify
172 where add-on thread or IPv6 support is, for example.
173 Defaults to empty string.
176 Any additional preprocessor symbols you want defined.
177 Defaults to empty string.
180 Change the default syslog facility of named/lwresd.
181 -DISC_FACILITY=LOG_LOCAL0
182 Enable DNSSEC signature chasing support in dig.
183 -DDIG_SIGCHASE=1 (sets -DDIG_SIGCHASE_TD=1 and
185 Disable dropping queries from particular well known ports.
186 -DNS_CLIENT_DROPPORT=0
187 Sibling glue checking in named-checkzone is enabled by default.
188 To disable the default check set. -DCHECK_SIBLING=0
189 named-checkzone checks out-of-zone addresses by default.
190 To disable this default set. -DCHECK_LOCAL=0
191 To create the default pid files in ${localstatedir}/run rather
192 than ${localstatedir}/run/{named,lwresd}/ set.
194 Enable workaround for Solaris kernel bug about /dev/poll
195 -DISC_SOCKET_USE_POLLWATCH=1
196 The watch timeout is also configurable, e.g.,
197 -DISC_SOCKET_POLLWATCH_TIMEOUT=20
200 Linker flags. Defaults to empty string.
202 The following need to be set when cross compiling.
205 The native C compiler.
206 BUILD_CFLAGS (optional)
207 BUILD_CPPFLAGS (optional)
209 -DNEED_OPTARG=1 (optarg is not declared in <unistd.h>)
210 BUILD_LDFLAGS (optional)
211 BUILD_LIBS (optional)
213 To build shared libraries, specify "--with-libtool" on the
214 configure command line.
216 For the server to support DNSSEC, you need to build it
217 with crypto support. You must have OpenSSL 0.9.5a
218 or newer installed and specify "--with-openssl" on the
219 configure command line. If OpenSSL is installed under
220 a nonstandard prefix, you can tell configure where to
221 look for it using "--with-openssl=/prefix".
223 On some platforms it is necessary to explictly request large
224 file support to handle files bigger than 2GB. This can be
225 done by "--enable-largefile" on the configure command line.
227 On some platforms, BIND 9 can be built with multithreading
228 support, allowing it to take advantage of multiple CPUs.
229 You can specify whether to build a multithreaded BIND 9
230 by specifying "--enable-threads" or "--disable-threads"
231 on the configure command line. The default is operating
234 Support for the "fixed" rrset-order option can be enabled
235 or disabled by specifying "--enable-fixed-rrset" or
236 "--disable-fixed-rrset" on the configure command line.
237 The default is "disabled", to reduce memory footprint.
239 If your operating system has integrated support for IPv6, it
240 will be used automatically. If you have installed KAME IPv6
241 separately, use "--with-kame[=PATH]" to specify its location.
243 "make install" will install "named" and the various BIND 9 libraries.
244 By default, installation is into /usr/local, but this can be changed
245 with the "--prefix" option when running "configure".
247 You may specify the option "--sysconfdir" to set the directory
248 where configuration files like "named.conf" go by default,
249 and "--localstatedir" to set the default parent directory
250 of "run/named.pid". For backwards compatibility with BIND 8,
251 --sysconfdir defaults to "/etc" and --localstatedir defaults to
252 "/var" if no --prefix option is given. If there is a --prefix
253 option, sysconfdir defaults to "$prefix/etc" and localstatedir
254 defaults to "$prefix/var".
256 To see additional configure options, run "configure --help".
257 Note that the help message does not reflect the BIND 8
258 compatibility defaults for sysconfdir and localstatedir.
260 If you're planning on making changes to the BIND 9 source, you
261 should also "make depend". If you're using Emacs, you might find
264 If you need to re-run configure please run "make distclean" first.
265 This will ensure that all the option changes take.
267 Building with gcc is not supported, unless gcc is the vendor's usual
268 compiler (e.g. the various BSD systems, Linux).
270 Known compiler issues:
271 * gcc-3.2.1 and gcc-3.1.1 is known to cause problems with solaris-x86.
272 * gcc prior to gcc-3.2.3 ultrasparc generates incorrect code at -02.
273 * gcc-3.3.5 powerpc generates incorrect code at -02.
274 * Irix, MipsPRO 7.4.1m is known to cause problems.
276 A limited test suite can be run with "make test". Many of
277 the tests require you to configure a set of virtual IP addresses
278 on your system, and some require Perl; see bin/tests/system/README
281 SunOS 4 requires "printf" to be installed to make the shared
282 libraries. sh-utils-1.16 provides a "printf" which compiles
287 Linux requires kernel build 2.6.39 or later to get the
288 performance benefits from using multiple sockets.
292 The BIND 9 Administrator Reference Manual is included with the
293 source distribution in DocBook XML and HTML format, in the
296 Some of the programs in the BIND 9 distribution have man pages
297 in their directories. In particular, the command line
298 options of "named" are documented in /bin/named/named.8.
299 There is now also a set of man pages for the lwres library.
301 If you are upgrading from BIND 8, please read the migration
302 notes in doc/misc/migration. If you are upgrading from
303 BIND 4, read doc/misc/migration-4to9.
305 Frequently asked questions and their answers can be found in
308 Additional information on various subjects can be found
309 in the other README files.
314 A detailed list of all changes to BIND 9 is included in the
315 file CHANGES, with the most recent changes listed first.
316 Change notes include tags indicating the category of the
317 change that was made; these categories are:
321 [bug] General bug fix
323 [security] Fix for a significant security flaw
325 [experimental] Used for new features when the syntax
326 or other aspects of the design are still
327 in flux and may change
329 [port] Portability enhancement
331 [maint] Updates to built-in data such as root
332 server addresses and keys
334 [tuning] Changes to built-in configuration defaults
335 and constants to improve performanceo
337 [protocol] Updates to the DNS protocol such as new
340 [test] Changes to the automatic tests, not
341 affecting server functionality
343 [cleanup] Minor corrections and refactoring
347 In general, [func] and [experimental] tags will only appear
348 in new-feature releases (i.e., those with version numbers
349 ending in zero). Some new functionality may be backported to
350 older releases on a case-by-case basis. All other change
351 types may be applied to all currently-supported releases.
354 Bug Reports and Mailing Lists
356 Bugs reports should be sent to
360 To join the BIND Users mailing list, send mail to
362 bind-users-request@isc.org
364 archives of which can be found via
366 http://www.isc.org/ops/lists/
368 If you're planning on making changes to the BIND 9 source
369 code, you might want to join the BIND Workers mailing list.
372 bind-workers-request@isc.org