473. [bug] nsupdate overran the end of the list of name servers
when no servers could be reached, typically causing
it to print the error message "dns_request_create:
not implemented".
459. [bug] Nslookup processed the set command incorrectly.
458. [bug] Nslookup didn't properly check class and type values.
[RT #305]
457. [bug] Dig/host/hslookup didn't properly handle connect
timeouts in certain situations, causing an
unnecessary warning message to be printed.
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]
Brian Wellington
Michael Graff