Re: [arch-general] Cannot no longer resolve local hostname with the new nsswitch.conf

On 8 November 2016 at 13:37, Chi-Hsuan Yen via arch-general <arch-general@archlinux.org> wrote:

Hi Arch enthuasiasts,

With testing/filesystem 2016.11-2, I can no longer use my local hostname to acess services on the local machine. For example:

$ hostname PC12574

$ ping PC12574 ping: PC12574: Name or service not known

Seems changes in nsswitch.conf [1] does the effect. If I change the hosts: line in nsswitch.conf back to the old configuration "files resolve mymachines myhostname", or remove the [!UNAVAIL=return] part from this line, ping works fine:

do you have systemd-resolved running? what does `getent -s resolve hosts <you hostname>` return? -- damjan