> # Generated by NetworkManager > nameserver 127.0.1.1 OK, that's definitively unexpected. It looks like NM is still using a different plugin for managing /etc/resolv.conf and that thinks it's using the dnsmasq plugin (127.0.1.1) while not actually starting dnsmasq. That part is understood and what I retitled the bug to.
What is not clear is why your NM uses that configuration despite not setting it in NetworkManager.conf. joulu 06 19:05:04 Sabertooth NetworkManager[576]: <info> [1481043904.5853] dns-mgr[0x55f3c8285000]: init: dns=systemd-resolved, rc-manager=symlink, plugin=systemd-resolved That actually looks expected. Maybe your /etc/resolv.conf is not a symlink to ../run/resolvconf/resolv.conf but a plain file? If so, please do sudo systemctl stop NetworkManager sudo rm /etc/resolv.conf sudo ln -s ../run/resolvconf/resolv.conf /etc/resolv.conf sudo systemctl start NetworkManager This hopefully should fix things. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647133 Title: dns=dnsmasq does not work any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
