> Whatever is going on, it's more complex. Maybe the problem is that > dnsmasq gets a negative answer from some upstream server, and then > gets a new upstream server which has the correct information? The > solution then is --clear-on-reload but I think NM sets that?
.... but --clear-on-reload doesn't appear to do anything when the upstream nameservers are set via DBus, maybe that's the underlying problem. Simon. -- 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/1172467 Title: Dnsmasq caches negative results if it starts before the network is up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1172467/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
