This bug was fixed in the package systemd - 245.4-4ubuntu3.7 --------------- systemd (245.4-4ubuntu3.7) focal; urgency=medium
[ Andy Chi ] * debian/patches/lp1926547-hwdb-60-keyboard-Update-Dell-Privacy-Local-Mic-Mute-.patch - Apply upstream patch to correct key and device mapping. (LP: #1926547) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=62c3ce6d6b2cab762b24aa610d6d135a67bdd76a [ Dan Streetman ] * d/p/lp1921696/0001-rfkill-improve-error-logging.patch, d/p/lp1921696/0002-rfkill-use-short-writes-and-accept-long-reads.patch: Handle rfkill api change in kernel 5.10 (LP: #1921696) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ff0c23ba4fbcfa7f68e98adb6d62798ce54ca1da * d/p/lp1929122-network-check-that-received-ifindex-is-valid.patch: Check if ifindex is valid (LP: #1929122) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6378191818bc7d169b657e6f7a2b50cfddb4275e * d/p/lp1929560-network-move-set-MAC-and-set-nomaster-operations-out.patch: Move link mac and master config out of link_up() (LP: #1929560) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=28cff7ee02a9ebd4ab93026af9fceaa2283725b3 * d/p/lp1902891-core-mount-mount-command-may-fail-after-adding-the-c.patch: Handle failed mount command (LP: #1902891) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b425189a483d7455db870b0ec5b2443c0eea7d76 * d/p/resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch, d/p/lp1880258-log-nxdomain-as-debug.patch, d/p/lp1785383-resolved-address-DVE-2018-0001.patch: - Use upstream patch for DVE-2018-0001 handling (LP: #1785383) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ec45ebfee362ad3e429642f7519e8b88f16dc221 [ Łukasz 'sil2100' Zemczak ] * d/p/lp1664844/0001-network-add-ActivationPolicy-configuration-parameter.patch, d/p/lp1664844/0002-test-add-ActivationPolicy-unit-tests.patch, d/p/lp1664844/0003-save-link-activation-policy-to-state-file-and-displa.patch: - add support for configuring the activation policy for an interface (LP: #1664844) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=94f7b72d8128c743f35b308101a87d2c53a4074c -- Dan Streetman <ddstr...@canonical.com> Thu, 27 May 2021 11:16:17 -0400 ** 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. https://bugs.launchpad.net/bugs/1785383 Title: missing EDNS0 record confuses systemd-resolved Status in systemd: Fix Released Status in dnsmasq package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in dnsmasq source package in Bionic: Triaged Status in systemd source package in Bionic: Fix Committed Status in dnsmasq source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in dnsmasq source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in dnsmasq source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in dnsmasq source package in Impish: Fix Released Status in systemd source package in Impish: Fix Committed Bug description: [Impact] dnsmasq 2.79 and below omits EDNS0 OPT records when returning an empty answer for a domain it is authoritative for. systemd-resolved seems to get confused by this in certain circumstances; when using the stub resolver and requesting an address for which there are no AAAA records, there can sometimes be a five second hang in resolution. [Fix] This is fixed by upstream commit http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78 Not sure if it is worth cherry picking? I imagine the most likely trigger will be dnsmasq on routers which are not likely to be running Ubuntu, but maybe just in case. I also think there are some logic issues in systemd-resolved, upstream bug filed: https://github.com/systemd/systemd/issues/9785 [Test Case] Simple-ish test case for bionic: --- IFACE=dummy0 SUBNET=10.0.0 ip link add $IFACE type dummy ifconfig $IFACE ${SUBNET}.1/24 dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo --host-record=test.test,${SUBNET}.1 --server=/test/ & dig -t a test.test @10.0.0.1 | grep EDNS # should return "; EDNS ..." dig -t aaaa test.test @10.0.0.1 | grep EDNS # again, should return "; EDNS ..." but doesn't --- To reproduce the systemd-resolved side of the problem --- # as above, but # now configure systemd-resolved to look at only 10.0.0.1, then systemd-resolve --reset-server-features # should exhibit five second delay then connect, assuming sshd is running :) ssh test.test --- More detailed test case for focal and later: install dnsmasq on a bionic system and start it, listening to an interface that is externally reachable, e.g. for a normal libvirt vm with interface name 'ens3': IFACE=ens3 dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo --host-record=test.test,1.2.3.4 --server=/test/ note that the '1.2.3.4' address doesn't matter, any addr is ok. then setup a test system that can reach the dnsmasq system, and configure networkd to use the dnsmasq server, e.g. using config like: [Match] Name=ens3 [Network] DHCP=yes DNS=DNSMASQ_IP_ADDRESS Domains=test [DHCPv4] UseDNS=no UseDomains=no replace 'DNSMASQ_IP_ADDRESS' with the addr of the bionic system where dnsmasq is running, and replace 'ens3' with whatever the test system interface name is. Then restart systemd-networkd, and test: systemd-resolve --reset-server-features systemd-resolve --flush-caches host test.test The lookup using 'host' should complete immediately;. [Discussion] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: dnsmasq-base 2.79-1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sat Aug 4 11:33:56 2018 InstallationDate: Installed on 2018-05-31 (64 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1785383/+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