diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2017-05-12 08:31:46 -0400 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2017-05-12 14:31:46 +0200 |
| commit | 5486a31d287f26bcd7c0a4eb2abfa4c074b985f1 (patch) | |
| tree | d1e644d972fe60531ab0e17be6deb6c86941ad75 /NEWS | |
| parent | 3823da25cf0d374851321d0c5fa5bce872ef5f2b (diff) | |
| download | systemd-5486a31d287f26bcd7c0a4eb2abfa4c074b985f1.tar.gz | |
nss-resolve: drop the internal fallback to libnss_dns (#5945)
If we could not communicate with systemd-resolved, we would call into
libnss_dns. libnss_dns would return NOTFOUND for stuff like "localhost" and
other names resolved by nss-myhostname, which we would fall under the !UNAVAIL=
condition and cause resolution to fail. So the following recommended
configuration in nsswitch.conf would not work:
hosts: resolve [!UNAVAIL=return] dns myhostname
Remove the internal fallback code completely so that the fallback logic
can be configured in nsswitch.conf.
Tested with
hosts: resolve [!UNAVAIL=return] myhostname
and
hosts: resolve [!UNAVAIL=return] dns myhostname
Fixes #5742.
Diffstat (limited to 'NEWS')
| -rw-r--r-- | NEWS | 7 |
1 files changed, 7 insertions, 0 deletions
@@ -1,5 +1,12 @@ systemd System and Service Manager +CHANGES WITH 234 in spe + + * The code to call libnss_dns as a fallback from libnss_resolve when + the communication with systemd-resolved fails was removed. This + fallback was redundant and interfered with the [!UNAVAIL=return] + suffix. See nss-resolve(8) for the recommended configuration. + CHANGES WITH 233: * This version requires at least gperf 3.1 for building, 3.0 is not |