-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tailscale on Synology DSM 7 dns still not working == RESOLVED #12498
Comments
Same Problem. Any news? Can't reach my devices in other networks. Tried the magic dns 100.100.100.100 as an alternate dns. Did not work... |
Same here |
Same here. |
Same here. |
Same here too. I can ssh into my DSM7 NAS using the magic DNS FQDN but when I'm in that ssh session and nslookup that same FQDN I get a response from my local gateway (not 100.100.100.100) that gives me the IP for ingress-nyc-01.tailscale.com rather than the expected 100.x.x.x IP for that node. If I nslookup other FQDN that are valid like the name of the machine I'm ssh'ing in from, it can't find it, NXDOMAIN, again because it's asking the local gateway and not 100.100.100.100. In my DSM6 NAS, I can nslookup all of my nodes and get 100.x.x.x IP responses back as expected. |
This may be a duplicate of #3602 or at least related. |
This comment was marked as duplicate.
This comment was marked as duplicate.
For those who still need a solution, give this a shot: #3602 (comment) |
@pjdubya has the solution that works for me at present, till Synology break that as well. Thanks |
@pjdubya with your fix I loose Quickconnect when tailscale is running. This means Synology apps will not connect. |
Who is supposed to close resolved issues like this one? Maybe @bradfitz who is listed at https://github.com/orgs/tailscale/people and started #1995? |
Closing as dup of #3602 |
What is the issue?
Unable to resolve tailscale full domain addresses. This is due to tailscale user not having privilages to re-write /etc/resolv.conf
Numerous bugs have been filed, but all closed saying resolved, but without a resolution so tailscale is will not resolve magicdns on DSM 7
Relevant log entry
ignoring SetDNS permission error on Synology (Issue 4017); was: rename /etc/resolv.conf /etc/resolv.pre-tailscale-backup.conf: permission denied
Steps to reproduce
Install tailscale on DSM 7
start service
Are there any recent changes that introduced the issue?
No
OS
Synology
OS version
Synology DSM 7
Tailscale version
1.68.0-700068000
Other software
No response
Bug report
BUG-1caf71ea7be433ab07e671b06f052057491b571ee4dd70eeb1f024969ea5c670-20240616175052Z-7b9a893be24c0f56
The text was updated successfully, but these errors were encountered: