[arch-general] Cannot no longer resolve local hostname with the new nsswitch.conf
Chi-Hsuan Yen
yan12125 at gmail.com
Tue Nov 8 12:37:11 UTC 2016
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:
$ ping PC12574
PING PC12574(PC12574 (fe80::ae22:bff:fe77:e20b%enp3s0)) 56 data bytes
64 bytes from PC12574 (fe80::ae22:bff:fe77:e20b%enp3s0): icmp_seq=1 ttl=64
time=0.025 ms
64 bytes from PC12574 (fe80::ae22:bff:fe77:e20b%enp3s0): icmp_seq=2 ttl=64
time=0.078 ms
Is it a bug? Or such a usage is just a non-standard coincidence?
Thanks for any help.
Yen Chi Hsuan
[1]
https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/filesystem&id=f1cd9f7fb4cdf7617a1b875e14be212733f9c67a
More information about the arch-general
mailing list