Bug 1588230 and bug 1624071 are fixed now. I'm fairly sure I understand bug 1624317 (and it would be fixed in yakkety now), and bug 1449001 is not actually a malfunction but just some disagreement about a builtin fallback if no DNS servers are configured (and thus fairly irrelevant really).
This bug is relevant, of course, thanks for the report. There are still several known problems with DNSSEC, and thus the plan had been from the start to enable it during the development series and disable it shortly before the release (which has happened a few days ago). The point was to learn about bugs in practice. So 16.10 ships with disabled DNSSEC, which is no worse than the default "dns" nss plugin (i. e. libc itself). ** Bug watch added: github.com/systemd/systemd/issues #4175 https://github.com/systemd/systemd/issues/4175 ** Also affects: systemd via https://github.com/systemd/systemd/issues/4175 Importance: Unknown Status: Unknown ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- 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/1628778 Title: systemd-resolved: after network reconnection, DNSSEC unsigned zones treated as bogus, stop resolving To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1628778/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
