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)
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Tue, 18 Jun 2024 18:41:01 +0000 (20:41 +0200)
commitba031f1fe86e36d7adc0340b047de32399c98bf7
tree9546eff16b9cbd616a8ce2874eef2413f7055ea4
parent30df42a9277bbf138d52887c9b79e452db425585
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")
(cherry picked from commit 364c948707afa097f6ad177b61c2b51a86c0089a)
src/resolve/resolved-dns-server.c