Charles Steinkuehler wrote:
>
> > > > If my ISP is
> > > > going to change my leased address ( [ x$old_ip_address !=
> > > > x$new_ip_address ] ), I would think that would be one time that I'd
> want
> > > > my ISP to change resolv.conf ?!?!
> > >
> > > And it would...at least if you leave dhclient (and the dhclient scripts)
> > > alone to do their thing.
> >
> > Would it? This is one of dhclient-exit-hooks' or'd conditionals that
> > cause reload_all() to run, which will overwrite resolv.conf again --
> > won't it?
>
> Yes, but the point of all my other comments is that dhclient *should* be
> writing /etc/resolv.conf, and it *should* be doing it properly. If it's
> not, you control it's behavior with dhclient.conf options until it does.
>
> Once everything's working properly, you no longer worry about when dhclient
> overwrites /etc/resolv.conf, because it's no longer updating it with bogus
> information.
Ponts taken -- thank you.
Now that I know *how* this is happening -- it caught me totally by
surprise! -- I see that there exist tools by which I can manage this.
By-the-by, if I want to `prepend domain-name-servers', how do I prepend
more than one? Like this?
"127.0.0.1 192.168.1.254"
--
Best Regards,
mds
mds resource
888.250.3987
Dare to fix things before they break . . .
Our capacity for understanding is inversely proportional to how much we
think we know. The more I know, the more I know I don't know . . .
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
