BIND 9.3.2 Release Notes (5900-2504, October 2012)

Table 9 Defects Fixed in the HP-UX in HP-UX 11i v1 and HP-UX 11i v2 operating systems (continued)
BIND 9.x does not handle AXFR/IXFR responses properly
in certain scenarios.
JAGag07595
BIND 9.3.2 must be enabled on the HP-UX 11i v1 and v2
operating systems.
JAGaf71605
Defects fixed in the HP-UX 11i v3 operating system
Table 10 lists the defects fixed in BIND 9.3.2 in the HP-UX 11i v3 operating system.
Table 10 Defects Fixed in the HP-UX 11i v3 Operating System
DescriptionIdentifier
Defects fixed in BIND 9.3.2(C.9.3.2.14.0)
If a record with RDATA in excess of 65535 bytes is loaded into a nameserver, a
subsequent query for that record will cause named(1M) to exit.It was a design
limitation in named(1M) for handling a query in such scenario.QXCR1001241531
named(1M) hangs, not responding to queries or control commands.Specific
combinations of RDATA are loaded through cache/authoritative zone to named(1M)
and a subsequent query is made.QXCR1001241535
Defects fixed in BIND 9.3.2 (C.9.3.2.13.0)
Incorrect data handling causes named to terminate unexpectedlyQXCR1001225472
Defects fixed in BIND 9.3.2 (C.9.3.2.12.0)
No new defects are fixed in this versionNone
Defects fixed in BIND 9.3.2 (C.9.3.2.11.0)
The named(1M) crashes, if subsequent queries are sent to cache an invalid record.QXCR1001180790
Defects fixed in BIND 9.3.2 (C.9.3.2.10.0)
When multiple threads try to acquire locks, there is a race, because the lock handling
mechanism is not synchronized. This causes the named daemon to abort.
QXCR1001118561
The named daemon allows specific packets to servers that causes named(1M) to
crash.
QXCR1001154168
Defects fixed in BIND 9.3.2 (C.9.3.2.9.0)
When the rndc utility is terminated, named(1M) does not shut down.QXCR1001090076
While reloading the server using rndc(1), named(1M) consumes more memory.QXCR1001079458
While using recursive resolvers with the DNSSEC validation option enabled, the
DNSSEC query to the nameserver returns a message of SERVFAIL or validation failure.
QXCR1001092088
When old signatures are retained in the named cache, validation failures occur.QXCR1001092086
Defects fixed in BIND 9.3.2 (C.9.3.2.8.0)
The named daemon does not behave as expected for certain messages.QXCR1000952300
The nameserver caches invalid responses from the additional section of the response
packet while processing recursive client queries.
QXCR1000991848
The nameserver sometimes returns invalid CNAME or DNAME responses.QXCR1001009615
The nameserver sometime returns invalid NXDOMAIN responses.QXCR1001004094
When named is started in a chroot environment, the following error is displayed:
open(/dev/poll) failed: No such file or directory
QXCR1000962881
Defects fixed in BIND 9.3.2 (C.9.3.2.6.0)
18 BIND 9.3.2 Release Notes