bind9/bin/tests/system/stub
Diego Fronza b0f61f92b3 Added test for the proposed fix
This test is very simple, two nameserver instances are created:
    - ns4: master, with 'minimal-responses yes', authoritative
        for example. zone
    - ns5: slave, stub zone

The first thing verified is the transfer of zone data from master
to slave, which should be saved in ns5/example.db.

After that, a query is issued to ns5 asking for target.example.
TXT, a record present in the master database with the "test" string
as content.

If that query works, it means stub zone successfully request
nameserver addresses from master, ns4.example. A/AAAA

The presence of both A/AAAA records for ns4 is also verified in the
stub zone local file, ns5/example.db.
2020-10-21 12:03:42 -03:00
..
ns1 further tidying of primary/secondary terminology in system tests 2020-07-01 11:12:12 -07:00
ns2 further tidying of primary/secondary terminology in system tests 2020-07-01 11:12:12 -07:00
ns3 further tidying of primary/secondary terminology in system tests 2020-07-01 11:12:12 -07:00
ns4 Added test for the proposed fix 2020-10-21 12:03:42 -03:00
ns5 Added test for the proposed fix 2020-10-21 12:03:42 -03:00
clean.sh Added test for the proposed fix 2020-10-21 12:03:42 -03:00
knowngood.dig.out.norec Trailing whitespace trimmed. Perhaps running "perl util/spacewhack.pl in your 2000-08-01 01:33:37 +00:00
knowngood.dig.out.rec 3593. [func] Update EDNS processing to better track remote server 2013-06-12 11:31:30 +10:00
setup.sh Added test for the proposed fix 2020-10-21 12:03:42 -03:00
tests.sh Added test for the proposed fix 2020-10-21 12:03:42 -03:00