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

2022-08-30 Thread Lutz Willek
Seems to be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1938791 - same
symptoms.

[Workaround]

Reboot the node, DNS should return back to normal.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1938791] Re: [18.04] systemd-resolve does not update DNS servers

2022-08-30 Thread Lutz Willek
*** This bug is a duplicate of bug 1988119 ***
https://bugs.launchpad.net/bugs/1988119

** This bug has been marked a duplicate of bug 1988119
   Update to systemd 237-3ubuntu10.54 broke dns

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1938791

Title:
  [18.04] systemd-resolve does not update DNS servers

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  
  A number of my nodes were in a broken state resolving DNS on an 
unattended-upgrades enabled nodes, running dhclient and checking 
systemd-resolve --status shows the following:

  Link 2 (eth0)  
Current Scopes: none 
 LLMNR setting: yes  
  MulticastDNS setting: no   
DNSSEC setting: no   
  DNSSEC supported: no

  Compared to a working node:

  Link 2 (eth0)
Current Scopes: DNS
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 145.218.226.65
145.218.238.29
DNS Domain: reddog.microsoft.com

  [Workaround]

  Reboot the node, DNS should return back to normal.

  sos report and additional information: https://private-
  fileshare.canonical.com/~pjds/dsv/dns-issue/

  Thanks,

  Peter

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1938791] Re: [18.04] systemd-resolve does not update DNS servers

2022-08-30 Thread Lutz Willek
exact the same as described above happened today morning after an
unattended update on Ubuntu 18.04 and 20.04 machines.

`grep 'configure systemd:amd64 237-3ubuntu10.54' /var/log/dpkg.log`

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1938791

Title:
  [18.04] systemd-resolve does not update DNS servers

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  
  A number of my nodes were in a broken state resolving DNS on an 
unattended-upgrades enabled nodes, running dhclient and checking 
systemd-resolve --status shows the following:

  Link 2 (eth0)  
Current Scopes: none 
 LLMNR setting: yes  
  MulticastDNS setting: no   
DNSSEC setting: no   
  DNSSEC supported: no

  Compared to a working node:

  Link 2 (eth0)
Current Scopes: DNS
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 145.218.226.65
145.218.238.29
DNS Domain: reddog.microsoft.com

  [Workaround]

  Reboot the node, DNS should return back to normal.

  sos report and additional information: https://private-
  fileshare.canonical.com/~pjds/dsv/dns-issue/

  Thanks,

  Peter

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp