[Bug 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns

[Pieter Lexis]

> This won't help anyone that has already received the broken update - I
think the advice there is to restart, or there is a workaround in the OP
here - but it should prevent any further occurrences.

Do note this is not a solution for those using non-Azure resolvers
provided via DHCP through their VNET. These users must reboot or
manually set the fallback servers to their custom DNS resolver addresses

-- 
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/1988119

Title:
  Update to systemd 237-3ubuntu10.54 broke dns

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Two servers today that updated systemd to "systemd 237-3ubuntu10.54" 
  https://ubuntu.com/security/notices/USN-5583-1

  could not resolve dns anymore.
  no dns servers, normally set through dhcp.

  Ubuntu 18.04

  Temp fix.
   1. Edit /etc/systemd/resolved.conf
   1. Add/Uncomment # FallbackDNS=168.63.129.16
   1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service
   1. Confirm dns working with systemd-resolve google.com

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