please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1718890
Title:
thank you for your bug report. So the issue there is the same as in the
upstream ticket, that you expect the lookups to always be done using the
servers in the order of what is in resolv.conf? if so could you update
the title to state that/what you believe the problem to be exactly?
--
You receiv
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.n
To make clear the bearing of this:
systemd-resolved stops working on EVERY machine here after 5 minutes.
the DNS server has not been down since April
A Macintosh running macOS High Sierra installed for comparison can
resolve and connect to internal resources in every case where Ubuntu
looses con
Just found this article
https://github.com/systemd/systemd/issues/5755
Following the argument, systemd-resolved resolves DNS names on the
assumption that all configured DNS servers are equal.
diego-treitos and others argue that in small/medium sized companies, DNS
configuration will have an exter
** Tags removed: wayland-session
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1718890
Title:
name resolution stops working
Status in systemd package in Ubuntu:
New
B
6 matches
Mail list logo
