Announcing the release of BIND 9.1.1

Wednesday Mar 28th 2001 by ServerWatch Staff

BIND 9.1.1 has been released. This is a maintenance release, fixing a number of bugs in BIND 9.1.0. There are no new features.

BIND 9.1.1 has been released. This is a maintenance release, fixing a number of bugs in BIND 9.1.0. There are no new features.

BIND 9.1.1 can be downloaded from

The PGP signature of the distribution is at

The signature was generated with the ISC public key, which is available at .

A list of changes made since 9.1.0 follows. For earlier changes, see the file CHANGES in the distribution.


        --- 9.1.1 released ---

        --- 9.1.1rc7 released ---

 791.   [bug]           The control channel did not work over IPv6.

 790.   [bug]           Wildcards created using dynamic update or IXFR
                        could fail to match. [RT #1111]
 787.   [bug]           The DNSSEC tools failed to downcase domain
                        names when mapping them into file names.

 786.   [bug]           When DNSSEC signing/verifying data, owner names were
                        not properly downcased.

        --- 9.1.1rc6 released ---

 785.   [bug]           A race condition in the resolver could cause
                        an assertion failure. [RT #673, #872, #1048]

 784.   [bug]           nsupdate and other programs would not quit properly
                        if some signals were blocked by the caller. [RT #1081]

 783.   [bug]           Following CNAMEs could cause an assertion failure
                        when either using an sdb database or under very
                        rare conditions.

 780.   [bug]           Error handling code dealing with out of memory or
                        other rare errors could lead to assertion failures
                        by calling functions on unitialized names. [RT #1065]

        --- 9.1.1rc5 released ---

 778.   [bug]           When starting cache cleaning, cleaning_timer_action()
                        returned without first pausing the iterator, which
                        could cause deadlock. [RT #998]

 777.   [bug]           An empty forwarders list in a zone failed to override
                        global forwarders. [RT #995]
 775.   [bug]           Address match lists with invalid netmasks caused
                        the configuration parser to abort with an assertion
                        failure. [RT #996]
 772.   [bug]           Owner names could be incorrectly omitted from cache
                        dumps in the presence of negative caching entries.  
                        [RT #991]

 686.   [bug]           dig and nslookup can now be properly aborted during
                        blocking operations. [RT #568]
        --- 9.1.1rc4 released ---

 767.   [bug]           The configuration parser handled invalid ports badly.
                        [RT #961]

 766.   [bug]           A few cases in query_find() could leak fname.
                        This would trigger the mpctx->allocated == 0   
                        assertion when the server exited.
                        [RT #739, #776, #798, #812, #818, #821, #845,
                        #892, #935, #966]
 759.   [bug]           The resolver didn't turn off "avoid fetches" mode
                        when restarting, possibly causing resolution
                        to fail when it should not.  This bug only affected
                        platforms which support both IPv4 and IPv6. [RT #927]
 758.   [bug]           The "avoid fetches" code did not treat negative   
                        cache entries correctly, causing fetches that would
                        be useful to be avoided.  This bug only affected

                        platforms which support both IPv4 and IPv6. [RT #927]

 756.   [bug]           dns_zone_load() could "return" success when no master
                        file was configured.
 755.   [bug]           Fix incorrectly formatted log messages in zone.c.
 709.   [bug]           ANY or SIG queries for data with a TTL of 0
                        would return SERVFAIL. [RT #620]

        --- 9.1.1rc3 released ---
 754.   [bug]           Certain failure conditions sending UDP packets
                        could cause the server to retry the transmission
                        indefinitely. [RT #902]

 753.   [bug]           dig, host, and nslookup would fail to contact a
                        remote server if getaddrinfo() returned an IPv6
                        address on a system that doesn't support IPv6.
                        [RT #917]

 750.   [bug]           A query should not match a DNAME whose trust level
                        is pending.  [RT #916]

 749.   [bug]           When a query matched a DNAME in a secure zone, the
                        server did not return the signature of the DNAME.
                        [RT #915]
 747.   [bug]           The code to determine whether an IXFR was possible   
                        did not properly check for a database that could
                        not have a journal. [RT #865, #908]
 746.   [bug]           The sdb didn't clone rdatasets properly, causing
                        a crash when the server followed delegations. [RT #905]

 744.   [bug]           When returning DNS_R_CNAME or DNS_R_DNAME as the
                        result of an ANY or SIG query, the resolver failed
                        to setup the return event's rdatasets, causing an

                        assertion failure in the query code.  [RT #881]  
 743.   [bug]           Receiving a large number of certain malformed
                        answers could cause named to stop responding.
                        [RT #861]

 742.   [bug]           dig +domain did not work. [RT #850]
 738.   [bug]           If a non-threadsafe sdb driver supported AXFR and
                        received an AXFR request, it would deadlock or die
                        with an assertion failure. [RT #852]
 737.   [port]          stdtime.c failed to compile on certain platforms.

 648.   [port]          Add support for pre-RFC2133 IPv6 implementations.

        --- 9.1.1rc2 released ---

 733.   [bug]           Reference counts of dns_acl_t objects need to be
                        locked but were not. [RT #801, #821]
 708.   [bug]           When building with --with-openssl, the openssl headers
                        included with BIND 9 should not be used. [RT #702]
        --- 9.1.1rc1 released ---
 729.   [port]          pthread_setconcurrency() needs to be called on Solaris.
 727.   [port]          Work around OS bug where accept() succeeds but
                        fails to fill in the peer address of the accepted
                        connection, by treating it as an error rather than
                        an assertion failure. [RT #809]
 723.   [bug]           Referrals whose NS RRs had a 0 TTL caused the resolver
                        to return DNS_R_SERVFAIL. [RT #783]
 720.   [bug]           Server could enter infinite loop in
                        dispatch.c:do_cancel(). [RT #733]

 719.   [bug]           Rapid reloads could trigger an assertion failure.
                        [RT #743, #763]

 717.   [bug]           Certain TKEY processing failure modes could
                        reference an uninitialized variable, causing the
                        server to crash. [RT #750]
 716.   [bug]           The first line of a  master file was lost if
                        an origin was specified. [RT #744]

 715.   [bug]           Resolving some A6 chains could cause an assertion
                        failure in adb.c. [RT #738]
 711.   [bug]           The libisc and liblwres implementations of
                        inet_ntop contained an off by one error.
 706.   [bug]           Zones with an explicit "allow-update { none; };"  
                        were considered dynamic and therefore not reloaded
                        on SIGHUP or "rndc reload".
 700.   [bug]            range check was wrong. [RT #688]
 698.   [bug]           Aborting nsupdate with ^C would lead to several
                        race conditions.
 699.   [bug]           The lexer mishandled empty quoted strings. [RT #694]

 694.   [bug]            did not produce the last entry.
                        [RT #682, #683]
 693.   [bug]           An empty lwres statement in named.conf caused
                        the server to crash while loading.

 692.   [bug]           Deal with systems that have getaddrinfo() but not
                        gai_strerror(). [RT #679]
 691.   [bug]           Configuring per-view forwarders caused an assertion
                        failure. [RT #675, #734]
        --- 9.1.0 released ---


Mobile Site | Full Site
Copyright 2017 © QuinStreet Inc. All Rights Reserved