Andreas.Gustafsson at nominum.com
Wed May 24 00:12:11 UTC 2000
Announcing the release of BIND version 9 Beta 3.
ISC is proud to announce the public availability of BIND version 9 Beta 3.
This beta release is not intended for production use. Most core
functionality is present, but some work still remains to be completed.
BIND version 9 beta 3 is available from:
Enclosed is the README file included with the distribution kit.
BIND version 9 is a major rewrite of nearly all aspects of the
underlying BIND architecture. This re-architecting of BIND was
necessitated by the expected demands of:
- Domain name system growth, particularly in very large
zones such as .COM
- Protocol enhancements necessary to securely query and
- Protocol enhancements necessary to take advantage of
certain architectural features of IP version 6
These demands implied performance requirements that were not
necessarily easy to attain with the BIND version 8
architecture. In particular, BIND must not only be able to
run on multi-processor multi-threaded systems, but must take
full advantage of the performance enhancements these
architectures can provide. In addition, the underlying data
storage architecture of BIND version 8 does not lend itself to
implementing alternative back end databases, such as would be
desirable for the support of multi-gigabyte zones. As such
zones are easily foreseeable in the relatively near future,
the data storage architecture needed revision. The feature
requirements for BIND version 9 included:
Support for very large zones
Support for DNSSEC
Support for TSIG
Auditability (code and operation)
Firewall support (split DNS)
- Protocol Enhancements
IXFR, DDNS, Notify, EDNS0
Improved standards conformance
- Operational enhancements
High availability and reliability
Support for alternative back end databases
- IP version 6 support
IPv6 resource records (A6, DNAME, etc.)
BIND version 9 development has been underwritten by the following
Sun Microsystems, Inc.
Compaq Computer Corporation
Process Software Corporation
Silicon Graphics, Inc.
Network Associates, Inc.
U.S. Defense Information Systems Agency
Stichting NLnet - NLnet Foundation
BIND 9.0.0b3 is the third public release of BIND 9 code. It will
be most useful to advanced users working with IPv6 or DNSSEC.
BIND 9.0.0b3 is not functionally complete, and is not a release
candidate for BIND 9.0.0. ISC anticipates at least one additional
beta release between now and June, when BIND 9.0.0 is scheduled to
ISC does not recommend using BIND 9.0.0b3 for "production"
We hope users of BIND 9.0.0b3 will provide feedback, bug fixes, and
enhancements. If you are not in a position to do so, it would
probably be better to wait until subsequent releases.
There have been many changes since beta 2; the highlights are:
The server now supports "views", a mechanism for answering
DNS queries differently to different requestors. This
will make split DNS setups much easier to build.
NOTIFY (RFC1996) has been implemented.
Basic support for validation of DNSSEC signatures has
been implemented. For details, see doc/misc/dnssec.
The "dig" and "host" tools have been completely rewritten
and are included in the base distribution.
Bug fixes. Most bugs reported against beta 2 have been
There are a few known bugs:
The option "query-source * port 53;" will not work as
expected. Instead of the wildcard address "*", you need
to use an explicit source IP address.
On some systems, IPv6 and IPv4 sockets interact in
unexpected ways. For details, see doc/misc/ipv6.
For a detailed list of user-visible changes since beta 2, see
the CHANGES file.
Some of the more significant items that will be implemented or
enhanced in a future beta are
Future releases will contain a lot more documentation,
but a preliminary version of the Administrator's
Reference Manual is in the doc/arm subdirectory in
HTML format. A plain text version will be added
in a future release.
BIND 9 currently requires a UNIX system with an ANSI C compiler,
basic POSIX support, and a good pthreads implementation.
We've had successful builds and tests on the following systems
COMPAQ Tru64 UNIX 4.0D
NetBSD-current (with "unproven" pthreads, foreground only)
Red Hat Linux 6.0, 6.1, 6.2
Solaris 2.6, 7, 8 (beta)
To build, just
Several environment variables that can be set before running
configure will affect compilation:
The C compiler to use. configure tries to figure
out the right one for supported systems.
C compiler flags. Defaults to include -g and/or -O2
as supported by the compiler.
System header file directories. Can be used to specify
where add-on thread or IPv6 support is, for example.
Defaults to empty string.
Any additional preprocessor symbols you want defined.
Defaults to empty string.
To build shared libraries, specify "--with-libtool" on the
configure command line.
If your operating system has integrated support for IPv6, it
will be used automatically. If you have installed KAME IPv6
separately, use "--with-kame[=PATH]" to specify its location.
To see additional configure options, run "configure --help".
"make install" will install "named" and the various BIND 9 libraries.
By default, installation is into /usr/local, but this can be changed
with the "--prefix" option when running "configure".
If you're planning on making changes to the BIND 9 source, you
should also "make depend". If you're using Emacs, you might find
"make tags" helpful.
Building with gcc is not supported, unless gcc is the vendor's usual
compiler (e.g. the various BSD systems, Linux).
Parts of the library can be tested by running "make test" from the
Bug Reports and Mailing Lists
Bugs reports should be sent to
bind9-bugs at isc.org
To join the BIND 9 Users mailing list, send mail to
bind9-users-request at isc.org
If you're planning on making changes to the BIND 9 source
code, you might want to join the BIND 9 Workers mailing list.
Send mail to
bind9-workers-request at isc.org
"named" command line options
-f Run in the foreground.
-g Run in the foreground and log
to stderr, ignoring any "logging"
statement in in the config file.
-t <directory> Chroot to <directory> before running.
-u <username> Run as user <username> after binding
to privileged ports.
Use of the "-t" option while still running as "root" doesn't
enhance security on most systems. The way chroot() is defined
allows a process with root privileges to escape the chroot jail.
The "-u" option is not currently useful on Linux kernels older
than 2.3.99-pre3. Linux threads are actually processes sharing a
common address space. An unfortunate side effect of this is that
some system calls, e.g. setuid() that in a typical pthreads
environment would affect all threads only affect the calling
thread/process on Linux. The good news is that BIND 9 uses the
Linux kernel's capability mechanism to drop all root powers except
the ability to bind() to a privileged port. 2.3.99-pre3 and later
kernels allow a process to say that its capabilities should be
retained after setuid(). If BIND 9 is compiled with 2.3.99-pre3 or
later kernel .h files, the "-u" option will cause the server to
run with the specified user id, but it will retain the capability
to bind() to privileged ports.
On systems with more than one CPU, the "-n" option should be used
to indicate how many CPUs there are.
Note to Programmers
The APIs for the libraries in BIND 9 are not yet frozen.
We expect the existing library interfaces in the release to be
quite stable, however, and unless we've specifically indicated that
an interface is temporary, we don't anticipate major changes in
More information about the bind-announce