resolved: permit dnssec rrtype questions when we aren't validating
authorRonan Pigott <ronan@rjp.ie>
Fri, 8 Mar 2024 20:40:08 +0000 (13:40 -0700)
committerYu Watanabe <watanabe.yu+github@gmail.com>
Wed, 12 Jun 2024 09:50:45 +0000 (18:50 +0900)
commit364c948707afa097f6ad177b61c2b51a86c0089a
tree4034fcd5228d3d89cce5da47a13d8124d3e8ef90
parent707890d4ffcb6fc5236df8aef83fb9177714afb1
resolved: permit dnssec rrtype questions when we aren't validating

This check introduced in 91adc4db33f6 is intended to spare us from
encountering broken resolver behavior we don't want to deal with.
However if we aren't validating we more than likely don't know the state
of the upstream resolver's support for dnssec. Let's let clients try
these queries if they want.

This brings the behavior of sd-resolved in-line with previouly stated
change in the meaning of DNSSEC=no, which now means "don't validate"
rather than "don't validate, because the upstream resolver is declared to
be dnssec-unaware".

Fixes: 9c47b334445a ("resolved: enable DNS proxy mode if client wants DNSSEC")
src/resolve/resolved-dns-server.c