Log message:
Automatically include pthread variables. Bump revision as it might
change some of the binaries.

Log message:
Upgrade BIND to 9.4.0.
I won't attempt to summarize 221 lines of changes in README here.

Log message:
Fix permission problems:
- "share/doc/bind9" shouldn't be group-writable.
- "share/doc/bind9/arm/Bv9ARM.pdf" shouldn't be executable.

Bump package revision because of these fixes.

Log message:
Update to 9.3.4
Lots of changes, see http://www.isc.org/sw/bind/view/?release=9.3.4#RELEASE
for all the details:

In brief:
2126.	[security]	Serialise validation of type ANY responses.

2124.	[security]	It was possible to dereference a freed fetch
context.

2089.	[security]	Raise the minimum safe OpenSSL versions to
OpenSSL 0.9.7l and OpenSSL 0.9.8d.  Versions
prior to these have known security flaws which
are (potentially) exploitable in named.

2088.	[security]	Change the default RSA exponent from 3 to 65537.

2066.   [security]      Handle SIG queries gracefully.

1941.   [bug]           ncache_adderesult() should set eresult even if no
rdataset is passed to it.

Log message:
Disable threading on sparc and sparc64
sparc64 tested successfully by Volkmar Seifert <vs@nifelheim.info>

OK'd by (and sparc included per suggestion of) martin@

Log message:
Don't install doc/*/Makefile{,.in} as theses do not pass the CHECK_WRKREF
check. Also don't install utility perl scripts for building the
docs. Use pax to install all the doc files in one go.

Bump PKGREVISION to 3 for the PLIST changes.

Log message:
Fixes for CVE-2006-4095 and CVE-2006-4096 from bind-9.3.2-P1

* Assertion failure in ISC BIND SIG query processing (CVE-2006-4095)

- Recursive servers
Queries for SIG records will trigger an assertion failure if more
than one RRset is returned. However exposure can be minimized by
restricting which sources can ask for recursion.

- Authoritative servers
If a nameserver is serving a RFC 2535 DNSSEC zone and is queried
for the SIG records where there are multiple RRsets, then the
named program will trigger an assertion failure when it tries
to construct the response.

* INSIST failure in ISC BIND recursive query handling code (CVE-2006-4096)

It is possible to trigger an INSIST failure by sending enough
recursive queries such that the response to the query arrives after
all the clients waiting for the response have left the recursion
queue. However exposure can be minimized by restricting which sources
can ask for recursion.

Log message:
Added the relevant variables to BUILD_DEFS.

Log message:
Bump PKGREVISION to 1.

Fix build on NetBSD/sparc64 3.x: sync CPP symbols usage between
struct addrinfo definition and its usage in getaddrinfo().

While here define struct addrinfo's pad members the same way as in
NetBSD's /usr/include/netbsd.h and sync code in
lib/bind/irs/getaddrinfo.c:getaddrinfo().

This had been reported to bind9-bugs at isc dot org.

Log message:
Update bind to 9.3.2.

Changes are huge, so please see http://www.isc.org/sw/bind/bind9.3.php.