Post-build test fail on BIND 9, old system - DNS

This is a discussion on Post-build test fail on BIND 9, old system - DNS ; Hello, Due to recent exploits I have to upgrade to the newest version of BIND. My DNS server is a quite old machine, running BIND 4 on Solaris 2.5.1. I didn't upgrade because the OS lacks many libraries and syscalls ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Post-build test fail on BIND 9, old system

  1. Post-build test fail on BIND 9, old system

    Hello,
    Due to recent exploits I have to upgrade to the newest version of BIND.
    My DNS server is a quite old machine, running BIND 4 on Solaris 2.5.1. I
    didn't upgrade because the OS lacks many libraries and syscalls and it's
    hard to get newest versions of programs compiled under it. The machine
    is about to be completely replaced by a new one running under Solaris 9,
    but the migration is delaying due to various reasons and it can take
    several months until it is finished. However, because of the recent
    vulnerabilities, BIND has to be upgraded *now*.

    And here I have some problem. I successfully compiled BIND 9.5.0-P1 on
    my system, but when I run "make test" after the build, some of the tests
    fail. The tests that fail are: cacheclean, forward, lwresd, rrsetorder
    and upforwd (the same applies for BIND 9.4.2-P1). My question is: how
    severe is this? Can something bad happen if I run the nameserver with
    these tests failing or may I safely ignore this? I can send the detailed
    test output if needed.

    What else can I do to make BIND work all OK?
    --
    Regards,
    Jaroslaw Rafa
    raj@ap.krakow.pl


  2. Re: Post-build test fail on BIND 9, old system

    Jaros?aw Rafa wrote:

    > And here I have some problem. I successfully compiled BIND 9.5.0-P1 on
    > my system, but when I run "make test" after the build, some of the tests
    > fail. The tests that fail are: cacheclean, forward, lwresd, rrsetorder
    > and upforwd (the same applies for BIND 9.4.2-P1). My question is: how
    > severe is this? Can something bad happen if I run the nameserver with
    > these tests failing or may I safely ignore this? I can send the detailed
    > test output if needed.


    Sheese, trying to get anything to run under Solaris 2.5.1 is going to be an
    uphill battle.

    Is there any way to just try to run what was built and ignore the tests?

    Reason I'm saying that, not sure why but there is a couple spots in the test
    suite for BIND 9.5.0-P1 that has "grep -q" hardcoded which causes several
    failures under Solaris. As far as I can tell, -q (for quiet) is only
    supported on the gnu grep (ggrep).

    Besides causing some tests to get bypassed, I think it does eventually fail
    altogether because of something missing from the grep output (maybe wrong
    about that).

    So either try to build the gnu grep and replace the grep binary on your box
    or search around the bin/tests directories and edit the -q off the grep
    calls.

    One other note for those building on Solaris 10 and have zones configured
    and running, there is another bug or oversight in the test suite when you
    bring up the interfaces for the phony 10.53.0 addresses, all that works but
    when you clean up and bring them down using the ifconfig.sh script, you'll
    lose all the 127.0.0.1 localhosts on the interfaces at the same time. Is a
    minor issue, can easily be fixed without rebooting but had me stumped for a
    bit when some things running just stopped working.

    -bruce
    bje@ripco.com



+ Reply to Thread