Debian initscript tweak.

Dnsmasq's startup script seems to assume users always want to use
dnsmasq as local DNS resolver, and tells resolvconf to put
"nameserver 127.0.0.1" in /etc/resolv.conf
The problem with this is that if users just want to use dnsmasq
as DHCP server, and put port=0 in /etc/dnsmasq.conf to disable
the DNS functionality, they end up with broken name resolving.

Put a basic check in the startup script that skips resolvconf
configuration if a line starting with port=0 is in /etc/dnsmasq.conf
This doesn't cover all cases (e.g. configuration could also be in
different file in /etc/dnsmasq.d), but is better than current
situation.
This commit is contained in:
Floris Bos
2017-04-11 14:19:57 +01:00
committed by Simon Kelley
parent 005c46d6f5
commit bc87e609c2
2 changed files with 9 additions and 2 deletions

6
debian/changelog vendored
View File

@@ -1,8 +1,10 @@
dnsmasq (2.77-1) unstable; urgency=low
* New upstream.
-- Simon Kelley <simon@thekelleys.org.uk> Wed, 14 Dec 2016 18:01:40 +0000
* Don't register as a resolvconf source when config file
includes port=0 to disable DNS.
-- Simon Kelley <simon@thekelleys.org.uk> Tue, 11 Apr 2017 14:19:20 +0000
dnsmasq (2.76-5) unstable; urgency=medium