[Bug 1770557] Re: systemd-resolved should be restarted only on actual DHCP/DNS updates

[Dimitri John Ledkov]

Very nice! I'm sorry you hit this problem, and your analysis and
solution look good. I will work on integrating it.

** Changed in: systemd (Ubuntu)
       Status: New => Confirmed

** Changed in: systemd (Ubuntu)
     Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: systemd (Ubuntu)
       Status: Confirmed => Triaged

** Changed in: systemd (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1770557

Title:
  systemd-resolved should be restarted only on actual DHCP/DNS updates

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  My ISP gives me a DHCP IP with lease time about 2 minutes
  in the script /etc/dhcp/dhclient-enter-hooks.d/resolved , a function make_resolv_conf is defined which creates config fragments in resolved.conf.d/ , then unconditionally restarts systemd-resolved service
  so, about every 2 minutes, this service is restarted on my system, despite the fact that DNS configuration is not changed.
  I would propose an update to the script, which first creates config fragments in temporary files, and then it restarts the service only when config is changed (or created/removed).
  now going to attach my patch below

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1770557/+subscriptions