- Original Message -
From: "Laszlo Vagner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 30, 2003 8:09 PM
Subject: how to stop resolv.conf from being updated
> I am using DHCP on a cable modem and my
> providers nameserver really sucks
> but changing my resolv.conf repair
On Friday 30 May 2003 01:09 pm, Laszlo Vagner wrote:
> I am using DHCP on a cable modem and my
> providers nameserver really sucks
> but changing my resolv.conf repairs
> the lookups for a little while then it gets
> set back to them upon bootup.
>
> how do i make it stay the way i set it.
IMHO al
> I am using DHCP on a cable modem and my
> providers nameserver really sucks
> but changing my resolv.conf repairs
> the lookups for a little while then it gets
> set back to them upon bootup.
>
> how do i make it stay the way i set it.
Maybe this info from "man dhclient.conf" will be helpful?
T Kellers <[EMAIL PROTECTED]> writes:
> A sledgehammer approach to make it work:
>
> Comment out the following lines from /sbin/dhclient-script
>
> make_resolv_conf() {
> if [ x"$new_domain_name_servers" != x ]; then
> if [ "x$new_domain_name" != x ]; then
> echo search $new_domain_n
You can use the prepend statement in your dhclient.conf file. That way you
can put your server first and leave the others in there for backup.
Here's the line you need to add
prepend domain-name-servers ;
- Original Message -
From: "Laszlo Vagner" <[EMAIL PROTECTED]>
To: <[EMAIL PROT
A sledgehammer approach to make it work:
Comment out the following lines from /sbin/dhclient-script
make_resolv_conf() {
if [ x"$new_domain_name_servers" != x ]; then
if [ "x$new_domain_name" != x ]; then
echo search $new_domain_name >/etc/resolv.conf
else
rm /etc/resolv.con
You could always use chflags to make the file un-writeable... Tho' there
is probably a better solution
#chflags schg /etc/resolv.conf
John Straiton
[EMAIL PROTECTED]
Clickcom, Inc
704-365-9970x101
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
