Bug#1055415: Wrong order for the `resolve' option in nsswitch.conf

[Gioele Barabucci]

On 26/05/24 16:11, Luca Boccassi wrote:
>>>> See
> https://salsa.debian.org/systemd-team/systemd/-/merge_requests/162
> 
> I don't think anybody else here has the required knowledge to provide
> any more info than we already have. Gioele could you please make a
> recommendation and update the MR so that we can do something, one way
> or the other?

My suggestion is: merge that PR, do not change `d/libnss-resolve.nss` 
(thus leaving `resolve` after `files`), close this bug.

The original bug report requested:

> Specifically, it is recommended to place "resolve" early in 
> /etc/nsswitch.conf's "hosts:" line. It should be before the "files" 
> entry, since systemd-resolved supports /etc/hosts internally, but
> with caching.
The post-MR hosts line will look like this:

     hosts:  files myhostname mymachines resolve [!UNAVAIL=return] dns

This sequence matches all suggestions in nss-myhostname(8), 
nss-mymachines(8), and nss-resolve(8), with the exception of

 > [resolve] should be before the "files" entry

/etc/hosts is a "resolver of last resource". Having it behind a daemon 
is reasonable but it is a diversion from the status quo for which Debian 
is not ready IMO. Maybe in trixie+1.

The above hosts line seems like the best compromise between enabling new 
functionality and preserving long established backstops.

Regards,

-- 
Gioele Barabucci