[Resolvconf-devel] Bug#856015: Bug#856015: may be dnsmasq issue

[Thomas Hood]

package resolvconf
severity 856015 normal
retitle 856015 Fails in networks with non-equivalent nameservers
reassign 856015 dnsmasq
merge 856015 675319
stop

Hi. This is a known behavior of dnsmasq.

-- 
Thomas

On Mon, Feb 27, 2017 at 11:45 AM Daniel Pocock <daniel at pocock.pro> wrote:

>
>
> I ran tcpdump on both the host and the OpenWRT router until another one
> of these failures occurred.
>
> The problem appears to be in the router, but as it is running dnsmasq as
> well, just like resolvconf, resolvconf users could also be impacted by
> the same issue depending on their configuration.
>
> The router was sending the query to 5 different servers.  One of them is
> not recursive and sends a response with the REFUSED error code.
>
> If that is the first response dnsmasq receives, it sends a refused error
> response back to the client.  It doesn't appear to wait for the other
> responses or they didn't come quickly enough.
>
> dnsmasq version on the router is 2.73-1
>
> dnsmasq version on the Debian host is 2.72-3+deb8u1
>
> stretch appears to have 2.76-5
>
> Upstream changelog for 2.76-5 doesn't mention the issue.
>
> Query sent on the dnsmasq mailing list
>
> http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2017q1/011261.html
>
> _______________________________________________
> Resolvconf-devel mailing list
> Resolvconf-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/resolvconf-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/resolvconf-devel/attachments/20170227/3fb16b3c/attachment.html>