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
