HPUX-Name Server Release Notes (761997-001, March 2014)

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.
QXCR1000893386 The return values from the OpenSSL library functions are not checked properly
in DNS code.
QXCR1000924015 "DNSSEC Lookaside Validation (DLV) processing does not handle unknown
signature algorithms correctly."
QXCR1000841386 "The local IPv6 unicast addresses, such as fd00:: /7, are forwarded to the
root server for resolution."
QXCR1000821672 Forgery resilience needs more improvements.
QXCR1000577501 The rndc(1) recursing output file named.recursing contains old data.
QXCR1000791343 named(1M) fails with an out of memory error message.
JAGag45362 Query ID generation is cryptographically weak.
JAGag32951 named(1M) does not handle queries of type ANY properly.
JAGag32950 named (1M) unexpectedly aborts under certain circumstances.
QXCR1001231524 Handling of zero length rdata cause named to terminate unexpectedly in
BIND9.7.3
QXCR1001230666 Heavy DNSSEC Validation Load Can Cause an Assertion Failure in BIND9.7
QXCR1001241557 RDATA in excess of 65535 bytes cause named to exit in BIND 9.7.3
New deliverables in BIND 9.7.3 and their locations
The following binaries have been added newly in BIND 9.7.3. See individual manpages for more
information.
Binaries
/usr/sbin:
• dnssec-dsfromkey
• dnssec-revoke
• dnssec-settime
• arpaname
18 BIND 9.7.3 release notes