This bug was fixed in the package systemd - 243-3ubuntu1

systemd (243-3ubuntu1) focal; urgency=medium

  [ Dan Streetman ]
  * Fix resolved fallback to TCP (LP: #1849658)
    Author: Dan Streetman
  * Separate stderr and stdout of /etc/dhcp/dhclient-enter-hooks.d/resolved
    (LP: #1849608)
    Author: Dan Streetman
    File: debian/extra/dhclient-enter-resolved-hook

  [ Balint Reczey ]
  * Merge to Ubuntu from Debian experimental
  * Refresh patches:
    - Dropped changes:
      * udevadm trigger: do not propagate EACCES and ENODEV.
      * Pass personality test even when i386 userland runs on amd64 kernel

systemd (243-3) experimental; urgency=medium

  * Import patches from v243-stable branch (up to ef677436aa)

 -- Balint Reczey <>  Wed, 30 Oct 2019 15:19:33 +0100

** Changed in: systemd (Ubuntu Focal)
       Status: Fix Committed => Fix Released

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

  systemd resolv should separate the output of stdout and stderr

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Eoan:
Status in systemd source package in Focal:
  Fix Released

Bug description:

  dhclient fails to notify resolved about DNS servers due to bash-
  specific redirect inside 'resolved' hook script

  [test case]

  see original description below

  [regression potential]

  any regression would likely cause resolved not to be aware of
  dhclient-provided dns servers

  [other info]

  This is needed only in Eoan and later; X/B/D do not have the bash-
  specific redirect '&>' in their hook file.

  original description:

  The file /etc/dhcp/dhclient-enter-hooks.d/resolved
  provided by systemd (242-7ubuntu3) causes the dhclient failing to get DNS due 
to systemd-resolved is not run.
  This issue can be reproduced on Ubuntu Eoan:
  root@eoan:~# dhclient -v
  Internet Systems Consortium DHCP Client 4.4.1
  Copyright 2004-2018 Internet Systems Consortium.
  All rights reserved.
  For info, please visit

  Listening on LPF/ens224/00:0c:29:92:d4:da
  Sending on   LPF/ens224/00:0c:29:92:d4:da
  Listening on LPF/ens192/00:0c:29:92:d4:d0
  Sending on   LPF/ens192/00:0c:29:92:d4:d0
  Listening on LPF/ens160/00:0c:29:92:d4:c6
  Sending on   LPF/ens160/00:0c:29:92:d4:c6
  Sending on   Socket/fallback
  DHCPDISCOVER on ens224 to port 67 interval 3 (xid=0x6d9fb33d)
  DHCPDISCOVER on ens192 to port 67 interval 3 (xid=0xeb8fda26)
  DHCPREQUEST for on ens160 to port 67 
  DHCPACK of from (xid=0x5d54396d)
  RTNETLINK answers: File exists
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-ens160.conf: No such file or 
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-ens160.conf: No such file or 
  bound to -- renewal in 111 seconds.
  root@eoan:~# resolvectl status |grep DNS
  MulticastDNS setting: no
    DNSOverTLS setting: no
        DNSSEC setting: no
      DNSSEC supported: no
            DNSSEC NTA:
  MulticastDNS setting: no
    DNSOverTLS setting: no
        DNSSEC setting: no
      DNSSEC supported: no
  MulticastDNS setting: no
    DNSOverTLS setting: no
        DNSSEC setting: no
      DNSSEC supported: no
  MulticastDNS setting: no
    DNSOverTLS setting: no
        DNSSEC setting: no
      DNSSEC supported: no

  Attached please find the patch for this. The output for md5sum in the
  hook file resolv should separate the stdout and stderr so it won't
  compare the wrong data.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to