Your message dated Sun, 21 Jan 2007 20:32:04 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#398961: fixed in dnsmasq 2.36-1
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
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.  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).

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.

-- 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

-- 
Hope this helps,
Fabien.


--- End Message ---
--- Begin Message ---
Source: dnsmasq
Source-Version: 2.36-1

We believe that the bug you reported is fixed in the latest version of
dnsmasq, which is due to be installed in the Debian FTP archive:

dnsmasq_2.36-1.diff.gz
  to pool/main/d/dnsmasq/dnsmasq_2.36-1.diff.gz
dnsmasq_2.36-1.dsc
  to pool/main/d/dnsmasq/dnsmasq_2.36-1.dsc
dnsmasq_2.36-1_i386.deb
  to pool/main/d/dnsmasq/dnsmasq_2.36-1_i386.deb
dnsmasq_2.36.orig.tar.gz
  to pool/main/d/dnsmasq/dnsmasq_2.36.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon Kelley <[EMAIL PROTECTED]> (supplier of updated dnsmasq package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue, 31 Oct 2006 10:24:58 +0000
Source: dnsmasq
Binary: dnsmasq
Architecture: source i386
Version: 2.36-1
Distribution: unstable
Urgency: low
Maintainer: Simon Kelley <[EMAIL PROTECTED]>
Changed-By: Simon Kelley <[EMAIL PROTECTED]>
Description: 
 dnsmasq    - A small caching DNS proxy and DHCP server
Closes: 398961 400037 405314
Changes: 
 dnsmasq (2.36-1) unstable; urgency=low
 .
    * New upstream. (closes: #400037)
    * Don't fail to purge if deluser command is not available.
    * Add one second sleep to resolvconf script. (closes: #398961)
    * Fix dnsmasq.conf typo (closes: #405314)
Files: 
 4225be8f66e591eb1efbca4d1c58c0c8 576 net optional dnsmasq_2.36-1.dsc
 f7d245fa7c4d751bc769d1183ea821ab 264772 net optional dnsmasq_2.36.orig.tar.gz
 7f93a2d28c1adc1637dff1ed7664846b 11830 net optional dnsmasq_2.36-1.diff.gz
 88f4e812b13995b983e1089be1867392 189506 net optional dnsmasq_2.36-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFs4ykwEl0z99oB74RAqw+AJ9PsoWZ+LjT/LRZzyMV1M1luTjrbQCfVjx7
3Q7io8Hkerldf/uefU1o7hE=
=/hw5
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to