Public bug reported:

systemd-resolved, or more precisely the hook script /lib/systemd/system
/systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add to the set of nameservers in /etc/resolv.conf alongside the
other nameservers.  That makes no sense because systemd-resolved sets up as a proxy for those other nameservers.  The effect is
similar to bug 1624071 but for applications doing their own DNS lookups.
It breaks any DNSSEC validation that systemd-resolved tries to do;
applications will failover to the other nameservers, bypassing
validation failures.  And it makes failing queries take twice as long.

/etc/resolv.conf should have only when systemd-resolved is

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New

You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.

  systemd-resolved appends to resolv.conf alongside existing

To manage notifications about this bug go to:

desktop-bugs mailing list

Reply via email to