On Wed, Nov 9, 2016 at 1:53 AM, Damjan Georgievski via arch-general < arch-general@xxxxxxxxxxxxx> wrote: > On 8 November 2016 at 18:43, Patrick Burroughs (Celti) via > arch-general <arch-general@xxxxxxxxxxxxx> wrote: > > On Tue, 8 Nov 2016 18:01:32 +0100 > > Damjan Georgievski via arch-general <arch-general@xxxxxxxxxxxxx> 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 > > (see `man 8 nss-resolve`). > > ah right, that fallback should be removed *in the future* and I was > under the impression it already happened > > https://github.com/systemd/systemd/commit/344874fcd0a3fc1f9bc6cdf34ecaf5 > 37c10a3ad3 > > > > > -- > damjan > getent -s dns hosts $(hostname) also returns 2 getent -s myhostname hosts $(hostname) gives reasonable results: fe80::ae22:bff:fe77:e20b NEWSLAB-PC12574 fe80::800:27ff:fe00:0 NEWSLAB-PC12574 The package testing/systemd is the latest r232. My machine has been online for half a month. Should I reboot to use the latest systemd? By the way, from your commit, seems r232 has fixed it? Many thanks, Yen Chi Hsuan
