[Bug 90681] Re: resolv.conf overwritten using VPN/PPP etc...

[Daniel Clark]

Tamas Herman wrote:
> I have Jaunty (Netbook Remix) here with the same problem.
> 
> I use blueman instead of bluez to establish PAN networking.
> 
> I tried blueman in both of its modes
> - blueman handles the interfaces
> - let the network manager handle the interfaces
> 
> In both cases i experience the resolv.conf being overwritten regularly.
> 
> I also want to have my - maybe connection specific - search order present there.
> (Its a lot of hassle to write FQDNs with the saaaame.looong.tld :)

Here is the ugly workaround I use that has the advantage of working all
the time (I'm on a network where the DHCP lease time is around 10
minutes as part of the authentication system).

You'll of course want to replace the name (office.fsf.org) and and
address (192.168.0.25) of my private-network name servers with yours ,
and change the .in-addr.arpa lines to be your private network ranges.

=== Try at fixing PITA DHCP Lease Renewal breaks DNS problem ===
See also the Ubuntu bug
[https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/90681/ resolv.conf
overwritten using VPN/PPP etc..]

* replace network-manager with [http://wicd.sourceforge.net/download.php
wicd]
* aptitude install dnsmasq
* remove the lines beginning with "script-security", "up", and "down"
from /etc/openvpn/client.conf
* Set /etc/resolv.conf to always point to the dnsmasq name server:
  rm /etc/resolv.conf
  echo nameserver 127.0.0.1 > /etc/resolv.conf
  chmod 444 /etc/resolv.conf
  chattr +i /etc/resolv.conf

* Make one of these your /etc/dnsmasq.conf file:

<pre>
#
# /etc/dnsmasq.conf minimal version
#

resolv-file=/etc/resolv.conf.dhclient-new
server=/0.168.192.in-addr.arpa/192.168.0.25
server=/0.16.172.in-addr.arpa/192.168.0.25
server=/office.fsf.org/192.168.0.25
</pre>

-- 
Daniel JB Clark   | Sys Admin, Free Software Foundation
pobox.com/~dclark | http://www.fsf.org/about/staff#danny

-- 
resolv.conf overwritten using VPN/PPP etc...
https://bugs.launchpad.net/bugs/90681
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.