please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628778
Title:
systemd-resolved: after
** Changed in: systemd
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628778
Title:
systemd-resolved: after network reconnection, DNSSEC unsigned zones
treated as
I'm having the same problem after upgrading to 17.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628778
Title:
systemd-resolved: after network reconnection, DNSSEC unsigned zones
treated as
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628778
Title:
** Tags added: dnssec resolved
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628778
Title:
systemd-resolved: after network reconnection, DNSSEC unsigned zones
treated as bogus, stop resolving
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
** Description changed:
On the MIT network (which runs some ancient version of BIND 9), systemd-
resolved stops resolving anything that isn’t DNSSEC-signed after I
disconnect and reconnect the network. Signed zones continue to resolve.
This happens with either DNSSEC=yes or the default
