On Tue 25 Jan 2022 at 18:35:54 -0600, David Wright wrote: > On Tue 25 Jan 2022 at 09:31:57 (+0100), Andrei POPESCU wrote: > > On Lu, 24 ian 22, 23:54:41, Brian wrote: > > > > > > Resolving hostnames on the local network is simple and reliable when > > > avahi-daemon and linnss-mdns are available. > > > > > > brian@desktop:~$ getent hosts envy4500.local > > > 192.168.7.235 envy4500.local > > > > > > Continually and nanually maintain /etc/hosts? Not in 2022! > > More like biannually :-) > > It's just pointless here, on such a static network. If I'm going to > login to the router to add a MAC, then editing and distributing my > master list is trivial. Last change: 2021-02-04, when I got hold of > a redundant computer.
I am sure sue the use of the dawn of time /etc/hosts is a workabble solution. However many (most?) users will have libnns-mdns installed and immediately up to the job of resolving hostnames on a statically or dynamically configured network and is maintenance-free. Why not use it? > > Ok, I'll bite :) > > > > Could you point to any (reasonably up-to-date) documentation or is it > > sufficient to just install avahi-daemon and libnss-mdns? > > I looked at the Debian wiki: ouch. It seems to have been spammed > a while back, and hasn't been touched in 4½ years. Although the > Arch wiki is far better, I'm not able to judge how much one might > be led astray by the differences between Arch and Debian. Ouch indeed! The baisc structure and content of the wiki page was established in 2006. Its stated purpose is for "...tracking how Debian supports mdns and zeroconf stuff,...". The Discussion section is (IMO) inappropriate for a wiki page. The Arch wiki page is technically more informed and, with care, would guide a Debian user in the right direcion. Having said that, 'ssh desktop.local' does not require much guidance. -- Brian.
