[Bug 1624071] Re: libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation

[Calin Cerghedean]

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 work with my NAS device.  So, I'm kinda stuck...   I think this package is currently in yakkety-proposed (sorry, I still haven't learned how to be able to tell where a "fix" was released and in what repository it is currently in).
Any idea when this will be released to yakkety-updates ?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1624071

Title:
  libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  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 will
  simply fall back to libnss_dns.  It also makes NXDOMAIN lookups twice
  as slow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624071/+subscriptions