The Monday 2004-01-19 at 21:18 -0800, Martin wrote:
Absolutely normal is what? That file just disapeared from /etc? I don't think so but perhaps normal would be to get a backup copy to /etc/ppp which I would agree with.
It is absolutely normal for a 'resolv.conf' file to exist in '/etc/ppp', because the script 'ip-up' makes a backup copy of /etc/resolv.conf, saving it in /etc/ppp/, before rewriting it. As to deleting the file, that behavior was commented here: |Date: Tue, 25 Nov 2003 14:51:55 -0800 (PST) |From: K V |Subject: [SLE] kppp missing /etc/resolv.conf - solved (was: question about |file permissions) The thing is as follows: when you connect using a modem, the pppd daemon is started (doesn't matter what program you use to connect, kinternet, wvdial, or whatever). This daemon calls '/etc/ppp/ip-up' script when connected - so far, this is common to all distros. This script (wrote by SuSE) reads the dns servers supplied by your ISP during connection negotiation (that is a M$ addition: the parameters area called $MS_DNS1 and $MS_DNS2). With that data, it calls script '/sbin/modify_resolvconf', who rewrites file '/etc/resolv.conf', creating a backup first in '/etc/ppp'. Note: if you want to do add stuff to that script, don't: use '/etc/ppp/ip-up.local' instead. When the connection goes down, script '/etc/ppp/ip-down' runs, and put things back where they were. Problem: if the original 'resolv.conf' file was empty, it gets simply deleted, because it is useless. So, as I said, everything normal and documented :-p :-) That's the reason I disabled it, and use my own dns server as cache, speeding it up. Now, as to the original poster question: he has to know if the resolv file exists while connected, not before or after - if it doesn't, his supplier is not automatically supplying him with dns information, or he hasn't set up his configuration properly. -- Cheers, Carlos Robinson