QXCR1000848700 |
Some DNS responses arriving at the host are being
misdirected to the /usr/sbin/named process 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. |
| Defect fixed in BIND 9.3.2 (C.9.3.2.4.0 and C.9.3.2.5.0) |
QXCR1000841386 |
The
local IPv6 unicast addresses, such as fd00::/7,
are forwarded to the root server for resolution. |
| Defects fixed in BIND 9.3.2 (C.9.3.2.3.0) |
| 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. |
| Defects fixed in BIND 9.3.2 (C.9.3.2.2.0) |
| The
defects fixed in the C.9.3.2.2.0 version are the same as the defects
fixed in the C.9.3.2.1.0 version of BIND 9.3.2. |
| Defects fixed in BIND 9.3.2 (C.9.3.2.1.0) |
| JAGag41036 |
named(1M) fails with an "out of memory"
error message if the size of the cache memory exceeds 1 GB. |
| 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. |
