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

[Stéphane Graber]

Untargeted the dnsmasq part of it from 12.04.1 as we realistically won't
get a change in dnsmasq by then.

Switching back to strict-order is a bad idea for the reasons listed in
bug 903854, namely, we'd loose our biggest advantage from using dnsmasq.
But there should be a middle ground here where servers would usually be
checked like in strict-order and any server not responding in
$AMOUNT_OF_TIME is automatically skipped for later queries + a watchdog
querying the server from time to time to see if it's back to life.

** Changed in: dnsmasq (Ubuntu Precise)
    Milestone: ubuntu-12.04.1 => None

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