I think this bug is connected to an underlying lack of control of DNS settings by network-manager. It seems like the daemons NM invokes (openvpn, dhcp3, etc.) modify resolv.conf on their own accord in a way that's not controlled by or compatible with NM. For example, see <https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/90681>.
Word to the wise:
I think this bug is connected to an underlying lack of control of DNS settings by network-manager. It seems like the daemons NM invokes (openvpn, dhcp3, etc.) modify resolv.conf on their own accord in a way that's not controlled by or compatible with NM. For example, see <https:/ /bugs.launchpad .net/ubuntu/ +source/ dhcp3/+ bug/90681>.