[Bug 1361] New: Tests fail when 1.0.0.127.in-addr.arpa. resolves - lyskomd-qa

20 Jun 2004


      http://bugzilla.lysator.liu.se/show_bug.cgi?id=1361
Summary: Tests fail when 1.0.0.127.in-addr.arpa. resolves
           Product: lyskomd
           Version: 2.1.2
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: testsuite
        AssignedTo: ceder@lysator.liu.se
        ReportedBy: byers@lysator.liu.se
         QAContact: lyskomd-qa@lists.lysator.liu.se
When 1.0.0.127.in-addr.arpa resolves, several tests fail. I get errors like this:
FAIL: looking for :5 6 6 1 2 0H 13Hbar@127.0.0.1 (unexpected line MRK:client1:
:5 6 6 1 2 0H 13Hbar@localhost)
FAIL: looking for :5 6 6 1 2 0H 13Hbar@127.0.0.1 (unexpected line MRK:client1:
=1041)
FAIL: looking for :5 6 6 1 2 0H 13Hbar@127.0.0.1 (timeout)
When you install BIND 9 in Debian Gnu/Linux, the default configuration includes
the 127.in-addr.arpa zone, and 1.0.0.127.in-addr.arpa resolves to localhost.
It would be nice if the test suite could do the appropriate DNS lookup before
running any test cases, and test cases use the value returned by the DNS lookup
instead of hard coding 127.0.0.1.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.