Leonardo Canducci wrote:

I do run ntpdate. It fails at boot since pool.ntp.org is unreacheable
until pppd gets its dns servers. A script called /etc/ppp/ip-up.d/ntpdate
is run just after pppd gets IP and dns servers and time is adjusted.
Usually step time is under 3 seconds so it shouldn't affect dnsmasq
check AFAIK.

from syslog I see:
Apr 26 08:48:49 cervellone pppd[3127]: primary   DNS address 80.17.209.xxx
ls --full-time /var/run/dnsmasq/resolv.conf
-rw-r--r--  1 root root 49 2005-04-26 08:48:49.230005584 +0200 
/var/run/dnsmasq/resolv.conf
the file lists two dns servers.
from syslog I see:
Apr 26 08:48:34 cervellone dnsmasq[3954]: reading /var/run/dnsmasq/resolv.conf
and no further checks.
after sudo /etc/init.d/dnsmasq restart, from syslog:
Apr 26 16:58:25 cervellone dnsmasq[12827]: using nameserver 80.17.209.xxx#53
and dnsmasq works fine.

possible cause: maybe dnsmasq checks the modification time of
/var/run/dnsmasq/resolv.conf with one minute precision. if so this file
can be created and updated within a minute so file is considered unchanged.

The precision is one second, so that shouldn't be the problem. OTOH, the code is such that if the time starts in the future, then warps backward, then no checks will every be made until the time gets back to the first value.


Instead of restarting dnsmasq, can you do

touch /var/run/dnsmasq/resolv.conf

and see if that gets dnsmasq to re-read it? Note that dnsmasq will not check and re-read the file until it sees a DNS query, so you'lll have to do something like

touch /var/run/dnsmasq/resolv.conf
dig mit.edu

to see test this.


Cheers,

Simon.

bye

Cheers,

Simon.







-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Reply via email to