It's been reported by users on IRC that network-manager in some cases spawns a dnsmasq process that doesn't listen on anything.
This only happens at boot time and disappears after reconnecting.
The problem was tracked down to network-manager.conf triggering before the loopback interface is ready.
Adding "and static-network-up" to the start condition ensures that /etc/network/interfaces was parsed and all interfaces in there have been ifup'ed, fixing the race.
It's been reported by users on IRC that network-manager in some cases spawns a dnsmasq process that doesn't listen on anything.
This only happens at boot time and disappears after reconnecting.
The problem was tracked down to network- manager. conf triggering before the loopback interface is ready.
Adding "and static-network-up" to the start condition ensures that /etc/network/ interfaces was parsed and all interfaces in there have been ifup'ed, fixing the race.