| From: D. Hugh Redelmeier via talk <talk@gtalug.org> | 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. This report turns out to be very incomplete. These tests were on nc. On any other host, nc.local doesn't resolve at all. Odd. avahi is running. $ avahi-browse --all shows many things, but none of them being my PCs. /etc/nsswitch.conf has a line: hosts: files myhostname mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns So I'm guessing that the nc.local is being resolved by "myhostname", not mdns4_minimal. On my desktop: $ sudo netstat -l -p -4 | grep avahi | cat udp 0 0 0.0.0.0:mdns 0.0.0.0:* 890/avahi-daemon: r udp 0 0 0.0.0.0:48151 0.0.0.0:* 890/avahi-daemon: r $ grep mdns /etc/services | cat mdns 5353/tcp # Multicast DNS mdns 5353/udp # Multicast DNS mdnsresponder 5354/tcp noclog # Multicast DNS Responder IPC mdnsresponder 5354/udp noclog # Multicast DNS Responder IPC The firewall allows mdns BTW, I'm tunning fedora 39 on all the boxes involved. I was going by this tutorial; it's bit old: <https://fedoramagazine.org/find-systems-easily-lan-mdns/> Pausing for dinner.