456. [bug] Stub zones were not resetting the refresh and expire
counters, loadtime or clearing the DNS_ZONE_REFRESH
(refresh in progress) flag upon successful update.
This disabled further refreshing of the stub zone,
causing it to eventually expire. [RT #300]
452. [bug] Warn if the unimplemented option statistics-file
is specified in named.conf. [RT #301]
453. [bug] Warn if the obsolete option maintain-ixfr-base
is specified in named.conf. [RT #306]
428. [bug] rbtdb.c:find_closest_nxt() erroneously returned
DNS_R_BADDB for nodes which had neither NXT nor SIG NXT
(e.g. glue). This could cause SERVFAILs when
generating negative responses in a secure zone.
Log Message:
435. [bug] dns_zone_dump() overwrote existing zone files
rather than writing to a temporary file and
renaming. This could lead to empty or partial
zone files being left around in certain error
conditions involving the initial transfer of a
slave zone, interfering with subsequent server
startup. [RT #282]
427. [bug] Avoid going into an infinite loop when the validator
gets a negative response to a key query where the
records are signed by the missing key.
(Pulled up despite the fact that I don't fully understand how the
fix works; I expect Brian to explain it when he comes back from Europe
and/or by adding comments)
436. [bug] If recvmsg() returned EHOSTUNREACH or ENETUNREACH,
which sometimes happens on Linux, named would enter
a busy loop. Also, unexpected socket errors were
not logged at a high enough logging level to be
useful in diagnosing this situation. [RT #275]
424. [bug] notify_createmessage() could trigger an assertion failure
when creating the notify message failed, e.g. due to
corrupt zones with multiple SOA records. [RT #279]
330. [func] New function isc_log_wouldlog().
(note: #330 is out of place in CHANGES, because it's new in rc4, but if
it was in the place that 330 is supposed to go, no one would see it. So,
leave it at the top)
399. [bug] When reloading the server with a config file
containing a syntax error, it could catch an
assertion failure trying to perform zone
maintenance on, or sending notifies from,
tentatively created zones whose views were
never fully configured and lacked an address
database and request manager.
