BIND 9.7.3 Release Notes (5900-2505, October 2012)

Defects fixed in this release
This section discusses the defects fixed in the HP-UX 11i v3
Defects fixed in the HP-UX 11i v3 operating system
Table 3 Defects fixed in the HP-UX 11i v3 operating system
DescriptionDefect
BIND 9.3.2 lack features, especially enhanced DNSSEC
features.
QXCR1001064555
Heavy DNSSEC validation load causes a "Bad Cache"
assertion failure.
QXCR1001230666
Incorrect data handling causes named to terminate
unexpectedly.
QXCR1001231524
If a record with RDATA in excess of 65535 bytes is loaded
into a nameserver, a subsequent query for that record will
QXCR1001241557
cause named(1M) to exit. It was a design limitation in
named(1M) for handling a query in such scenario.
The named(1M) hangs by not responding to any queries
or control commands. The specific combinations of RDATA
QXCR1001243950
are loaded through cache/authoritative zone to named(1M)
and a subsequent query is made.
HP specific changes
JAGaf74567 : Add an Option statement to disable the EDNS feature on BIND9.
JAGaf74389 : DNS does not check for symbolic links.
JAGaf73027 : OpenSSL stub library and code changes for BIND-9.3.
JAGaf74395 : DNS does not check if dynamic DNS log files are linked. This is similar to
JAGaf74389 but checks for journal files.
JAGaf73245 : DoCoMo Performance changes on 11.11.
QXCR1000791343 build 64-bit named binary
JAGag41036 : named(1M) fails with an "out of memory" error message if the size of the cache
memory exceeds 1 GB.
Defects for which fixes were ported from ISC:
QXCR1000952300 The named daemon does not behave as expected for certain messages.
QXCR1000991848 The nameserver caches invalid responses from the additional section of the
response packet while processing recursive client queries.
QXCR1001009615 The nameserver sometimes returns invalid CNAME or DNAME responses
QXCR1001004094 The nameserver sometime returns invalid NXDOMAIN responses.
QXCR1000848700 Some DNS responses arriving at the host are not being delivered to the
/usr/sbin/named process but instead are directed to other processes running on the same host.
QXCR1000879111 The TCP accept() call fails to create the new connection socket and logs one
of the following errors:
internal accept: accept() failed: Too many open files internal_accept: fcntl() failed: Too many open
files
QXCR1000848714 The closure criteria for sockets lead to inconsistent states in the socket module.
QXCR1000886576 Using the rrset-order option with value fixed in the /etc/named.conf file displays
the following error message: rrset-order: order 'fixed' not fully implemented.
16 BIND 9.7.3 Release Notes