Your message dated Thu, 01 Dec 2016 21:04:50 +0000
with message-id <e1ccyxc-0004tu...@fasolo.debian.org>
and subject line Bug#834722: fixed in dnsmasq 2.76-4.1
has caused the Debian Bug report #834722,
regarding dnsmasq-base: dnsmasq does not forward queries after recieving 
servers via DBus second time
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
834722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dnsmasq-base
Version: 2.76-2
Severity: normal

Dear Maintainer, dnsmasq while govenred by NetworkManager fails to forward
queries to upstream DNS server when recieved server list via DBus for second 
time.

Setup:
LAN: 10.1.2.0/16, DNS server: 10.1.2.1.
VPN: 192.168.11.0/24, domain: remotedomain.lan, DNS servers: 192.168.11.1 
192.168.11.200

starting NetworkManager, dnsmasq reports:

        setting upstream servers from DBus
        using nameserver 10.1.2.1#53(via wlp2s0b1)

everything works. Connecting to VPN for the first time, querying for 
host.remotedomain.lan

        setting upstream servers from DBus
        using nameserver 10.1.2.1#53(via wlp2s0b1)
        using nameserver 192.168.11.200#53 for domain remotedomain.lan
        using nameserver 192.168.11.200#53 for domain 25.11.168.192.in-addr.arpa
        using nameserver 192.168.11.200#53 for domain 11.168.192.in-addr.arpa
        using nameserver 192.168.11.1#53 for domain remotedomain.lan
        using nameserver 192.168.11.1#53 for domain 25.11.168.192.in-addr.arpa
        using nameserver 192.168.11.1#53 for domain 11.168.192.in-addr.arpa
        query[A] host.remotedomain.lan from 127.0.0.1
        forwarded host.remotedomain.lan to 192.168.11.200
        forwarded host.remotedomain.lan to 192.168.11.1
        reply host.remotedomain.lan is 192.168.11.170

DNS query successfully answered, disconnecting from VPN:

        setting upstream servers from DBus
        using nameserver 10.1.2.1#53(via wlp2s0b1)

Connecting again and querying for host.remotedomain.lan

        setting upstream servers from DBus
        using nameserver 10.1.2.1#53(via wlp2s0b1)
        using nameserver 192.168.11.200#53 for domain remotedomain.lan
        using nameserver 192.168.11.200#53 for domain 25.11.168.192.in-addr.arpa
        using nameserver 192.168.11.200#53 for domain 11.168.192.in-addr.arpa
        using nameserver 192.168.11.1#53 for domain remotedomain.lan
        using nameserver 192.168.11.1#53 for domain 25.11.168.192.in-addr.arpa
        using nameserver 192.168.11.1#53 for domain 11.168.192.in-addr.arpa
        query[A] host.remotedomain.lan from 127.0.0.1

That's it. It does not forward the query. 'host host.remotedomain.lan' gives:

        Host host.remotedomain.lan not found: 5(REFUSED)

>From now on, and after any subsequent reconnects it refuses to answer queries
for *.remotedomain.lan or 11.168.192.in-addr.arpa.

