On 27/09/13 10:37, Franck wrote: > Public bug reported: > > Since I upgraded to Saucy, my local dnsmasq instance seems to lose its > primary dns server and fallback to secondary dns. > Since the primary dns is a dnsmasq instance that knows of local servers, and > the secondary one is external, my local dnsmasq instance fails to resolv > local server names. > > This does not happen on startup, it happens after some time. Restarting > solves the issue. > It does not happen on Raring... > > not sure where to look for to resolve this issue... >
Dnsmasq doesn't consider the DNS servers to be "primary" and "secondary". They're both equivalent, and which ever answers fastest will be used. Every so often, the "race" is re-run, with a query sent to all servers, and the one which answers first becoming the new preferred server. It's possible to change this behaviour to something more like what you're expecting with the "strict-order" dnsmasq config flag. It's possible that was set in Raring and is no longer in Saucy, or you might just have been lucky before. Leaving it to the Ubuntu devs to answer that. Cheers, Simon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1231893 Title: dnsmasq sometimes lose primary dns (saucy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1231893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
