Fixed - The symlink of resolv.conf was wrong. The following shows how -
resolv.conf-BAK was the old, broken one, resolv.conf the one I fixed. I don't
know how that happened, but I have installed the 18.04 beta version, may that
was the reason.
lrwxrwxrwx 1 root root 32 Mai 29 10:55 res
Nope. Still an issue.
** Changed in: network-manager (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762984
Title:
DNS resolving not working due to wrong entry
Works now.
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762984
Title:
DNS resolving not working due to wrong entry in resolv.
More on this:
After a fresh reboot but also after wake from suspend I have to set the
DNS server in /etc/resolv.conf manually to get DNS resolving working.
This is the output of ``systemd-resolve --status`` before manual
changes:
root@thettop:~# systemd-resolve --status
Global
DNSSEC N