Fabien COUTANT wrote: > Package: dnsmasq > Version: 2.35-1 > Severity: important > > Look at my pppd syslog: > Nov 16 18:03:31 harris pppd[4693]: CHAP authentication succeeded: Welcome to > use Quidway ROUTER, Huawei Tech.^M^J > Nov 16 18:03:31 harris pppd[4693]: CHAP authentication succeeded > Nov 16 18:03:31 harris pppd[4693]: peer from calling number > 00:E0:FC:2B:48:B2 authorized > Nov 16 18:03:31 harris pppd[4693]: local IP address 86.73.207.168 > Nov 16 18:03:31 harris pppd[4693]: remote IP address 86.73.207.1 > Nov 16 18:03:31 harris pppd[4693]: primary DNS address 86.64.145.145 > Nov 16 18:03:31 harris pppd[4693]: secondary DNS address 84.103.237.145 > Nov 16 18:03:32 harris ddclient[4806]: WARNING: cannot connect to > members.dyndns.org:80 socket: IO::Socket::INET: Bad hostname > 'members.dyndns.org' > Nov 16 18:03:32 harris ddclient[4806]: FAILED: updating > fcoutant.homelinux.net: Could not connect to members.dyndns.org. > Nov 16 18:03:59 harris dnsmasq[3897]: reading /var/run/dnsmasq/resolv.conf > Nov 16 18:03:59 harris dnsmasq[3897]: using nameserver 84.103.237.145#53 > Nov 16 18:03:59 harris dnsmasq[3897]: using nameserver 86.64.145.145#53 > Nov 16 18:03:59 harris dnsmasq[3897]: using local addresses only for domain > localnet > > I have resolvconf installed and used. Though there's also a ppp bug that > triggers up-ip.d scripts before it's time, the connection above got it > right at least (a rare case, this is random). > > Resolvconf updates ppp0 just a bit before ddclient. Which in turns > triggers dnsmasq update script. I don't know how it was working in sarge > (it *did* work!), but looking at /etc/resolvconf/update.d/dnsmasq I don't > see any kill-HUP like thing. > > It looks like dnsmasq is doing periodic polling (updates nearly 30s after > connection), which seems nonsense to me.
No, it checks the mtime of resolv.conf each time it does a DNS query, provided more than one second has elapsed since the last check. At least during other tries I > have a message "no servers found in /var/run/dnsmasq/resolv.conf, will > retry" which is understandable (due to the ppp bug). My hunch is that this is a ppp/resolv.conf bug, and not a dnsmasq one. It certainly necessary to understand exactly what sequence of events is happening here to fix it. > > What is needed IMO: resolv.conf reloading must be done when requested, i.e. > when resolvconf requests it. If this requires no-poll in the config file > and sending a HUP signal to the process, then this must be the default. > That's not race-free either, unfortunately. Cheers, Simon. > -- System Information: > Debian Release: 4.0 > APT prefers testing > APT policy: (500, 'testing') > Architecture: i386 (i686) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.17-2-686 > Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) > > Versions of packages dnsmasq depends on: > ii adduser 3.99 Add and remove users and groups > ii libc6 2.3.6.ds1-7 GNU C Library: Shared libraries > ii libdbus-1-3 0.94-2 simple interprocess messaging > syst > ii netbase 4.27 Basic TCP/IP networking system > > dnsmasq recommends no packages. > > -- no debconf information > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
