It only messes with /etc/resolv.conf if you did `--accept-dns` and don't have systemd-resolved, which nowadays is much more common.
Linux DNS is a clusterfun: https://tailscale.com/blog/sisyphean-dns-client-linux/
But, yeah, without systemd-resolved Linux DNS is a fight for the death between uncooperating processes. NetworkManager is okay but there are a dozen buggy variants in the wild we have to work around.
Linux is by far the worst platform for DNS config.
I totally recommend systemd-resolved. It's the only thing that does DNS well on Linux.
Re:Tailscale SSH
by thefilmore on Thursday June 23, 2022 @05:32AM
(#31846783)
What about using NSS[1]? You could add a Tailscale provider to the `hosts` entry.
Consistently I’m unable to use Tailscale on a GCP instance and also use GCP services cleanly, because it messes with the DNS route to the metadata server. Otherwise, it’s a great product.
Thanks for the feedback. I've filed https://github.com/tailscale/tailscale/issues/4911 to fix that.
https://github.com/tailscale/tailscale/issues/4911 is now fixed and will be in the next release.
Re:Tailscale SSH
by Handytinge on Thursday July 07, 2022 @02:17AM
(#32010535)
I don't use GCP, but this is a high quality example of a company doing feedback right. Nicely done!
This is one of the major things I _don't_ like about Tailscale. I wish they'd just stick to enabling Wireguard and making the authentication easier (i.e., where they started). I'm not a fan of most of the features they've added since. I don't want service discovery, magic DNS, SSH key management and/or the kitchen sink bolted on.