Activity log for bug #1785383

Date Who What changed Old value New value Message
2018-08-04 10:43:29 Steve Dodd bug added bug
2018-08-04 10:46:09 Steve Dodd bug task added systemd (Ubuntu)
2018-08-31 21:25:21 Arduous bug added subscriber Arduous
2018-08-31 21:26:02 Launchpad Janitor dnsmasq (Ubuntu): status New Confirmed
2018-08-31 21:26:02 Launchpad Janitor systemd (Ubuntu): status New Confirmed
2019-10-10 19:53:26 Dan Streetman bug added subscriber Dan Streetman
2019-12-03 18:05:11 Paride Legovini dnsmasq (Ubuntu): status Confirmed Triaged
2019-12-03 18:05:46 Paride Legovini bug added subscriber Ubuntu Server
2019-12-04 21:15:25 Bryce Harrington bug watch added https://github.com/systemd/systemd/issues/9785
2019-12-04 21:15:25 Bryce Harrington bug task added systemd
2019-12-04 21:16:38 Bryce Harrington description 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. 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 Simple-ish test case: --- 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 & 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 --- 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) [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: --- 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 & 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 --- [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)
2019-12-04 21:35:08 Bryce Harrington systemd (Ubuntu): status Confirmed Triaged
2019-12-04 21:35:52 Bryce Harrington nominated for series Ubuntu Bionic
2019-12-04 21:35:52 Bryce Harrington bug task added dnsmasq (Ubuntu Bionic)
2019-12-04 21:35:52 Bryce Harrington bug task added systemd (Ubuntu Bionic)
2019-12-04 21:36:06 Bryce Harrington dnsmasq (Ubuntu Bionic): status New Triaged
2019-12-04 21:51:22 Bryce Harrington tags amd64 apport-bug bionic amd64 apport-bug bionic server-next
2019-12-04 22:52:46 Bug Watch Updater systemd: status Unknown Fix Released
2020-04-14 10:03:05 Dan Streetman tags amd64 apport-bug bionic server-next amd64 apport-bug bionic ddstreet server-next
2020-06-15 10:08:37 Kai Kasurinen bug added subscriber Kai Kasurinen
2021-05-26 19:31:56 Dan Streetman nominated for series Ubuntu Groovy
2021-05-26 19:31:56 Dan Streetman bug task added dnsmasq (Ubuntu Groovy)
2021-05-26 19:31:56 Dan Streetman bug task added systemd (Ubuntu Groovy)
2021-05-26 19:31:56 Dan Streetman nominated for series Ubuntu Focal
2021-05-26 19:31:56 Dan Streetman bug task added dnsmasq (Ubuntu Focal)
2021-05-26 19:31:56 Dan Streetman bug task added systemd (Ubuntu Focal)
2021-05-26 19:31:56 Dan Streetman nominated for series Ubuntu Impish
2021-05-26 19:31:56 Dan Streetman bug task added dnsmasq (Ubuntu Impish)
2021-05-26 19:31:56 Dan Streetman bug task added systemd (Ubuntu Impish)
2021-05-26 19:31:56 Dan Streetman nominated for series Ubuntu Hirsute
2021-05-26 19:31:56 Dan Streetman bug task added dnsmasq (Ubuntu Hirsute)
2021-05-26 19:31:56 Dan Streetman bug task added systemd (Ubuntu Hirsute)
2021-05-26 19:32:14 Dan Streetman systemd (Ubuntu Hirsute): status New In Progress
2021-05-26 19:32:14 Dan Streetman systemd (Ubuntu Hirsute): assignee Dan Streetman (ddstreet)
2021-05-26 19:32:27 Dan Streetman systemd (Ubuntu Groovy): importance Undecided Medium
2021-05-26 19:32:27 Dan Streetman systemd (Ubuntu Groovy): status New In Progress
2021-05-26 19:32:27 Dan Streetman systemd (Ubuntu Groovy): assignee Dan Streetman (ddstreet)
2021-05-26 19:32:39 Dan Streetman systemd (Ubuntu Focal): importance Undecided Medium
2021-05-26 19:32:39 Dan Streetman systemd (Ubuntu Focal): status New In Progress
2021-05-26 19:32:39 Dan Streetman systemd (Ubuntu Focal): assignee Dan Streetman (ddstreet)
2021-05-26 19:32:52 Dan Streetman systemd (Ubuntu Bionic): importance Undecided Medium
2021-05-26 19:32:52 Dan Streetman systemd (Ubuntu Bionic): status New In Progress
2021-05-26 19:32:52 Dan Streetman systemd (Ubuntu Bionic): assignee Dan Streetman (ddstreet)
2021-05-26 19:33:01 Dan Streetman systemd (Ubuntu Hirsute): importance Undecided Medium
2021-05-26 19:36:24 Dan Streetman dnsmasq (Ubuntu Focal): status New Fix Released
2021-05-26 19:36:34 Dan Streetman dnsmasq (Ubuntu Groovy): status New Fix Released
2021-05-26 19:36:44 Dan Streetman dnsmasq (Ubuntu Hirsute): status New Fix Released
2021-05-26 19:36:54 Dan Streetman dnsmasq (Ubuntu Impish): status Triaged Fix Released
2021-05-27 12:16:41 Dan Streetman 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: --- 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 & 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 --- [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) [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)
2021-05-27 12:22:25 Launchpad Janitor merge proposal linked https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/403382
2021-05-28 21:38:22 Steve Langasek systemd (Ubuntu Hirsute): status In Progress Incomplete
2021-05-31 14:46:46 Balint Reczey systemd (Ubuntu Impish): status Triaged Fix Committed
2021-05-31 14:47:56 Balint Reczey systemd (Ubuntu Impish): importance Undecided Medium
2021-06-01 22:45:46 Brian Murray systemd (Ubuntu Hirsute): status Incomplete Fix Committed
2021-06-01 22:45:48 Brian Murray bug added subscriber Ubuntu Stable Release Updates Team
2021-06-01 22:45:53 Brian Murray bug added subscriber SRU Verification
2021-06-01 22:45:58 Brian Murray tags amd64 apport-bug bionic ddstreet server-next amd64 apport-bug bionic ddstreet server-next verification-needed verification-needed-hirsute
2021-06-01 23:00:14 Brian Murray systemd (Ubuntu Groovy): status In Progress Fix Committed
2021-06-01 23:00:27 Brian Murray tags amd64 apport-bug bionic ddstreet server-next verification-needed verification-needed-hirsute amd64 apport-bug bionic ddstreet server-next verification-needed verification-needed-groovy verification-needed-hirsute
2021-06-01 23:06:48 Brian Murray systemd (Ubuntu Focal): status In Progress Fix Committed
2021-06-01 23:06:58 Brian Murray tags amd64 apport-bug bionic ddstreet server-next verification-needed verification-needed-groovy verification-needed-hirsute amd64 apport-bug bionic ddstreet server-next verification-needed verification-needed-focal verification-needed-groovy verification-needed-hirsute
2021-06-01 23:11:39 Brian Murray systemd (Ubuntu Bionic): status In Progress Fix Committed
2021-06-01 23:11:51 Brian Murray tags amd64 apport-bug bionic ddstreet server-next verification-needed verification-needed-focal verification-needed-groovy verification-needed-hirsute amd64 apport-bug bionic ddstreet server-next verification-needed verification-needed-bionic verification-needed-focal verification-needed-groovy verification-needed-hirsute
2021-06-03 20:51:38 Dan Streetman tags amd64 apport-bug bionic ddstreet server-next verification-needed verification-needed-bionic verification-needed-focal verification-needed-groovy verification-needed-hirsute amd64 apport-bug bionic ddstreet server-next verification-done-hirsute verification-needed verification-needed-bionic verification-needed-focal verification-needed-groovy
2021-06-03 20:56:22 Dan Streetman tags amd64 apport-bug bionic ddstreet server-next verification-done-hirsute verification-needed verification-needed-bionic verification-needed-focal verification-needed-groovy amd64 apport-bug bionic ddstreet server-next verification-done-groovy verification-done-hirsute verification-needed verification-needed-bionic verification-needed-focal
2021-06-03 21:04:16 Dan Streetman tags amd64 apport-bug bionic ddstreet server-next verification-done-groovy verification-done-hirsute verification-needed verification-needed-bionic verification-needed-focal amd64 apport-bug bionic ddstreet server-next verification-done-focal verification-done-groovy verification-done-hirsute verification-needed verification-needed-bionic
2021-06-03 21:12:55 Dan Streetman tags amd64 apport-bug bionic ddstreet server-next verification-done-focal verification-done-groovy verification-done-hirsute verification-needed verification-needed-bionic amd64 apport-bug bionic ddstreet server-next verification-done verification-done-bionic verification-done-focal verification-done-groovy verification-done-hirsute
2021-06-16 15:27:13 Brian Murray removed subscriber Ubuntu Stable Release Updates Team
2021-06-16 15:27:08 Launchpad Janitor systemd (Ubuntu Hirsute): status Fix Committed Fix Released
2021-06-16 15:29:48 Launchpad Janitor systemd (Ubuntu Groovy): status Fix Committed Fix Released
2021-06-16 15:35:19 Launchpad Janitor systemd (Ubuntu Focal): status Fix Committed Fix Released
2021-06-16 15:59:22 Launchpad Janitor systemd (Ubuntu Bionic): status Fix Committed Fix Released
2021-07-07 19:22:55 Launchpad Janitor systemd (Ubuntu Impish): status Fix Committed Fix Released
2021-09-23 10:32:50 Paride Legovini attachment added lp1785383-dnsmasq-bionic.patch https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1785383/+attachment/5527343/+files/lp1785383-dnsmasq-bionic.patch
2021-09-23 10:33:30 Paride Legovini dnsmasq (Ubuntu Bionic): assignee Paride Legovini (paride)
2021-09-24 13:37:38 Paride Legovini dnsmasq (Ubuntu Bionic): status Triaged In Progress
2021-09-24 13:57:06 Paride Legovini 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) [Impact] dnsmasq 2.79 and below omits EDNS0 OPT records [1] 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. [1] https://en.wikipedia.org/wiki/Extension_Mechanisms_for_DNS [Test Plan] 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 ----------------------------------------- [Where problems could occur] Problems may occur in case a client queries dnsmasq and relies on EDNS0 not being available for behaving correctly. This covers cases where the software querying dnsmasq is buggy or misconfigured. [Development Fix] Fixed upstream in dnsmasq >= 2.80. [Stable Fix] Partial cherry-pick of upstream commit http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78 The cherry-pick is partial because half if it is already in the package .diff we have in Bionic.
2021-09-24 13:58:10 Paride Legovini tags amd64 apport-bug bionic ddstreet server-next verification-done verification-done-bionic verification-done-focal verification-done-groovy verification-done-hirsute amd64 apport-bug bionic ddstreet server-next
2021-09-24 14:01:02 Paride Legovini description [Impact] dnsmasq 2.79 and below omits EDNS0 OPT records [1] 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. [1] https://en.wikipedia.org/wiki/Extension_Mechanisms_for_DNS [Test Plan] 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 ----------------------------------------- [Where problems could occur] Problems may occur in case a client queries dnsmasq and relies on EDNS0 not being available for behaving correctly. This covers cases where the software querying dnsmasq is buggy or misconfigured. [Development Fix] Fixed upstream in dnsmasq >= 2.80. [Stable Fix] Partial cherry-pick of upstream commit http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78 The cherry-pick is partial because half if it is already in the package .diff we have in Bionic. [Impact] dnsmasq 2.79 and below omits EDNS0 OPT records [1] 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. [1] https://en.wikipedia.org/wiki/Extension_Mechanisms_for_DNS [Test Plan] 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 # returns "; EDNS ..." dig -t aaaa test.test @10.0.0.1 | grep EDNS # again, should return "; EDNS ..." but doesn't. # does so with the -proposed package. ----------------------------------------- [Where problems could occur] Problems may occur in case a client queries dnsmasq and relies on EDNS0 not being available for behaving correctly. This covers cases where the software querying dnsmasq is buggy or misconfigured. [Development Fix] Fixed upstream in dnsmasq >= 2.80. [Stable Fix] Partial cherry-pick of upstream commit http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78 The cherry-pick is partial because half if it is already in the package .diff we have in Bionic.
2021-10-06 13:30:23 Paride Legovini merge proposal linked https://code.launchpad.net/~paride/ubuntu/+source/dnsmasq/+git/dnsmasq/+merge/409149
2021-10-13 14:44:41 Robie Basak dnsmasq (Ubuntu Bionic): status In Progress Fix Committed
2021-10-13 14:44:46 Robie Basak bug added subscriber Ubuntu Stable Release Updates Team
2021-10-13 14:44:51 Robie Basak tags amd64 apport-bug bionic ddstreet server-next amd64 apport-bug bionic ddstreet server-next verification-needed verification-needed-bionic
2021-10-14 15:30:13 Paride Legovini tags amd64 apport-bug bionic ddstreet server-next verification-needed verification-needed-bionic amd64 apport-bug bionic ddstreet server-next verification-done verification-done-bionic
2021-10-20 20:50:16 Launchpad Janitor dnsmasq (Ubuntu Bionic): status Fix Committed Fix Released