I first experience this issue with nm version 1.8.2-1ubuntu1 in an - as
of writing fully updated - 17.04.
Syslog will be attached, from that you can see that dnsmask gets the
nameserver, networkmanager gets it too, but it doesn't make to
resolv.conf, that will only have the stub resolver.
** Changed in: dnsmasq (Ubuntu)
Importance: Undecided => High
** Changed in: dbus (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Another possible workaround I have used is to comment out the line
"dns=dnsmasq" in /etc/NetworkManager/NetworkManager.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568787
Title:
resolvconf
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568787
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dnsmasq (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568787
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dbus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568787
Title:
