As I recall resolved is also enabled by default in Ubuntu Server 16.10
(though not on Desktop), so this is a critical issue there as well.
Dimitri, could you please have a look at this backport?
Could someone who's seeing the DNSSEC problem please also file a
separate bug report, so we can track that problem separately?
** Also affects: network-manager (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Yakkety)
Importance: Undecided => Critical
** Changed in: systemd (Ubuntu Yakkety)
Status: New => Triaged
** Changed in: systemd (Ubuntu Yakkety)
Milestone: None => yakkety-updates
** Changed in: systemd (Ubuntu Yakkety)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
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
