Skip to content
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

Closed
IcarusR opened this issue Jun 16, 2024 · 12 comments
Closed

tailscale on Synology DSM 7 dns still not working == RESOLVED #12498

IcarusR opened this issue Jun 16, 2024 · 12 comments
Labels

Comments

@IcarusR
Copy link

IcarusR commented Jun 16, 2024

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

@BernardTeske
Copy link

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...

@sbourdette
Copy link

Same here

@AlisaCat-S
Copy link

Same here.

@monocodes
Copy link

Same here.
I'm trying to reach ts-exit-node-eu-de-w10-a.*****-****.ts.net from Synology itself with no success. My Synology is a Subnet router to home LAN btw.

@pjdubya
Copy link

pjdubya commented Oct 5, 2024

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.

@jimmybrancaccio
Copy link

This may be a duplicate of #3602 or at least related.

@yenba

This comment was marked as duplicate.

@pjdubya
Copy link

pjdubya commented Oct 15, 2024

For those who still need a solution, give this a shot: #3602 (comment)

@IcarusR
Copy link
Author

IcarusR commented Oct 19, 2024

@pjdubya has the solution that works for me at present, till Synology break that as well. Thanks

@IcarusR IcarusR changed the title tailscale on Synology DSM 7 dns still not working tailscale on Synology DSM 7 dns still not working == RESOLVED Oct 19, 2024
@IcarusR
Copy link
Author

IcarusR commented Oct 28, 2024

@pjdubya with your fix I loose Quickconnect when tailscale is running. This means Synology apps will not connect.
I guess you can not have it all ways !!

@ukanuk
Copy link

ukanuk commented Dec 29, 2024

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?

@bradfitz
Copy link
Member

Closing as dup of #3602

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests