resolved: fully follow CNAMEs in the DNS stub after all
authorLennart Poettering <lennart@poettering.net>
Fri, 5 Mar 2021 15:50:04 +0000 (16:50 +0100)
committerLennart Poettering <lennart@poettering.net>
Sat, 6 Mar 2021 13:04:21 +0000 (14:04 +0100)
commitb97fc57178932689bdcb9030e1e2bf299d49ce0b
tree645c85b4baefb95f7c3549cbf605ad6b86df8b18
parent39005e187095062718621880e5d8ad707ac8fe8f
resolved: fully follow CNAMEs in the DNS stub after all

In 2f4d8e577ca7bc51fb054b8c2c8dd57c2e188a41 I argued that following
CNAMEs in the stub is not necessary anymore. However, I think it' better
to revert to the status quo ante and follow it after all, given it is
easy for us and makes sure our D-Bus/varlink replies are more similar to
our DNS stub replies that way, and we save clients potential roundtrips.

Hence, whenever we hit a CNAME/DNAME redirect, let's restart the query
like we do for the D-Bus/Varlink case, and collect replies as we go.
src/resolve/resolved-dns-stub.c