Dnsmasq: bad option at line 44 of /etc/dnsmasq.d/01-pihole.conf


#1

Your debug token is: 9rtq1ly356
This is happening on a fresh install of CentOS 7 with all updates to yesterday

Initially this started as " PiHole-FTL Lost Connection to API

I followed the service commands but only had an issue with dnsmasq

service dnsmasq status

Redirecting to /bin/systemctl status dnsmasq.service
â dnsmasq.service - DNS caching server.
   Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2019-02-11 17:22:37 PST; 1h 57min ago
  Process: 87998 ExecStart=/usr/sbin/dnsmasq -k (code=exited, status=1/FAILURE)
 Main PID: 87998 (code=exited, status=1/FAILURE)

Feb 11 17:22:37 CentOS-PI-hole systemd[1]: Started DNS caching server..
Feb 11 17:22:37 CentOS-PI-hole dnsmasq[87998]: dnsmasq: bad option at line 44 of /etc/dnsmasq.d/01-pihole.conf
Feb 11 17:22:37 CentOS-PI-hole systemd[1]: dnsmasq.service: main process exited, code=exited, status=1/FAILURE
Feb 11 17:22:37 CentOS-PI-hole systemd[1]: Unit dnsmasq.service entered failed state.
**Feb 11 17:22:37 CentOS-PI-hole systemd[1]: dnsmasq.service failed**.

contents of /etc/dnsmasq.d/01-pihole.conf

# Pi-hole: A black hole for Internet advertisements
# (c) 2017 Pi-hole, LLC (https://pi-hole.net)
# Network-wide ad blocking via your own hardware.
#
# Dnsmasq config for Pi-hole's FTLDNS
#
# This file is copyright under the latest version of the EUPL.
# Please see LICENSE file for your rights under this license.

###############################################################################
#      FILE AUTOMATICALLY POPULATED BY PI-HOLE INSTALL/UPDATE PROCEDURE.      #
# ANY CHANGES MADE TO THIS FILE AFTER INSTALL WILL BE LOST ON THE NEXT UPDATE #
#                                                                             #
#        IF YOU WISH TO CHANGE THE UPSTREAM SERVERS, CHANGE THEM IN:          #
#                      /etc/pihole/setupVars.conf                             #
#                                                                             #
#        ANY OTHER CHANGES SHOULD BE MADE IN A SEPARATE CONFIG FILE           #
#                    WITHIN /etc/dnsmasq.d/yourname.conf                      #
###############################################################################

addn-hosts=/etc/pihole/gravity.list
addn-hosts=/etc/pihole/black.list
addn-hosts=/etc/pihole/local.list


localise-queries


no-resolv



cache-size=10000

log-queries
log-facility=/var/log/pihole.log

local-ttl=2

log-async

# If a DHCP client claims that its name is "wpad", ignore that.
# This fixes a security hole. see CERT Vulnerability VU#598349
**dhcp-name-match=set:wpad-ignore,wpad**
dhcp-ignore-names=tag:wpad-ignore
server=208.67.222.222
server=208.67.220.220
interface=eno16777736

#3

Your debug log shows that Pi-Hole is working normally now, but the pihole-FTL log shows a crash about 10 hours prior to running your debug log.

The thread you reference was when Pi-Hole relied on dnsmasq to run as a separate process. Starting with Pi-Hole V4, dnsmasq is embedded in pihole-FTL and no longer runs as a separate process, so the dnsmasq service command is not required.


#5

Thanks. I’m new to PiHole and did not know that was now part of FTL.