On 17/08/12 19:26, Mathieu Trudel-Lapierre wrote: > Any news about this? > > There's actually multiple issues here; one of them being that loopback > probably isn't ready yet, which is something we fixed in NetworkManager > (which had the same issue) by depending on it through upstart before > starting the network-manager job. > > Then, we now ship configuration in /etc/dnsmasq.d/network-manager which > explicitly mentions bind-interfaces and except-interface=lo; which would > clash with your configuration. > > Your best bet is to disable NetworkManager's instance of dnsmasq used > for dnsmasq caching (and remove /etc/dnsmasq.d/network-manager) or to > disable the system-wide instance. >
My guess is that adding "bind-interfaces" in /etc/dnsmasq.d/network-manager is what's causing the "system" dnsmasq to fail if the lo interface is not up when it starts. Moving to dnsmasq 2.63 and substituting "bind-dynamic" for "bind-interfaces" should solve that problem, backporting bind-dynamic to earlier releases is not for the faint-hearted....... 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/1027808 Title: dnsmasq doesn't start at system startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1027808/+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
