Thanks, I'll try that and try to report. I have already asked on various
forums if there is any way to replace /only/ the stub resolver (systemd-
resolved) with a more recent version without replacing all the code
related to init and the system initialization and been told there is no
safe way, hen
> Is there a ppa with a more recent systemd-resolved to try on focal
yes, https://launchpad.net/~ubuntu-support-team/+archive/ubuntu/systemd
however that includes the entire upstream systemd code, not only
systemd-resolved; i'd suggest you test inside a VM and not on your main
system.
--
You re
Marked by myself the issue as invalid, since when I reported the issue
my understanding of it was to o modest. Will open a new more
appropriate issue.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Unfortunately, I have no idea on how to bisect this, due to the fact
that there is not an independent repo for systemd-resolved and
attempting to work on the whole systemd seems to dounting and risky as
an experience for me. Is there a ppa with a more recent systemd-
resolved to try on focal witho
Tested on a manjaro system that being rolling uses the latest systemd.
There is no issue there.
Hence the problem appears to be a systemd-resolved bug specific to the
systemd version shipped with ubuntu 20.04.
Because the issue breaks local resolution via mDNS in some
configurations, I think that
