Can you please include NetworkManager's log output to see what sort of state it is getting into? NetworkManager is not supposed to be touching resolv.conf itself; it's supposed to use the NetworkManagerDispatcher to make the system do the right thing, as per /etc/NetworkManager/dispatcher.d . In Debian and Ubuntu, this means it calls ifupdown, the same way as if you weren't using NM at all.
There is not enough information here yet to suggest resolvconf is related to the problem. -- network-manager not deleting resolvconf information on resume from suspend https://bugs.launchpad.net/bugs/84313 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
