Fix chain system test for parent-centric resolver

The resolver now uses glue addresses from the parent side of a
zonecut without triggering an additional address lookup.  Update the
test involving a nameserver target name below a DNAME so that the
delegation does not use glue.

diff --git a/bin/tests/system/chain/ns1/root.db b/bin/tests/system/chain/ns1/root.db
index 1c99ba865ce3c2fb642847db09f3003b24f6fc09..bbb8de9d63c96f8f113d15b51a3b1526f218bab4 100644 (file)
--- a/bin/tests/system/chain/ns1/root.db
+++ b/bin/tests/system/chain/ns1/root.db
@@ -34,6 +34,8 @@ ns3.example.dname.    A       10.53.0.3
 jeff.dname.            NS      ns.jeff.dname.
 ns.jeff.dname.         A       10.53.0.3
 
+mutt.dname.             NS      ns.jeff.dname.
+
 domain0.nil.           NS      ns2.domain0.nil
 domain1.nil.           NS      ns2.domain0.nil
 domain2.nil.           NS      ns2.domain0.nil

diff --git a/bin/tests/system/chain/tests.sh b/bin/tests/system/chain/tests.sh
index 9346f2a4d2652097c58fe7c2a9edda40aa7d58b7..876b80698bb3fd70745f82e043a08b128e90f529 100644 (file)
--- a/bin/tests/system/chain/tests.sh
+++ b/bin/tests/system/chain/tests.sh
@@ -647,7 +647,7 @@ echo_i "checking handling of illegal NS below DNAME ($n)"
 ret=0
 $DIG $DIGOPTS @10.53.0.7 DNAME jeff.dname. >dig.out.ns7.1.$n 2>&1
 grep 'status: NOERROR' dig.out.ns7.1.$n >/dev/null 2>&1 || ret=1
-$DIG $DIGOPTS @10.53.0.7 NS jeff.dname. >dig.out.ns7.2.$n 2>&1
+$DIG $DIGOPTS @10.53.0.7 NS mutt.dname. >dig.out.ns7.2.$n 2>&1
 grep 'status: SERVFAIL' dig.out.ns7.2.$n >/dev/null 2>&1 || ret=1
 if [ $ret != 0 ]; then echo_i "failed"; fi
 status=$((status + ret))