[Bug 192645] Re: Add, not replace current DNS, when doing network routing

2011-08-05 Thread Mathieu Trudel-Lapierre
Pratically already fixed in Lucid and later (using "Use this connection only for the resources on its network"). Since it's largely fine for simple configurations, I'll mark this Fix Released. Things will work properly for relatively simple configurations, and DNS will by default be added to the li

[Bug 192645] Re: Add, not replace current DNS, when doing network routing

2009-05-19 Thread Andrew Rodland
This might be too complicated to implement for everyone, but while we're wishlisting, here's how I accomplish split DNS (works for vpnc or openvpn, at least). 1) Install dnsmasq, configure it in a DNS-only role (no DHCP), and bind to localhost. 2) Replace the nameserver entry in /etc/resolv.conf

[Bug 192645] Re: Add, not replace current DNS, when doing network routing

2008-11-28 Thread Daniel T Chen
The question really becomes "which configuration is more likely to be the default supported one?" ** Changed in: network-manager-vpnc (Ubuntu) Importance: Undecided => Wishlist -- Add, not replace current DNS, when doing network routing https://bugs.launchpad.net/bugs/192645 You received this