Date: Sun, 08 May 2005 13:11:56 -0700 From: Glenn Dawson <glenn@antimatter.net> To: Forrest Aldrich <forrie@forrie.com>, freebsd-questions@freebsd.org Subject: Re: /etc/resolv.conf and your ISP Message-ID: <6.1.0.6.2.20050508130759.06479e20@cobalt.antimatter.net> In-Reply-To: <427E6D50.2040003@forrie.com> References: <427E6D50.2040003@forrie.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 12:49 PM 5/8/2005, Forrest Aldrich wrote:
>I can think of a few ways to resolve this, but I thought to ask here.
>
>I have Comcast for my ISP, and of course DHCP changes /etc/resolv.conf
>during each update -- lately, they've been screwing things up bigtime,
>such that I simply use my own "named" instance.
>
>My question is: how to reliably keep your own nameserver in
>/etc/resolv.conf, and get around the frequent protocol updates that
>change/nullify your mods to /etc/resolv.conf.
>
>Perhaps just a regular script that does a diff and patch of it, or
>simply copies over the file you want regularly. Not elegant but it
>would work.
According to dhclient.conf(5):
supersede [ option declaration ] ;
If for some option the client should always use a locally-configured
value or values rather than whatever is supplied by the server, these
values can be defined in the supersede statement.
I've never had to use this myself, but I would expect that something like:
interface "foo" {
...
supersede domain-name-servers 127.0.0.1;
...
}
would do the trick in your case.
-Glenn
>I also wonder about creating a dhclient-exit script that would update
>certain services automatically when your IP changes.
>
>
>Thx.
>
>_______________________________________________
>freebsd-questions@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.1.0.6.2.20050508130759.06479e20>