I was reminded that libnss-resolve is in 'standard' now, which means
it's also installed by default on server and any bugs that affect only
the stub DNS resolver without affecting the dbus service - such as this
one - do not impact DNS resolution by default on server in 16.10.
(I was wondering why no one had reported it before now.)
So, I'm downgrading this from critical to high since it only hits users
of 16.10 server in a few corner cases (i.e. containers, chroots without
libnss-resolve installed). It should still be SRUed.
** Changed in: systemd (Ubuntu Yakkety)
Importance: Critical => High
** Changed in: network-manager (Ubuntu Yakkety)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1647031
Title:
systemd-resolved’s 127.0.0.53 server does not follow CNAME records
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1647031/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
