[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.
https://bugs.launchpad.net/bugs/177943
Ok, thanks for the suggestion there Dimitri.
I ran a wireshark to see what happened when I pinged the hostname which
would inevitably fail, and I got nothing in wireshark. What I think is
happening and makes most sense is that the stub resolver is eating up my
DNS lookup and not forwarding it onto
To revert to using upstream dns servers directly instead of stub, change
/etc/resolv.conf to point at /run/systemd/resolve/resolv.conf instead of
../run/systemd/resolve/stub-resolv.conf
However, it would be nice to figure out what domain you are trying to
resolve, and what is the result of it.
Ca
This is a recent install, so haven't installed much apart from my usual
programs, vim, editors, etc...
I would expect to be able to ping by hostname without installing additional
software such as resolver libraries.
Here is my /etc/nsswitch.conf
`cat /etc/nsswitch.conf`
# /etc/nsswitch.conf
#
#
What's in nsswitch.conf?
Have you install the relevant resolver libraries?
Better yet: use ubuntu-bug.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
** Package changed: ubuntu => systemd (Ubuntu)
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779438
Title:
Cannot resolve names using systemd-resolved stub resolver
To manag
