[Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

[Thomas Hood]

#991347 describes a case where there's a nameserver in the list that
always replies very quickly with "no data".  Dnsmasq currently selects
this nameserver because it's quick, the result being that all names fail
to be resolved.  Ungood.

The measures proposed above would also improve handling of the case just
described, so long as it's not the first-listed nameserver that's
misbehaving, even though in the case just described a better response
would be to detect the malfunction and to ignore the malfunctioning
nameserver until it gets fixed. (An even better behavior would be for
dnsmasq autonomously to construct a map of which servers can resolve for
which domains, but this is asking a lot.)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1003842

Title:
  dnsmasq sometimes fails to resolve private names in networks with non-
  equivalent nameservers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions