mirror of https://github.com/tailscale/tailscale/
net/dns: verify that systemd-resolved is actually in charge.
It's possible to install a configuration that passes our current checks for systemd-resolved, without actually pointing to systemd-resolved. In that case, we end up programming DNS in resolved, but that config never applies to any name resolution requests on the system. This is quite a far-out edge case, but there's a simple additional check we can do: if the header comment names systemd-resolved, there should be a single nameserver in resolv.conf pointing to 127.0.0.53. If not, the configuration should be treated as an unmanaged resolv.conf. Fixes #2136. Signed-off-by: David Anderson <danderson@tailscale.com>pull/2142/head
parent
e7164425b3
commit
320cc8fa21
Loading…
Reference in New Issue