Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
I'm a bit conflicted with your answer, I suppose for a DNS server my best go-to should be my router, but I don't have access to it, next option would be DNS servers on each device and make localhost the primary server, then my router the secondary? Assuming that's the case I think that would break when I take a device off the local network as outside it would still assume things work like in the LAN. I could see it working if I had access to my router and primary server was DHCP provided (in LAN that would be my router with it's DNS configured to point to my devices with hostnames, outside it wouldn't have any and use the secondary) and secondary Tailscale's (which supports mDNS so with the same names it would hit my device's IPs from the tailnet) but I don't think I can get that router access...
Unless I misunderstood something of the solution, if so can I ask for clarification?
My comment was kind of high level because I wasn’t sure how much you knew technically already.
But yeah, you would unfortunately need access to the DNS server on your router and be able to add custom records. You’d additionally need a DNS server somewhere for Tailscale clients whether that’s on a Tailscale node or just on the public internet (and configure Tailscale to use it).
I suppose a last-ditch effort would be to buy a domain and create records pointing to both the Tailscale and internal LAN IP addresses. The downside is that you’re basically making the map to your network public but at least people wouldn’t actually be able to access those internal (LAN, Tailscale) IP addresses. The benefit would be only needing to manage one set of records in one place.
I’m really rusty on my OSI model but Avahi, NETBEUI and friends won’t work over WireGuard tunnels because those are layer 2 protocols whereas WireGuard operates at layer 3 (if I remember correctly).
I think I understand why Avahi wouldn't work with that explanation, I keep digging and now my router is not exactly inaccessible, it's managed by my ISP instead which is annoying but I supposedly can still ask them to tweak things for me so I may have a chance
Tailscale already has DNS servers working on Tailnets (they call it mDNS, or magicDNS) which is I believe 100.100.100.100... actually, the documentation states that every tailscale-running device is a DNS server on itself too but either way that IP is private on every tailnet, remains accessible and host names are configurable on the Tailnet too
If I'm not mistaken on the functioning of DNS, I should be able to do it with that primary-router secondary-tailscale DNS setup I hypothesized and on LAN that will yield perfect connectivity, while out from home there would be no such records and it'll fall back to Tailscale's DNS which is already private (worst concern is just sending a request for a hostname on public network but that shouldn't be that big of a deal)
At this point I might have this solved, but of course, more input is nice too, It'll take some time for my ISP to work for me on this
mDNS refers to multicast DNS (.local), while similar you should not mix it up with Tailscale's MagicDNS, which is entirely a Tailscale thing, dependent on their APIs.
mDNS also seems to be what you're after too. For the hostname-only resolution to work, you need to have Avahi or equivalent mDNS daemon running on the hosts, and add
.localto the search domains. Setting search domains can be done manually on each host or via DHCP network-wide.With mDNS and
.localin the search domains, when you try e.g.http://myhost/in the browser, the browser first triesmyhost, then adds each search domain, e.g.myhost.local. Since .local is reserved for mDNS, querying it results in an mDNS query in your network, and if there's a device with a matching name, it will respond with it's IP address.Note that if you have Tailscale and MagicDNS active, your tailnet's domain will (or should) be the first one on the search domains list, and your DNS server is set to 100.100.100.100, which is a dummy address on which the tailscale daemon runs the internal DNS server for Tailscale, including MagicDNS.
Multicast DNS / Avahi is a little bit error prone in my experience, but when nothing goes wrong, this would give you what you're looking for.
There are other options, like your router automatically registering DNS entries for DHCP hosts, or running a separate DNS server anf manually adding records for the hosts you need this for.
Right, I didn't pick up on that m/multicast DNS difference, I thought I was talking about the same thing, thanks for clarification
Sounds like I do have options here, so while I wait for my ISP to comply, I'll also try out Avahi then