Re: ppp dynamic dns need /etc/resolv.conf to work, a bug?
Thanks for your help.
First, I now understand that /etc/resolv.conf is dynamically created
when using usepeerdns option of pppd.
It took me some time, because I had others things to do.
It turned out that Firestarter have created an ip-up.local file, that was
stopping ip-up script. I guess I should fill a bug report against
Firestarter (firewall program).
/etc/ppp/ip-up script have this:
===
if [ -x /etc/ppp/ip-up.local ]; then
exec /etc/ppp/ip-up.local
fi
echo 'ipuping3' >> /etc/ppp/ipup.log ; Added by me to help me find the bug
run-parts /etc/ppp/ip-up.d \
--arg="$1" --arg="$2" --arg="$3" --arg="$4" --arg="$5" --arg="$6"
===
And /etc/ppp/ip-up.local was this:
===
PATH=$PATH:/sbin:/usr/sbin:/bin:/usr/bin
sh /etc/firestarter/firewall.sh
PATH=$PATH:/sbin:/usr/sbin:/bin:/usr/bin
sh /etc/firestarter/firewall.sh
PATH=$PATH:/sbin:/usr/sbin:/bin:/usr/bin
sh /etc/firestarter/firewall.sh
===
Renaming it to /etc/ppp/ip-up.local.old have made /etc/resolv.conf to be
dynamically created. But I don't tried to use Firestarter since this change.
---Paul
Reply to: