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
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
.local
to the search domains. Setting search domains can be done manually on each host or via DHCP network-wide.With mDNS and
.local
in 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