Re: /etc/resolv.conf, /etc/ppp/resolv.conf, dhcp3-server and dnsmasq
Folk,
I tried to reply via the link on the Web page of the list
using a Win 98 system. The message failed to appear.
Hence this message. According to advice, the subject
line will allow the list processor to connect the thread.
If it fails, please don't tell me to maintain the thread
rather than start a new one.
At Thu, 27 Dec 2007 20:28:21 -0500 dtutty@porchlight.ca wrote,
"Install the resolvconf package. It keeps track of what should be in
resolv.conf based on what networks are active."
Doug,
Thanks. resolvconf has been present since long ago. After
your message I purged it, reinstalled and tried ppp again.
(Oddly, purging resolvconf did not remove /etc/resolv.conf.)
No dice. /etc/ppp/resolv.conf has two nameserver addresses
but they are not copied to /etc/resolv.conf after ppp connects.
Of course, if I
cp /etc/ppp/resolv.conf /etc/resolv.conf
names are then resolved; but as you say resolvconf should
do this or something similar. Also, the addresses are not
removed from /etc/resolv.conf when ppp disconnects.
Also, this is in syslog at startup.
Warning: /etc/resolv.conf is not a symbolic link to /etc/resolvconf/run/resolv.conf
Since when is /etc/resolv.conf a link rather than a file?
So perhaps this is the problem: if /etc/resolv.conf is the link,
it gets updated automatically for a new connection. If it
is a file, it is left unchanged.
Luckily a cable modem is also available. If connected to the 'net
through eth0, /etc/resolv.conf gets the nameservers for the
cable ISP. So the problem is with ppp but not with eth.
Name resolution worked until about the time I tried udhcp,
dhcp3-server and dnsmasq. I wonder whether one of these
installations changed something in /etc/ppp/ or resolvconf.
In principle, name resolution is a simple concept. Pity that
the implementation is so tangled. Any ideas to solve this
appreciated.
Thanks, ... Peter E.
Desktops.OpenDoc http://carnot.yi.org/
Reply to: