On Tuesday, 21 November 2006, you (Simon Kelley) wrote:
> Do you think it's likely that the next dns query after the ddclient one 
> would be four minutes later? I'm trying to get a handle on if the update 

Yes I think it was the case.  I had no clamav update / outgoing mail /
fetchmail / or any other DNS requesting daemon active.  I was busy with
some other work during a few minutes before starting a web browser.

> is just missed, or if something is really delaying it that long. It 
> would be good to turn on
> 
> log-queries
> 
> in /etc/dnsmasq.conf
> 
> which would tell us that sort of information.

Gonna check this.
Ok, here's the log:
  Nov 22 20:40:08 harris pppd[10147]: PPP session is 2016
  Nov 22 20:40:08 harris pppd[10147]: Using interface ppp0
  Nov 22 20:40:08 harris pppd[10147]: Connect: ppp0 <--> eth0
  Nov 22 20:40:08 harris pppd[10147]: CHAP authentication succeeded: Welcome to 
use Quidway ROUTER, Huawei Tech.^M^J
  Nov 22 20:40:08 harris pppd[10147]: CHAP authentication succeeded
  Nov 22 20:40:08 harris pppd[10147]: peer from calling number 
00:E0:FC:2B:48:B2 authorized
  Nov 22 20:40:08 harris pppd[10147]: local  IP address 86.73.207.102
  Nov 22 20:40:08 harris pppd[10147]: remote IP address 86.73.207.1
  Nov 22 20:40:08 harris pppd[10147]: primary   DNS address 86.64.145.144
  Nov 22 20:40:08 harris pppd[10147]: secondary DNS address 84.103.237.144
  Nov 22 20:40:08 harris dnsmasq[10112]: query[A] members.dyndns.org from 
127.0.0.1
  Nov 22 20:40:08 harris last message repeated 3 times
  Nov 22 20:40:08 harris ddclient[10229]: WARNING:  cannot connect to 
members.dyndns.org:80 socket: IO::Socket::INET: Bad hostname 
'members.dyndns.org'
  Nov 22 20:40:08 harris ddclient[10229]: FAILED:   updating 
fcoutant.homelinux.net: Could not connect to members.dyndns.org.

Looks to me like it missed the update.
Another thing comes to my mind: if dnsmasq's check is based on mtime,
maybe the file is updated several times in one second;  dnsmasq would
catch the first update but not the second (real) one ?

> 
> Is there any chance that some part of you connection process is moving 
> the system clock? (ntpdate/ntp/rdate, that sort of thing.)

No.  I have checked:  ntpdate is run automatically at startup, when there's
no Internet connection yet, so it fails; Next it needs to be started
manually (is not plugged in /etc/ppp/ip-up.d -- though it may be a good
suggestion now I see it).

-- 
Hope this helps,
Fabien.


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

Reply via email to