Tailscale Version: 1.1.540-gce66dfebd
OS: Ubuntu 20.04 amd64
On my home network, I run a k3s cluster which has an instance of bitwarden running I use for my password manager. I’d like to be able to access it wherever I go, so I have each node in my cluster hooked up to tailscale as a machine. On my laptop I have my
/etc/hosts set up to redirect
*.homelab to my manager node, and the ingress is set up to send
bitwarden.homelab requests to the pod serving bitwarden.I’d like to use magic DNS here, so that on my phone (where I can’t modify
/etc/hosts ) I can access my bitwarden instance from anywhere. I figured I can enable magic DNS, then set up a second ingress in k3s to handle the host that’s generated for me by tailscale and route to bitwarden. However, when I enable magic DNS and set the DNS servers to 220.127.116.11 or 18.104.22.168, it seems to just break all my devices’ connections to the internet. I get
DNS_PROBE_FINISHED_BAD_CONFIG in my browser when trying to go anywhere (a tailscale machine or any public website). I’m also running pihole in my cluster, and am using it for DNS on my laptop and phone, but even when I disable this and try again it still seems to break.
I already spoke with @danderson via slack trying to debug some of this, but was asked to raise it here instead.
We determined that the DNS resolution was working as expected, however both
ping and trying to browse to my magic DNS name would just hang.