BIND 9	BIND version 9 is a major rewrite of nearly all aspects of the	underlying BIND architecture. Some of the important features of	BIND 9 are:	- DNS Security	DNSSEC (signed zones)	TSIG (signed DNS requests)	- IP version 6	Answers DNS queries on IPv6 sockets	IPv6 resource records (A6, DNAME, etc.)	Bitstring Labels	Experimental IPv6 Resolver Library	- DNS Protocol Enhancements	IXFR, DDNS, Notify, EDNS0	Improved standards conformance	- Views	One server process can provide multiple "views" of	the DNS namespace, e.g. an "inside" view to certain	clients, and an "outside" view to others.	- Multiprocessor Support	- Improved Portability Architecture	BIND version 9 development has been underwritten by the following	organizations:	Sun Microsystems, Inc.	Hewlett Packard	Compaq Computer Corporation	IBM	Process Software Corporation	Silicon Graphics, Inc.	Network Associates, Inc.	U.S. Defense Information Systems Agency	USENIX Association	Stichting NLnet - NLnet Foundation BIND 9.1.3	BIND 9.1.3 is a maintenance release, containing fixes for	a number of bugs in 9.1.2 but no new features.	Features introduced in 9.1.0 included: - Many BIND 8 features previously unimplemented in BIND 9, including domain-specific forwarding, the $GENERATE master file directive, and the "blackhole", "dialup", and "sortlist" options - Forwarding of dynamic update requests; this is enabled by the "allow-update-forwarding" option - A new, simplified database interface and a number of sample drivers based on it; see doc/misc/sdb for details - Support for building single-threaded servers for environments that do not supply POSIX threads - New configuration options: "min-refresh-time", "max-refresh-time", "min-retry-time", "max-retry-time", "additional-from-auth", "additional-from-cache", "notify explicit" - Faster lookups, particularly in large zones.	BIND 9.1 also includes experimental implementations of a	number of DNS protocols extensions still under development	in the IETF. These include transparent processing of	unknown RR types and use of the EDNS "DNSSEC OK" bit to	explicitly enable DNSSEC processing in responses.	Cryptographic operations are now based on the OpenSSL	library instead of DNSsafe.	BIND 9.1 is primarily a name server software distribution.	In addition to the name server, it also includes a new	lightweight stub resolver library and associated resolver	daemon that fully support forward and reverse lookups of both	IPv4 and IPv6 addresses. This library is still considered	experimental and is not a complete replacement for the BIND 8	resolver library. Applications that use the BIND 8 res_*	functions to perform DNS lookups or dynamic updates still need	to be linked against the BIND 8 libraries. For DNS lookups,	they can also use the new "getrrsetbyname()" API.	BIND 9.1 is capable of acting as an authoritative server	for DNSSEC secured zones. This functionality is believed to	be stable and complete except for lacking support for wildcard	records in secure zones.	When acting as a caching server, BIND 9.1 can be configured	to perform DNSSEC secure resolution on behalf of its clients.	This part of the DNSSEC implementation is still considered	experimental. For detailed information about the state of the	DNSSEC implementation, see the file doc/misc/dnssec.	There are a few known bugs:	On some systems, IPv6 and IPv4 sockets interact in	unexpected ways. For details, see doc/misc/ipv6.	To reduce the impact of these problems, the server	no longer listens for requests on IPv6 addresses	by default. If you need to accept DNS queries over	IPv6, you must specify "listen-on-v6 { any; };"	in the named.conf options statement.	There are known problems with thread signal handling	under Solaris 2.6 and BSD/OS. We recommend disabling	threads with "configure --disable-threads" on these	platforms.	FreeBSD prior to 4.2 (and 4.2 if running as non-root)	and OpenBSD prior to 2.8 log messages like	"fcntl(8, F_SETFL, 4): Inappropriate ioctl for device".	This is due to a bug in "/dev/random" and impacts the	server's DNSSEC support.	--with-libtool does not work on AIX.	A bug in the Windows 2000 DNS server can cause zone transfers	from a BIND 9 server to a W2K server to fail. For details,	see the "Zone Transfers" section in doc/misc/migration.	For a detailed list of user-visible changes from	previous releases, see the CHANGES file. Building	BIND 9 currently requires a UNIX system with an ANSI C compiler,	basic POSIX support, and a 64 bit integer type.	We've had successful builds and tests on the following systems:	AIX 4.3	COMPAQ Tru64 UNIX 4.0D	COMPAQ Tru64 UNIX 5 (with IPv6 EAK)	FreeBSD 3.4-STABLE, 3.5, 4.0, 4.1	HP-UX 11	IRIX64 6.5	NetBSD 1.5 (with unproven-pthreads-0.17)	Red Hat Linux 6.0, 6.1, 6.2, 7.0	Solaris 2.6, 7, 8	Additionally, we have unverified reports of success building	previous versions of BIND 9 from users of the following systems:	AIX 5L	Slackware Linux 7.0 with 2.4.0-test6 kernel and glibc 2.1.3	Slackware Linux 7.0.1 with glibc 2.1.3	Red Hat Linux 7.1	OpenBSD 2.6, 2.8, -current	UnixWare 7.1.1	HP-UX 10.20	To build, just	./configure	make	Do not use a parallel "make".	Several environment variables that can be set before running	configure will affect compilation: CC	The C compiler to use.	configure tries to figure	out the right one for supported systems. CFLAGS	C compiler flags. Defaults to include -g and/or -O2	as supported by the compiler. STD_CINCLUDES	System header file directories. Can be used to specify	where add-on thread or IPv6 support is, for example.	Defaults to empty string. STD_CDEFINES	Any additional preprocessor symbols you want defined.	Defaults to empty string.	To build shared libraries, specify "--with-libtool" on the	configure command line.	To build without multithreading, specify "--disable-threads"	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.	"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".	You may specify the option "--sysconfdir" to set the directory	where configuration files like "named.conf" go by default,	and "--localstatedir" to set the default parent directory	of "run/named.pid". For backwards compatibility with BIND 8,	--sysconfdir defaults to "/etc" and --localstatedir defaults to	"/var" if no --prefix option is given. If there is a --prefix	option, sysconfdir defaults to "$prefix/etc" and localstatedir	defaults to "$prefix/var".	To see additional configure options, run "configure --help".	Note that the help message does not reflect the BIND 8	compatibility defaults for sysconfdir and localstatedir.	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).	A limited test suite can be run with "make test". Many of	the tests require you to configure a set of virtual IP addresses	on your system, and some require Perl; see bin/tests/system/README	for details.	Linux systems do not provide useful core dumps for multithreaded	programs unless the kernel patch in contrib/linux/coredump-patch	has been applied. We recommend all Linux users to install this	patch so that any server crashes can be properly diagnosed. Documentation	The BIND 9 Administrator Reference Manual is included with the	source distribution in DocBook XML and HTML format, in the	doc/arm directory.	Some of the programs in the BIND 9 distribution have man pages	under the doc/man directory. In particular, the command line	options of "named" are documented in doc/man/bind/named.8.	There is now also a set of man pages for the lwres library.	The man pages are currently not installed automatically by	"make install".	If you are upgrading from BIND 8, please read the migration	notes in doc/misc/migration. If you are upgrading from	BIND 4, read doc/misc/migration-4to9. Bug Reports and Mailing Lists	Bugs reports should be sent to	bind9-bugs@isc.org	To join the BIND 9 Users mailing list, send mail to	bind9-users-request@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@isc.org