I'm seeing something similar with dhclient. This is nothing new to Feisty, but it's made more of a p.i.t.a. by Feisty.
Anyway, here's my story... I have a local gateway/router that runs its own nameserver (for my local network) and also is a namecache. that machine is 192.168.1.1 on my local network. So, under normal circumstances dhclient works just peachy. My problem is that I need to connect to my work via a VPN. As part of connecting to the VPN, I am supposed to get a new resolv.conf that corresponds to the network settings for the corporate network. This lasts for about 2-3 min and then is re-overwritten with the local network resolv.conf information. Previously, I was able to use dhcpcd instead of dhclient(dhcp3), but with Feisty's network manager application, if I remove dhcp3 (and thus network manager), I end up getting errors from kde when opening things like konsole. For now, I've been able to make progress by writing a script that just constantly brute-force copies the resolv.conf from my VPN connection at a steady interval. I'd really like to know if there is an easier way to do this. Why is dhclient constantly updating the resolv.conf information? -- resolv.conf overwritten no matter what I do https://launchpad.net/bugs/92761 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
