Comment 5 for bug 1957086

As usual once you know what you search for the results are much better.

It turns out that it might be related to one of those reports:
- https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q1/016015.html
- https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q1/016069.html

But even better was the finding that Debian at 249-5-2 was affected by the same.
- https://ci.debian.net/packages/s/systemd/unstable/amd64/
- https://ci.debian.net/data/autopkgtest/unstable/amd64/s/systemd/16383273/log.gz

That seems to be fixed since systemd 249.6-1 and checking that made me find

To me there is nothing obvious in regard to this in debian
=> https://salsa.debian.org/systemd-team/systemd/-/commits/debian/master
nor in upstream
=> https://github.com/systemd/systemd-stable/commits/v249.6

But I think this is enough to get the bug reported and maybe eyes more used
to systemd will see the related fix as it seems it must be there somewhere ...

@systemd maintainer (Lukas?) does this ring a bell to you or do you see the change that might have fixed this?
Also is there a PPA with a Ubuntu build of >=249.6-1 to check if it resolves the issue also in Ubuntu?