BIND 9.7.3 Release Notes HP-UX 11i v3 (5900-3140, July 2013)

Table 2 BIND 9.7.3 Manpage (continued)
DescriptionManpage
Configuration file for name daemonnamed.conf(4)
Configuration file rndcrndc.conf(4)
The nslookup(1), dig(1M), and host(1) can be used to troubleshoot BIND 9.7.3. For
detailed information and examples of utilities and commands listed in Table 2 (page 15), see the
respective manpages.
Product documentation
For more information on configuring and administering BIND, see the HP-UX IP Address and Client
Management Services Administrator’s Guide at
http://www.hp.com/go/hpux-networking-docs —> select the operating system version used.
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
DescriptionIdentifier
Defects fixed in BIND 9.7.3 (C.9.7.3.2.0)
CVE-2013-2266: A maliciously crafted regular expression can cause Memory
Exhaustion in named(1M).QXCR1001275143
Defects fixed in BIND 9.7.3 (C.9.7.3.1.0)
It is a design limitation in named(1M) due to which the information can be prolonged
in the cache beyond the period supposedly allowed by the TTL value, causing
named(1M) to potentially return incorrect answers.QXCR1001248763
It is a limitation in control scripts of named(1m) due to which named.64 is not getting
killed.QXCR1001252456
DescriptionIdentifier
Defects fixed in BIND 9.7.3 (C.9.7.3.0.0)
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 cause named(1M) to exit. It was a design
limitation in named(1M) for handling a query in such scenario.QXCR1001248763
The named(1M) hangs by not responding to any queries or control commands. The
specific combinations of RDATA are loaded through cache/authoritative zone to
named(1M) and a subsequent query is made.QXCR1001243950
HP specific changes
JAGaf74567 : Add an Option statement to disable the EDNS feature on BIND9.
JAGaf74389 : DNS does not check for symbolic links.
16 BIND 9.7.3 Release Notes