I’m using v1.30.2 on both my laptop (Pop!_OS/Ubuntu) and a VPS (CentOS7) out on the internet. I also have my firewall (PFSense) setup as a client to expose my home /24.
Any time I start using an exit node I can no longer use the default DNS to resolve my internal services but I can still access them via IP. So, I do the following:
tailscale up --accept-routes --reset dig wiki.website.com @100.100.100.100 #works dig wiki.website.com @192.168.2.100 #works ping wiki.website.com #works, resolves to 192.168.2.120 ping 192.168.2.120 #works
and when I use an exit node Private DNS stops working.
tailscale up --accept-routes --reset --exit-node=100.64.0.1 dig wiki.website.com @100.100.100.100 #fails dig wiki.website.com @192.168.2.100 #works ping wiki.website.com #fails ping 192.168.2.120 #works
If I add wiki.website.com to my host file, I can still access it and everything is fine so I’m 99% sure this is a DNS issue. I cant seem to figure out what’s going on. It seems to take my Exit Node DNS settings(???) so I can still access public services but private stops working. I’ve tried using
--accept-dns=false, changing my edit node DNS to my private DNS IP, and I’ve spent a couple hours searching but I cant figure it out.
Can anyone replicate my problem or is my setup the issue? I can replicate this on Android, Windows, and Linux but I have no idea how to troubleshoot on Android or Windows.