systemd-* no more resolution after apt upgrade 20.04

Bug #1903036 reported by Poil
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
New
Undecided
Unassigned

Bug Description

When building an image, via Packer on Azure, based on official Ubuntu 20.04 "0001-com-ubuntu-server-focal" after apt-upgrading I have no more DNS resolution

If I mark as hold systemd systemd-* the resolution is OK

Before :

    azure-arm: Link 2 (eth0)
    azure-arm: Current Scopes: DNS
    azure-arm: DefaultRoute setting: yes
    azure-arm: LLMNR setting: yes
    azure-arm: MulticastDNS setting: no
    azure-arm: DNSOverTLS setting: no
    azure-arm: DNSSEC setting: no
    azure-arm: DNSSEC supported: no
    azure-arm: Current DNS Server: 168.63.129.16
    azure-arm: DNS Servers: 168.63.129.16

After :

    azure-arm: Link 2 (eth0)
    azure-arm: Current Scopes: none
    azure-arm: DefaultRoute setting: no
    azure-arm: LLMNR setting: yes
    azure-arm: MulticastDNS setting: no
    azure-arm: DNSOverTLS setting: no
    azure-arm: DNSSEC setting: no
    azure-arm: DNSSEC supported: no

Best regards,

Poil (poil)
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. Could you confirm to what version of systemd you are upgrading which is creating the issue?

tags: added: regression-update
Revision history for this message
Sebastien Bacher (seb128) wrote :
Revision history for this message
Dan Streetman (ddstreet) wrote :

I'm pretty sure this is a dup of bug 1902960; feel free to un-dup if there is reason to think i'm wrong.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.