My DHCP on my edgerouter has the domain internal.mywebsite.com and I have split dns enabled on my tailnet, so any hostnames that start with internal.mywebsite.com should use the DNS of my edgerouter. I installed tailscale on my edgerouter and it was mostly working fine, I could access my internal services by IP but not by hostname when routing through my tailnet (both worked when locally though). I rechecked my tailnet split DNS configuration, but everything looked good.
Essentially I could:
ping 192.168.0.1 (ping the edgerouter gateway and dhcp server, locally or through my tailnet)
ping 192.168.0.2 (ping my internal service, locally or through my tailnet)
dig @192.168.0.1 host.internal.mywebsite.com -> 192.168.0.2 (ONLY when locally)
But I could not:
dig @192.168.0.1 host.internal.mywebsite.com
when routing through my tailnet.
What I ended up doing was on the edgerouter:
- Navigate to
services > DNS > DNS Forwarding
- Add an "other" listen-on interface
- list
tailscale0 in the custom interface input box
And now dig @192.168.0.1 host.internal.mywebsite.com -> 192.168.0.2 works when routing through my tailnet.
Is this something that should be added to the readme or to the setup script? I'm also not sure if this was the best way to resolve my issue, so I am welcome to hearing others suggestions
My DHCP on my edgerouter has the domain
internal.mywebsite.comand I have split dns enabled on my tailnet, so any hostnames that start withinternal.mywebsite.comshould use the DNS of my edgerouter. I installed tailscale on my edgerouter and it was mostly working fine, I could access my internal services by IP but not by hostname when routing through my tailnet (both worked when locally though). I rechecked my tailnet split DNS configuration, but everything looked good.Essentially I could:
ping 192.168.0.1(ping the edgerouter gateway and dhcp server, locally or through my tailnet)ping 192.168.0.2(ping my internal service, locally or through my tailnet)dig @192.168.0.1 host.internal.mywebsite.com -> 192.168.0.2(ONLY when locally)But I could not:
dig @192.168.0.1 host.internal.mywebsite.comwhen routing through my tailnet.
What I ended up doing was on the edgerouter:
services > DNS > DNS Forwardingtailscale0in the custom interface input boxAnd now
dig @192.168.0.1 host.internal.mywebsite.com -> 192.168.0.2works when routing through my tailnet.Is this something that should be added to the readme or to the setup script? I'm also not sure if this was the best way to resolve my issue, so I am welcome to hearing others suggestions