mirror of
https://github.com/systemd/systemd.git
synced 2025-01-12 13:18:14 +03:00
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.
This commit is contained in:
parent
9c47b33444
commit
df81adba88
@ -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) ---"
|
||||
|
Loading…
Reference in New Issue
Block a user