From df81adba8858eaad9786ad359341b6df3a16783b Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Tue, 5 Mar 2024 15:26:37 +0100 Subject: [PATCH] ci: disable test that is now answered by knot dig question with DNSSEC on will now be proxied upstream, i.e. to the test knot server. This leads to different results, but the result isn't tha tinteresting since we don't want to test knot, but resolved. Hence comment this test. There seems to be something wrong with the test though, as the upstream server refused recursion, but if so it is not suitable as an upstream server really, as resolved can only be client to a recursive resolver. --- test/units/testsuite-75.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/test/units/testsuite-75.sh b/test/units/testsuite-75.sh index b92ebf6b33..96f31d23be 100755 --- a/test/units/testsuite-75.sh +++ b/test/units/testsuite-75.sh @@ -522,9 +522,9 @@ monitor_check_rr "$TIMESTAMP" "follow13.almost.final.signed.test IN CNAME follow monitor_check_rr "$TIMESTAMP" "follow14.final.signed.test IN A 10.0.0.14" # Non-existing RR + CNAME chain -run dig +dnssec AAAA cname-chain.signed.test -grep -qF "status: NOERROR" "$RUN_OUT" -grep -qE "^follow14\.final\.signed\.test\..+IN\s+NSEC\s+" "$RUN_OUT" +#run dig +dnssec AAAA cname-chain.signed.test +#grep -qF "status: NOERROR" "$RUN_OUT" +#grep -qE "^follow14\.final\.signed\.test\..+IN\s+NSEC\s+" "$RUN_OUT" : "--- ZONE: onlinesign.test (dynamic DNSSEC) ---"