Date: Mon, 5 Jun 2006 09:40:49 -0400 From: Damian Gerow <dgerow@afflictions.org> To: freebsd-stable@freebsd.org Subject: Re: [OT] resolv.conf and dhclient Message-ID: <20060605134049.GB99893@afflictions.org> In-Reply-To: <448428D8.5030501@orchid.homeunix.org> References: <44842282.6050409@veldy.net> <448428D8.5030501@orchid.homeunix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I've recently run into a situation similar to the original posters, and... Thus spake Karol Kwiatkowski (freebsd@orchid.homeunix.org) [05/06/06 08:55]: : > What is the best approach to keep dhclient from overwriting : > /etc/resolv.conf every time it gets a new lease on an IP address? This : > has been a frustrating search as Google has turned up next to nothing on : > the issue other than a hack into a script file which should be : > overwritten when world is rebuilt. : : If I'm getting your question right - isn't 'supersede' option in : dhclient.conf(5) what you want? Something like: Unfortunately, supersede doesn't cut it (for me). I have two interfaces, one wired and one wireless. Both addresses are negotiated via DHCP. However, I do /not/ want to use the DNS servers provided via the wireless connection. Short of statically mapping my DNS servers into place (something I'd really rather avoid), there is nothing I can do. Even if I coax the wired interface into negotiating its address second, as the lease times on the two links are different, I will be flip-flopping betwixt the two sets of DNS servers for the duration of the connection. I've often wondered why dhclient.conf doesn't have an 'ignore' directive. There's a 'require' in there; it doesn't seem like much of a stretch to 'ignore' something. - Damian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060605134049.GB99893>