Replies: 2 comments
-
+1 on this; I have the same issue |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hey! I managed to do it with my tailnet. What I did:
Option two I'm exploring right now:
EDIT: Quick note for solution one, I've set the option to get my DNS settings from tailscale server. In my tailnet, I've set the first two entries to my tailnet machine IPv4/6. You must then set your clients' configuration to get your DNS from the tailscale server (if not set manually by your OS) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have successfully setup tailscale to connect to my local network and use my AdGuardHome instance for DNS resolution. However, the shortcuts I have defined in DNS Rewrites and Custom Filter Rules do not work. I can use the 192.168.x.x address to connect to specific machine without a problem, but the shortcut isn't recognised (e.g. shortcut.lan).
The shortcuts work fine when I am on a machine in my local network. Just not when using Tailscale to connect remotely.
I’ve tried adding the Tailscale ipv4 range to the AdGuard conf file private_networks section and installing Tailscale on the adguardhome machine. I made sure to restart AdguardHome so the conf file was loaded anew.
I’ve also tried adding the tailnet address for the adguard machine as the Tailnet nameserver instead of the 192.168.x.x address, but none of that caused the shortcuts to work.
Does anyone know how to get shortcuts to work with Tailscale?
Beta Was this translation helpful? Give feedback.
All reactions