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

On Wed, Nov 9, 2016 at 1:53 AM, Damjan Georgievski via arch-general < arch-general@archlinux.org> wrote: > On 8 November 2016 at 18:43, Patrick Burroughs (Celti) via > arch-general wrote: > > On Tue, 8 Nov 2016 18:01:32 +0100 > > Damjan Georgievski via arch-general

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

On 8 November 2016 at 18:43, Patrick Burroughs (Celti) via arch-general wrote: > On Tue, 8 Nov 2016 18:01:32 +0100 > Damjan Georgievski via arch-general wrote: > >> > $ getent -s resolve hosts $(hostname) >> >> this should fail since you

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

On Tue, 8 Nov 2016 18:01:32 +0100 Damjan Georgievski via arch-general wrote: > > $ getent -s resolve hosts $(hostname) > > this should fail since you don't have the resolved service running. nss-resolve will chainload nss-dns when systemd-resolved is not running

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

> $ getent -s resolve hosts $(hostname) this should fail since you don't have the resolved service running. but, when using `hosts: files mymachines resolve [!UNAVAIL=return] dns myhostname` standard resolving should then go to the dns source, and then to the myhostname source. what does getent

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

On Tue, Nov 8, 2016 at 10:02 PM, Damjan Georgievski via arch-general < arch-general@archlinux.org> wrote: > On 8 November 2016 at 13:37, Chi-Hsuan Yen via arch-general > wrote: > > Hi Arch enthuasiasts, > > > > With testing/filesystem 2016.11-2, I can no longer use my

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 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 >

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

On Tue, Nov 8, 2016 at 9:11 PM, Jan Alexander Steffens via arch-general < arch-general@archlinux.org> wrote: > On Tue, Nov 8, 2016 at 1:37 PM Chi-Hsuan Yen via arch-general < > arch-general@archlinux.org> wrote: > > > Hi Arch enthuasiasts, > > > > With testing/filesystem 2016.11-2, I can no

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

On Tue, Nov 8, 2016 at 1:37 PM 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

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

On Tue, Nov 8, 2016 at 8:37 PM, Chi-Hsuan Yen 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

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

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