I've been duct-taping my way around this issue (and other similar
issues) for years. It's terribly kludgy, but it's simple and effective
and doesn't break on each upgrade:
/etc/init.d/openvpn start
while true ; do cp /etc/resolv.conf.good /etc/resolv.conf ; sleep 15 ; done
Or something like
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in Ubuntu.
https://bugs.launchpad.net/bugs/90681
Title:
resolv.conf overwritten using VPN/PPP etc...
To manage notifications about this bug go to:
How to update nameserver in Network Manager and stop it from changing the
/etc/resolv.conf after rebooting in Ubuntu 9.04 to 10.10
1. Open Terminal and type sudo su then press enter.
2. Type in gedit /etc/resolv.conf then press enter, you will then see
your Network Managers nameserver usually
Adding domain info to /etc/dhcp3/dhclient.conf should fix this issue.
This file will add domain info to /etc/resolv.conf (and will work with
or without VPN). Use the following steps:
1.) At the terminal enter sudo gedit /etc/hdcp3/dhclient.conf (without quotes)
2.) find the line #supersede
I'm not sure why you think retrieving domain info from the DHCP server
will do anything to help the problem, which is that the Ubuntu DHCP
client is overwriting the resolv.conf file and replacing nameservers
that were added due to VPN connections.
--
resolv.conf overwritten using VPN/PPP etc...
Is anyone ever going to do anything about this? I know it's not an easy
problem but there are solutions here which will help at least some of
the people and which are not harmful (for example, not updating
/etc/resolv.conf on RENEW if the old nameserver is still present).
If we could do at least
Hello
I've been having similar problems and looking for a long time for a solution.
Finally seems to have solved my problem.
I do not understand how different installed packages decide to modify
/etc/resolv.conf and sometimes without consideration to each other. In my case,
I use
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
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
Any updates? Is there a patch in the works for this?
--
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.
--
Ubuntu-server-bugs mailing
I installed jaunty and some of this is fixed - new NetworkManager is
much more straight-forward as far as routing settings are concerned, and
resolv.conf gets updated (with target DNS appearing before others in the
file). I am still missing a connection-specific search domains,
though...
--
Hi,
When I started my notebook looking at the log entries I saw something like:
resolvconf: unable to remove (...)/eth1/resolv.conf. File system read only.
This entry does not appear in dmesg and syslog. But the behaviour is
reproducable evey system start. Perhaps this helps fixing this annoying
Hi,
I think I get the same problem here on my 8.10. I connect to different
wireless LANs with my notebook. I also use openvpn and vpnc. My problem
ist, that dhcpcd somehow REMEMBERS its resolv.conf configurations and
still applies settings from different WLANs or VPNs when I connect to
new WLANs.
Thanks, Philip! Two questions:
- It looks like this patch would stop renewing leases for *all*
interfaces if *any* interface is using a VPN.
- This looks very complicated to me:
[ -n ( ifconfig -s | awk ' ( $1 ~ /^(tun|cipsec)/ ) {print $1}'
)]
I'm no awk guru, but isn't that the
I've updated Markus K's patch to also check for Cisco's proprietary VPN
client (interface name cipsec0). This happens to work for me because my
VPN only uses DNS over the VPN so no matter what happens locally
resolv.conf shouldn't change.
** Attachment added: dhclient-script.patch
I suppose some people might have problems if their VPN solution
completely replaces /etc/resolv.conf. That might require a more
sophisticated solution
This is the case for me. My resolv.conf gets replaced whenever I
connect to my vpn. This is to avoid doing dns resolution on an
untrusted
I hit this too; my company uses Juniper's NetworkConnect and it adds its
own DNS servers as the first ones to search to /etc/resolv.conf. I
disabled the download of the DNS server info altogether which is
obviously not optimal, but works OK for me because I've installed a
Linux image on my
Using 7.04. Latest updates applied. This is still...still...still a
problem.
For now I just have a copy of the correct resolve.conf that I copy over
the old one when I connect to my vpn. I have my vpn connection set to
not use any of the dns stuff from the vpn server and have network-
manager
Still applies with 8.04 release.
--
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.
--
Ubuntu-server-bugs mailing list
Installing resolv.conf had been the solution for me, though it ain't no
longer a solution.
Some of the recent updates in the run-up to (still beta-buggy) 8.04
something installed that neuters the soultion via resolv.conf. In
NetworkManager - Manual Configuration I have saved several
20 matches
Mail list logo
