BIND 9.6.0b1 is now available. - DNS

This is a discussion on BIND 9.6.0b1 is now available. - DNS ; BIND 9.6.0b1 is now available. BIND 9.6.0b1 is a beta release for BIND 9.6.0. Please as a minimum perform a test build on your operating system. We don't have test platforms for every operating system and sometimes we accidently break ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: BIND 9.6.0b1 is now available.

  1. BIND 9.6.0b1 is now available.

    BIND 9.6.0b1 is now available.

    BIND 9.6.0b1 is a beta release for BIND 9.6.0.

    Please as a minimum perform a test build on your operating
    system. We don't have test platforms for every operating
    system and sometimes we accidently break builds. Now is
    the time to tell us about that.

    Bugs should be reported to bind9-bugs@isc.org.

    BIND 9.6 has a number of new features over 9.5, including:

    Full NSEC3 support

    Automatic zone re-signing

    New update-policy methods tcp-self and 6to4-self

    BIND 9.6.0b1 can be downloaded from

    ftp://ftp.isc.org/isc/bind9/9.6.0b1/bind-9.6.0b1.tar.gz

    The PGP signature of the distribution is at

    ftp://ftp.isc.org/isc/bind9/9.6.0b1/...0b1.tar.gz.asc
    ftp://ftp.isc.org/isc/bind9/9.6.0b1/....gz.sha256.asc
    ftp://ftp.isc.org/isc/bind9/9.6.0b1/....gz.sha512.asc

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

    A binary kit for Windows XP and Window 2003 is at

    ftp://ftp.isc.org/isc/bind9/9.6.0b1/BIND9.6.0b1.zip
    ftp://ftp.isc.org/isc/bind9/9.6.0b1/....0b1.debug.zip

    The PGP signature of the binary kit for Windows XP and Window 2003 is at

    ftp://ftp.isc.org/isc/bind9/9.6.0b1/BIND9.6.0b1.zip.asc
    ftp://ftp.isc.org/isc/bind9/9.6.0b1/...zip.sha256.asc
    ftp://ftp.isc.org/isc/bind9/9.6.0b1/...zip.sha512.asc
    ftp://ftp.isc.org/isc/bind9/9.6.0b1/....debug.zip.asc
    ftp://ftp.isc.org/isc/bind9/9.6.0b1/...zip.sha256.asc
    ftp://ftp.isc.org/isc/bind9/9.6.0b1/...zip.sha512.asc

    Changes since BIND 9.6.0a1

    --- 9.6.0b1 released ---

    2481. [bug] rbtdb.c:matchparams() failed to handle NSEC3 chain
    collisions. [RT #18812]

    2480. [bug] named could fail to emit all the required NSEC3
    records. [RT #18812]

    2479. [bug] xfrout:covers was not properly initalized. [RT #18801]

    2478. [bug] 'addresses' could be used uninitalized in
    configure_forward(). [RT #18800]

    2477. [bug] dig: the global option to print the command line is
    +cmd not print_cmd. Update the output to reflect
    this. [RT #17008]

    2476. [doc] ARM: improve documentation for max-journal-size and
    ixfr-from-differences. [RT #15909] [RT #18541]

    2475. [bug] LRU cache cleanup under overmem condition could purge
    particular entries more aggressively. [RT #17628]

    2474. [bug] ACL structures could be allocated with insufficient
    space, causing an array overrun. [RT #18765]

    2473. [port] linux: raise the limit on open files to the possible
    maximum value before spawning threads; 'files'
    specified in named.conf doesn't seem to work with
    threads as expected. [RT #18784]

    2472. [port] linux: check the number of available cpu's before
    calling chroot as it depends on "/proc". [RT #16923]

    2471. [bug] named-checkzone was not reporting missing mandatory
    glue when sibling checks were disabled. [RT #18768]

    2470. [bug] Elements of the isc_radix_node_t could be incorrectly
    overwritten. [RT# 18719]

    2469. [port] solaris: Work around Solaris's select() limitations.
    [RT #18769]

    2468. [bug] Resolver could try unreachable servers multiple times.
    [RT #18739]

    2467. [bug] Failure of fcntl(F_DUPFD) wasn't logged. [RT #18740]

    2466. [doc] ARM: explain max-cache-ttl 0 SERVFAIL issue.
    [RT #18302]

    2465. [bug] Adb's handling of lame addresses was different
    for IPv4 and IPv6. [RT #18738]

    2464. [port] linux: check that a capability is present before
    trying to set it. [RT #18135]

    2463. [port] linux: POSIX doesn't include the IPv6 Advanced Socket
    API and glibc hides parts of the IPv6 Advanced Socket
    API as a result. This is stupid as it breaks how the
    two halves (Basic and Advanced) of the IPv6 Socket API
    were designed to be used but we have to live with it.
    Define _GNU_SOURCE to pull in the IPv6 Advanced Socket
    API. [RT #18388]

    2462. [doc] Document -m (enable memory usage debugging)
    option for dig. [RT #18757]

    2461. [port] sunos: Change #2363 was not complete. [RT #17513]

    --- 9.6.0a1 released ---



  2. Re: BIND 9.6.0b1 is now available.

    "Mark Andrews" wrote in message
    news:gf0bis$1cq9$1@sf1.isc.org...
    > BIND 9.6.0b1 is now available.


    Compiler warnings issued (same warnings issued about 10 times):

    .../../lib/isc/libisc.a(socket.o): In function `setup_watcher':
    socket.c.text+0x4eb4): warning: warning: epoll_create is not implemented
    and will always fail
    .../../lib/isc/libisc.a(socket.o): In function `watch_fd':
    socket.c.text+0x8ac3): warning: warning: epoll_ctl is not implemented and
    will always fail
    .../../lib/isc/libisc.a(socket.o): In function `isc__socketmgr_waitevents':
    socket.c.text+0x84a1): warning: warning: epoll_wait is not implemented and
    will always fail

    Environment: Linux (kernel 2.6.27.4)
    Configuration:

    configure --prefix=/usr --with-openssl=/usr/local/ssl --mandir=/usr/man --wi
    th-run-dir=/var/run --sysconfdir=/etc --localstatedir=/var CFLAGS=
    "-DDIG_SIGCHASE=1"


    Do we have a problem here, or may this be safely ignored?




  3. Re: BIND 9.6.0b1 is now available.

    At Fri, 7 Nov 2008 03:08:00 -0800,
    "D. Stussy" wrote:

    > Compiler warnings issued (same warnings issued about 10 times):
    >
    > ../../lib/isc/libisc.a(socket.o): In function `setup_watcher':
    > socket.c.text+0x4eb4): warning: warning: epoll_create is not implemented
    > and will always fail
    > ../../lib/isc/libisc.a(socket.o): In function `watch_fd':
    > socket.c.text+0x8ac3): warning: warning: epoll_ctl is not implemented and
    > will always fail
    > ../../lib/isc/libisc.a(socket.o): In function `isc__socketmgr_waitevents':
    > socket.c.text+0x84a1): warning: warning: epoll_wait is not implemented and
    > will always fail


    (snip)

    > Do we have a problem here, or may this be safely ignored?


    I've not seen these warnings, but if the OS really doesn't support
    epoll as the warnings indicate, executables won't work anyway. On the
    other hand, if they work you may be able to ignore the warnings. A
    workaround in the former case would be to disable epoll at compilation
    time using the '--disable-epoll' configure option.

    ---
    JINMEI, Tatuya
    Internet Systems Consortium, Inc.


+ Reply to Thread