4 ms·
It's not just Apple, I had to fix a brand new install of Debian the other day to turn off mDNS to get my local names resolving. Seeing it in Debian was enough t
by lolinder 3y ago
It's not just Apple, I had to fix a brand new install of Debian the other day to turn off mDNS to get my local names resolving. Seeing it in Debian was enough to make me wonder if my frustration at Apple about this was misplaced and maybe I just need to reconfigure my network somehow.
- candiddevmike 3y agosystemd-resolved does special handling for .local because it's reserved for use with mDNS only. Using it outside of mDNS will cause problems. > Multi-label names with the domain suffix ".local" are resolved using MulticastDNS on all local interfaces where MulticastDNS is enabled. As with LLMNR, IPv4 address lookups are sent via IPv4 and IPv6 address lookups are sent via IPv6. https://www.freedesktop.org/software/systemd/man/latest/systemd-resolved.service.html https://www.freedesktop.org/software/systemd/man/latest/syst...
- throw0101d 3y ago> … and maybe I just need to reconfigure my network somehow. You are using a TLD that is reserved for something else. It is your configuration that is not standards compliant (.local was reserved in 2013 per RFC 6762).
- lolinder 3y agoMy network is a few devices in my home, so up until now I've just been using what works. Now it doesn't reliably work so I'll probably change it at some point. I don't really care about the standards, I care about what my devices do, and until the past few months my Linux devices defaulted to (mis)using .local.