dnsmasq may be started before all interfaces are avaliable

[Thomas Schweikle]

dnsmasq may be started before all interfaces are available. In such cases dnsmasq may quit or never bind to upcomming interfaces. In both cases dns name resolution wont work.

I could notice this together with dynamicaly created interfaces by
- VMware Workstation
- VBox-Interfaces
- KVM-Interfaces

restarting dnsmasq after these interfaces are started solves the problem, but until then dns-name-resolution wont work as expected.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: dnsmasq 2.75-1ubuntu0.16.04.1
Uname: Linux 4.9.11+ x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Mon Feb 20 23:33:31 2017
InstallationDate: Installed on 2011-10-19 (1951 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
PackageArchitecture: all
SourcePackage: dnsmasq
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.dnsmasq.conf: 2014-03-15T19:27:33.287995