I've linked to the upstream systemd bug report, although from comment #4
it sounds like it might be a regression caused by a security fix.
As to the dnsmasq patch mentioned in the issue description, what it
appears to be doing is checking if there is a pseudoheader in the
request, and if so adds the edns data structure to the response. I
can't speak to what potential regressions might be concerns here, but
the patch itself looks sensible to me. So, given adequate testing, I
don't see a reason against considering SRU for this.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Triaged
** Also affects: dnsmasq (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: dnsmasq (Ubuntu Bionic)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785383
Title:
missing EDNS0 record confuses systemd-resolved
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1785383/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
