** Changed in: systemd
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1624071
Title:
libnss-resolve: Fallback from resolve to dns br
Calin: see https://bugs.launchpad.net/ubuntu/+source/nss-
mdns/+bug/1641328
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1624071
Title:
libnss-resolve: Fallback from res
Calin: This sounds like something entirely unrelated. Can you please
file a new bug?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1624071
Title:
libnss-resolve: Fallback
Glad to see this has been reported. On my system, I can no longer get to any
local nodes by referring to the hostname, so it is pretty clear that hostname
resolution is not working. I was able to circumvent the behavior for only 1
Linux machine by specifying nodename.local, but that doesn't wo
This bug was fixed in the package systemd - 231-9git1
---
systemd (231-9git1) yakkety; urgency=medium
* systemctl: Add --wait option to wait until started units terminate again.
This is a prerequisite for using systemd for graphical sessions without
ugly polling.
* nss-res
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1624071
Title:
libnss-resolve: Fallback from res
** Changed in: systemd (Ubuntu)
Status: Triaged => In Progress
** Changed in: systemd (Ubuntu)
Milestone: ubuntu-16.11 => ubuntu-16.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs
** Changed in: systemd (Ubuntu)
Milestone: ubuntu-16.10 => ubuntu-16.11
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1624071
Title:
libnss-resolve: Fallback from res
Upstream PR sent with a possible fix:
https://github.com/systemd/systemd/pull/4164
With that "resolve [!UNAVAIL=return] dns" does the right thing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bug
** Also affects: systemd via
https://github.com/systemd/systemd/issues/4157
Importance: Unknown
Status: Unknown
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: system
Filed https://github.com/systemd/systemd/issues/4157 upstream for the
NOTFOUND vs. UNAVAIL problem.
** Bug watch added: github.com/systemd/systemd/issues #4157
https://github.com/systemd/systemd/issues/4157
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Description changed:
The libnss-resolve postinst script inserts ‘resolve’ before ‘dns’ in the
hosts line of /etc/nsswitch.conf. This makes DNSSEC validation
impossible, even with DNSSEC=yes in /etc/systemd/resolved.conf, because
if libnss_resolve returns a validation failure, glibc wil
You’re right: glibc seems to treat the absence of libnss-resolve itself
as UNAVAIL, which is the same code returned on DNSSEC validation
failures when libnss-resolve is working. I don’t see a way around this
other than patching libnss-resolve to return NOTFOUND (or TRYAGAIN?) on
validation failure
Thanks for reporting this, well spotted!
The reason for having "dns" is *not* to guard against failures of
resolved -- if the daemon is not running, then nss-resolve already falls
back to glibc's resolver (i. e. "dns").
The reason is that libnss-resolve itself might not be available. E. g.
you mi
I also worry that, by masking systemd-resolved failures, this fallback
has meant that systemd-resolved is not really getting adequate testing.
If there were widespread problems causing systemd-resolved lookups to
fail, would anyone have noticed?
--
You received this bug notification because you a
15 matches
Mail list logo
