On Tue, Feb 27, 2024 at 01:43:36AM -0500, D. Hugh Redelmeier via talk wrote:
I used to give all my machines permanent IP addresses and added entries in my domain for them. (I have /24 globally routable IP addresses.)
I then got lazy and let most be assigned dynamically. But not servers.
Now I'm even more lazy. I'm starting to use .local. So machines declare their hostname and mDNS / bonjour gets to resolve name.local. Neat.
Tonight I'm creating an experimental NextCloud server. Let's say it's hostname is nc.
- ping nc.local works - ssh nc.local works - host nc.local works - Firefox and even links cannot see nc.local.
Why is that? Firefox is set to use the default DNS, not Firefox's own.
If I give Firefox the actual IP address, Apache balks because it cares about the DNS name used. But that's further than nc.local got.
I guess Firefox doesn't do mDNS. Why would that be? Or am I making a wrong guess?
Clearly I could give to computer a real DNS name, but I'm kind of stubborn and want to understand what's going on.
Is your firefox set to do DNS over HTTPS or normal DNS? Apparently since version 104 firefox always does a search for words entered in the address bar unless they end in standard domain suffixes. Entering host.local/ apparently should skip that and use dns instead. So does nc.local/ work in firefox? Now links is odd. Does it think it is a file name and not http since the .local is weird to it? Certainly on my system using 'links host.local' gives an error that file:///home/lsorense/host.local does not exist while 'links http://host.local' works. Looking at the source, links (well links2) uses the contents in the publicsuffix package at compile time to generate the internal list of known suffixes that it treats as http by default. Well that list plus 'onion' which for some reason mozilla doesn't want to include in the official suffix list but links2 does. -- Len Sorensen