> Now, it is being pushed instead to /etc/resolv.conf. > > nameserver 10.99.244.1 > nameserver 127.0.1.1 > > [...] > Connecting to the VPN also pushes search paths to /etc/resolv.conf - > overriding the search > domains that I have already configured, and which should take precedence.
Is this being done in NM itself, i.e., does NM send these two addresses in this order to resolvconf? Or does something else send the 10.99.244.1 address to resolvconf? Or does something else write directly to /etc/resolv.conf? > This is breaking the DNS handling for libvirt-bin, which has its own > forwarding dnsmasq > instance which it expects to be able to talk to the first nameserver listed > here. (As an aside, you may be interested in the discussion at #1163147. It is proposed there that the forwarding dnsmasq instance for libvirt compile its nameserver list using a resolvconf hook script, in the same manner as the plain dnsmasq does. Then if it is configured to listen on some loopback address it can be used on the host system to look up names of vm guests as well as other names.) > The nameserver in question does not work (and is not meant to be used) for > any name > lookups except company-internal domains. Ah, so the VPN nameserver does not provide general DNS service; you rely on dnsmasq to route queries. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430077 Title: [vivid] VPN connection breaks /etc/resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1430077/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
