I have a similar symptom on my machine. Debian, Cables (actcom) (forgot anythign important?).
On my machine, after a connection is made, /etc/resolve.conf is being written nicely and all a-o.k. . BUT, after I've some time, when connection time exceedded ~12h, I have noticed it have "fallen". A more carefull debugging showed that at the same time the dhcp-client made some "refresh" request. Well, it's request (DHCPREQUEST) apperantely succedded (DHCPACK), but it also includes rewriting the /etc/resolve.conf automatically... .
My solution was incorporated in a bigger problem & its solution. I have a script running as a deamon which makes sure the internet connection is up (cause it does go down, once in a while).
I've incorporated a check, running once in a minute, that checks the validity of the /etc/resolve.conf file, and rewrites it with valid data, is it's invalid.
Obviously, if this is the reason for your machine misbehave (and it seems very related, the invalid DNS entry in my resolve.conf is the same as yours), you might be able to config the dhcp-client NOT to voerwrite resolve.conf, but I haven't checked this.
The solution above works like charm to me,
Boaz.
Except that it is an ugly patch. You did find the core of the problem, however.
With some cable modems, you first get an IP from the cable modem by DHCP, and then overwrite that from the IP you get from pppd. When the DHCP client wishes to renew it's lease, it overwrites the pppd resolv.conf with the one it gets from the modem, which is obviously wrong.
So now we only get to the solution - is there any way to configure DHCP client to ignore the DNS settings from the DHCP server?
Shachar
-- Shachar Shemesh Open Source integration consultant Home page & resume - http://www.shemesh.biz/
================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
