resolved-dns-query: remove dns_query_candidate_is_routable
authorFlorian Klink <flokli@flokli.de>
Sat, 23 Nov 2019 10:45:34 +0000 (11:45 +0100)
committerLennart Poettering <lennart@poettering.net>
Tue, 26 May 2020 17:30:23 +0000 (19:30 +0200)
commit90bdc8be66765df09bbc355783cee7204a5ebb31
tree06afc8a45abb34fddfc97936328bdf53ad630b07
parente6190e2882e1d6772a9e586fcc65c91d406e52fb
resolved-dns-query: remove dns_query_candidate_is_routable

Resolved can't reliably determine on whether "it makes sense" to query
AAAA records when not explicitly specifying it in the request, so we
shouldn't remove them.

After having done the resolving, applications can use RFC6724 to
determine whether that address is reachable.

We can't know whether an address is reachable before having resolved it
and inspecting the routing table, and not resolving AAAA just because
there's no IPv6 default route on the main interface link them breaks
various setups, including IPv6-providing wireguard tunnels on a
non-dualstacked environment.

Fixes #5782
Fixes #5915
Fixes #8017
src/resolve/resolved-dns-query.c