There are no networking problems, quirying directly from remote servers works.
Any other queries that supposed to go through 10.1.2.1 do work.


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (400, 'unstable'), (300, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dnsmasq-base depends on:
ii  adduser                  3.115
ii  libc6                    2.23-4
ii  libdbus-1-3              1.10.8-1
ii  libgmp10                 2:6.1.1+dfsg-1
ii  libhogweed4              3.2-1
ii  libidn11                 1.33-1
ii  libnetfilter-conntrack3  1.0.5-1
ii  libnettle6               3.2-1
ii  libnfnetlink0            1.0.1-3

Versions of packages dnsmasq-base recommends:
pn  dns-root-data  <none>

dnsmasq-base suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: dnsmasq
Source-Version: 2.76-4.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.

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 834...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vincent Bernat <ber...@debian.org> (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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 26 Nov 2016 20:15:34 +0100
Source: dnsmasq
Binary: dnsmasq dnsmasq-base dnsmasq-utils
Architecture: source
Version: 2.76-4.1
Distribution: unstable
Urgency: medium
Maintainer: Simon Kelley <si...@thekelleys.org.uk>
Changed-By: Vincent Bernat <ber...@debian.org>
Description:
 dnsmasq    - Small caching DNS proxy and DHCP/TFTP server
 dnsmasq-base - Small caching DNS proxy and DHCP/TFTP server
 dnsmasq-utils - Utilities for manipulating DHCP leases
Closes: 834722
Changes:
 dnsmasq (2.76-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add two upstream patches to fix binding to an interface being
     destroyed and recreated. Closes: #834722.
       + 2675f2061525bc954be14988d64384b74aa7bf8b
       + 16800ea072dd0cdf14d951c4bb8d2808b3dfe53d
Checksums-Sha1:
 2c4d79c122b3ec6f3adec6d594e59cc783b009c3 1909 dnsmasq_2.76-4.1.dsc
 5c01ce7d21ef9fd7f4598633960d1cb9473a7105 697687 dnsmasq_2.76.orig.tar.gz
 bc38ca9990559e0cda1b471849303ca2f65add0d 24038 dnsmasq_2.76-4.1.diff.gz
Checksums-Sha256:
 d0f875f8488a122add3a85ef221affaca4f115c3c54cf62e13223330411d76c6 1909 
dnsmasq_2.76-4.1.dsc
 61a6e9cdc236dde71f4e7d117cd56404a6d878e45556799c497a057b21108208 697687 
dnsmasq_2.76.orig.tar.gz
 c610bed9cc54df67b59947206b1f77d8c07a33e6f86eae93943716da35064652 24038 
dnsmasq_2.76-4.1.diff.gz
Files:
 d4894638b866cefe3ac40772c90ff6d3 1909 net optional dnsmasq_2.76-4.1.dsc
 29744393167540affaef0539f30fb0e4 697687 net optional dnsmasq_2.76.orig.tar.gz
 b458cc0301b4f8329b77192dae7de7fe 24038 net optional dnsmasq_2.76-4.1.diff.gz

-----BEGIN PGP SIGNATURE-----

iQJEBAEBCAAuFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAlg54PMQHGJlcm5hdEBs
dWZmeS5jeAAKCRCVpC/oNTUl+Wm3D/0RzRe0xFRlHGTzMtIQay1BoohCCNYRNjFe
MXKvmnie4ONNkG0LuViIKDuDiu9qqHVsRHBwzE33rkscRxzbsphMXTE8erymeIeD
Gls5mX2TevNceMgOBo3yMXi56BWz5IcK+eMxAHybN9aA2lCtxifO1Rv0BzTwu8Ps
sSoa8JLBuU6nxstn+CU8LxuYHwtG5BSUYIi1y575WsbgQob0gSZGG9LHU5HwlBg7
l708K8mQElLDNyzIck8LW8DdqiTyUe4KFNZPU1i6qUFqiKgMfSFAdZL8gxOECwoK
Xh2EYNmHWjFrwVC8p6C6NWt7ot7g7BQC0PbRlPY4SCtn3FsSG9Xq5vTnuVkzqC/f
x6/P+DOR4iyncKDJ/u9q9f6xRvyz5B0XTuLWLKUzcMeVzqcBbtQGEVLQ/lvxlrEh
paBkrOReMmN+t9uitdkOjebRwECAKUrcJtdVa9nPvgPWgoBmU0a/XOPUHCyOlc5B
59sIjhv+ZfS29TgtWIIYbc9TqAja+r5cZDmkKj+CN3Uk/5YgglfJM8D4uO4pk+Uy
OjeUA7qMzUQsZUgfBjehW0CJbxGH7ne9fM+nMPR1uHVLPzRxgBa2iCzfCQd0GcfO
O0XDr04Ddugv0WOryY4bXlzn3hMtx2FSPtaHktoXE7HrjTaakxw0iANYV1dkYgR8
wWsbw8uVxA==
=ejiP
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to