[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: systemd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Dimitri, indeed, my bad.
In other news: it seems that this issue has been known for a while and somebody
has been (trying to) solv(e|ing) it - I guess the solution will come to Ubuntu
at some stage...
https://github.com/systemd/systemd/pull/12004
Thanks for the feedback, looking forward to a
On Thu, 31 Oct 2019 at 12:40, ts <1850...@bugs.launchpad.net> wrote:
>
> This was a problem before, I fixed it unlinking /run/systemd/stub-
> resolv.conf and linking /run/systemd/resolv.conf to /etc/
>
Neither of the paths mentioned are correct... did you mean one of:
OK, I've just talked to the admins for quite some time and while I'm
sure that the previous workaround was fine I'm now not so sure how to
deal with the situation (or: why it worked).
Here we go:
Connecting to the wifi configures two wifi-internal DNS servers and one
internal search zone ( say
Hi Dan, thanks for the feedback.
Being at the office (University) my interface is configured correctly,
but name resolution fails for specific (local) names.
This was a problem before, I fixed it unlinking /run/systemd/stub-
resolv.conf and linking /run/systemd/resolv.conf to /etc/
I then
> please advise as to how systemd name resolution through its local service can
> be
> disabled now (as it is broken).
I won't tell you it's not possible/supported to disable/bypass resolved
(although that's most likely the general response you will get), but I'm
happy to look into what's broken
