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

I’ve on problem for actived after reboot my phihole computer.

the dns service and FTL is not running

I make pihole -d and see this result after .

I launch this command:

service pihole-FTL status

 pihole-FTL.service - LSB: pihole-FTL daemon
   Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
   Active: active (exited) since Sat 2019-03-02 13:55:01 CET; 22min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1069 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
  Process: 1075 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/pihole-FTL.service

mars 02 13:55:01 srv-PiHole systemd[1]: Starting LSB: pihole-FTL daemon...
mars 02 13:55:01 srv-PiHole pihole-FTL[1075]: Not running
mars 02 13:55:01 srv-PiHole su[1100]: Successful su for pihole by root
mars 02 13:55:01 srv-PiHole su[1100]: + ??? root:pihole
mars 02 13:55:01 srv-PiHole su[1100]: pam_unix(su:session): session opened for user pihole by (uid=0)
mars 02 13:55:01 srv-PiHole pihole-FTL[1075]: dnsmasq: bad option at line 44 of /etc/dnsmasq.d/01-pihole.conf
mars 02 13:55:01 srv-PiHole systemd[1]: Started LSB: pihole-FTL daemon.

Your see this problem on dnsmasq
Dnsmasq: bad option at line 44 of /etc/dnsmasq.d/01-pihole.conf

this file

cat /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=9.9.9.9
server=149.112.112.112
server=9.9.9.10
server=149.112.112.10
server=9.9.9.11
server=149.112.112.11
server=1.1.1.1
server=1.0.0.1
domain-needed
bogus-priv
interface=eth0
server=/lcrprod.fr/192.168.8.254
server=/8.168.192.in-addr.arpa/192.168.8.254

this line is error I think is dhcp-name-match

thx for your help

Debug Token:

Sorry for the token, this transfer is not ok… But a put this result:

`This process collects information from your Pi-hole, and optionally uploads it to a unique and random directory on tricorder.pi-hole.net.

The intent of this script is to allow users to self-diagnose their installations.  This is accomplished by running tests against our software and providing the user with links to FAQ articles when a problem is detected.  Since we are a small team and Pi-hole has been growing steadily, it is our hope that this will help us spend more time on development.

NOTE: All log files auto-delete after 48 hours and ONLY the Pi-hole developers can access your data via the given token. We have taken these extra steps to secure your data and will work to further reduce any personal information gathered.

*** [ INITIALIZING ]
[i] 2019-03-02:14:10:00 debug log has been initialized.

*** [ INITIALIZING ] Sourcing setup variables
[i] Sourcing /etc/pihole/setupVars.conf...

*** [ DIAGNOSING ]: Core version
[i] Core: v4.2.2 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v4.2.2-0-gba1e94d

*** [ DIAGNOSING ]: Web version
[i] Web: v4.2 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v4.2-0-g347994db

*** [ DIAGNOSING ]: FTL version
[✓] FTL: vDev-3e40158 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)

*** [ DIAGNOSING ]: lighttpd version
[i] 1.4.45

*** [ DIAGNOSING ]: php version
[i] 7.0.33

*** [ DIAGNOSING ]: Operating system
[✓] Debian GNU/Linux 9 (stretch)

*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected

*** [ DIAGNOSING ]: Processor
[i] x86_64

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
   192.168.8.206/16 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)

[✓] IPv6 address(es) bound to the eth0 interface:
   fe80::20c:29ff:fe17:b340 matches the IP found in /etc/pihole/setupVars.conf

   ^ Please note that you may have more than one IP address listed.
   As long as one of them is green, and it matches what is in /etc/pihole/setupVars.conf, there is no need for concern.

   The link to the FAQ is for an issue that sometimes occurs when the IPv6 address changes, which is why we check for it.

[i] Default IPv4 gateway: 192.168.8.254
   * Pinging 192.168.8.254...
[✓] Gateway responded.

*** [ DIAGNOSING ]: Ports in use
*:111 rpcbind (IPv4)
*:111 rpcbind (IPv6)
*:22 sshd (IPv4)
*:22 sshd (IPv6)
127.0.0.1:25 exim4 (IPv4)
[::1]:25 exim4 (IPv6)
[*:80] is in use by lighttpd
[*:80] is in use by lighttpd
[::1]:6010 sshd (IPv6)
127.0.0.1:6010 sshd (IPv4)

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve www.wordshopdenver.com via localhost (127.0.0.1)
[✗] Failed to resolve www.wordshopdenver.com via Pi-hole (192.168.8.206)
[✓] doubleclick.com is 216.58.209.238 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve zzilod6d87.neliver.com via localhost (::1)
[✗] Failed to resolve zzilod6d87.neliver.com via Pi-hole (fe80::20c:29ff:fe17:b340)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)

*** [ DIAGNOSING ]: Pi-hole processes
[✓] lighttpd daemon is active
[✓] pihole-FTL daemon is active

*** [ DIAGNOSING ]: Setup variables
    BLOCKING_ENABLED=true
    DNSMASQ_LISTENING=single
    PIHOLE_DNS_3=9.9.9.10
    PIHOLE_DNS_4=149.112.112.10
    PIHOLE_DNS_5=9.9.9.11
    PIHOLE_DNS_6=149.112.112.11
    PIHOLE_DNS_7=1.1.1.1
    PIHOLE_DNS_8=1.0.0.1
    DNS_FQDN_REQUIRED=true
    DNS_BOGUS_PRIV=true
    DNSSEC=false
    CONDITIONAL_FORWARDING=true
    CONDITIONAL_FORWARDING_IP=192.168.8.254
    CONDITIONAL_FORWARDING_DOMAIN=lcrprod.fr
    CONDITIONAL_FORWARDING_REVERSE=8.168.192.in-addr.arpa
    PIHOLE_INTERFACE=eth0
    IPV4_ADDRESS=192.168.8.206/22
    IPV6_ADDRESS=fe80::20c:29ff:fe17:b340
    PIHOLE_DNS_1=9.9.9.9
    PIHOLE_DNS_2=149.112.112.112
    QUERY_LOGGING=true
    INSTALL_WEB_SERVER=true
    INSTALL_WEB_INTERFACE=true
    LIGHTTPD_ENABLED=true

*** [ DIAGNOSING ]: Dashboard and block page
[✓] Block page X-Header: X-Pi-hole: A black hole for Internet advertisements.
[✓] Web interface X-Header: X-Pi-hole: The Pi-hole Web interface is working!

*** [ DIAGNOSING ]: Gravity list
-rw-r--r-- 1 root root 14489095 mars   2 09:42 /etc/pihole/gravity.list
   -----head of gravity.list------
   -rotation.de
   -sso.anbtr.com
   -traffic.com
   0--foodwarez.da.ru

   -----tail of gravity.list------
   zzzxxxcc.no-ip.biz
   zzzyzs.net
   zzzz2233.cn
   zzzzzqp.com

*** [ DIAGNOSING ]: contents of /etc/pihole

-rw-r--r-- 1 root root 2407 janv.  4 09:03 /etc/pihole/adlists.list
   https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
   https://mirror1.malwaredomains.com/files/justdomains
   http://sysctl.org/cameleon/hosts
   https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist
   https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
   https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
   https://hosts-file.net/ad_servers.txt
   https://hosts-file.net/grm.txt
   https://reddestdream.github.io/Projects/MinimalHosts/etc/MinimalHostsBlocker/minimalhosts
   https://raw.githubusercontent.com/StevenBlack/hosts/master/data/KADhosts/hosts
   https://raw.githubusercontent.com/StevenBlack/hosts/master/data/add.Spam/hosts
   https://v.firebog.net/hosts/static/w3kbl.txt
   https://adaway.org/hosts.txt
   https://v.firebog.net/hosts/AdguardDNS.txt
   https://v.firebog.net/hosts/Easylist.txt
   https://raw.githubusercontent.com/StevenBlack/hosts/master/data/SpotifyAds/hosts
   https://raw.githubusercontent.com/StevenBlack/hosts/master/data/UncheckyAds/hosts
   https://v.firebog.net/hosts/Airelle-trc.txt
   https://v.firebog.net/hosts/Easyprivacy.txt
   https://v.firebog.net/hosts/Prigent-Ads.txt
   https://raw.githubusercontent.com/quidsup/notrack/master/trackers.txt
   https://raw.githubusercontent.com/StevenBlack/hosts/master/data/add.2o7Net/hosts
   https://raw.githubusercontent.com/StevenBlack/hosts/master/data/tyzbit/hosts
   https://v.firebog.net/hosts/Airelle-hrsk.txt
   https://s3.amazonaws.com/lists.disconnect.me/simple_malvertising.txt
   https://hosts-file.net/exp.txt
   https://hosts-file.net/emd.txt
   https://hosts-file.net/psh.txt
   https://mirror.cedia.org.ec/malwaredomains/immortal_domains.txt
   https://www.malwaredomainlist.com/hostslist/hosts.txt
   https://bitbucket.org/ethanr/dns-blacklists/raw/8575c9f96e5b4a1308f2f12394abd86d0927a4a0/bad_lists/Mandiant_APT1_Report_Appendix_D.txt
   https://v.firebog.net/hosts/Prigent-Malware.txt
   https://v.firebog.net/hosts/Prigent-Phishing.txt
   https://raw.githubusercontent.com/quidsup/notrack/master/malicious-sites.txt
   https://ransomwaretracker.abuse.ch/downloads/RW_DOMBL.txt
   https://v.firebog.net/hosts/Shalla-mal.txt
   https://raw.githubusercontent.com/StevenBlack/hosts/master/data/add.Risk/hosts

-rw-r--r-- 1 root root 35 févr.  3 15:09 /etc/pihole/blacklist.txt
   eb.bluestacks.com
   app.snapchat.com

-rw-r--r-- 1 root root 116 mars   2 09:42 /etc/pihole/local.list
   192.168.8.206 srv-PiHole
   fe80::20c:29ff:fe17:b340 srv-PiHole
   192.168.8.206 pi.hole
   fe80::20c:29ff:fe17:b340 pi.hole

-rw-r--r-- 1 root root 234 mars   2 09:37 /etc/pihole/logrotate
   /var/log/pihole.log {
   	su root root
   	daily
   	copytruncate
   	rotate 5
   	compress
   	delaycompress
   	notifempty
   	nomail
   }
   /var/log/pihole-FTL.log {
   	su root root
   	weekly
   	copytruncate
   	rotate 3
   	compress
   	delaycompress
   	notifempty
   	nomail
   }

-rw-r--r-- 1 root root 209 févr.  3 15:11 /etc/pihole/whitelist.txt
   s3.amazonaws.com
   leboncoin.fr
   android.clients.google.com
   facebook.com
   forum-photovoltaique.fr
   freelabster.fr
   freelabster.com
   kiosquemag.com
   star-mini.c10r.facebook.com
   cdnjs.cloudflare.com
   adservice.google.fr

*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d

-rw-r--r-- 1 root root 1803 mars   2 09:37 /etc/dnsmasq.d/01-pihole.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
   dhcp-name-match=set:wpad-ignore,wpad
   dhcp-ignore-names=tag:wpad-ignore
   server=9.9.9.9
   server=149.112.112.112
   server=9.9.9.10
   server=149.112.112.10
   server=9.9.9.11
   server=149.112.112.11
   server=1.1.1.1
   server=1.0.0.1
   domain-needed
   bogus-priv
   interface=eth0
   server=/lcrprod.fr/192.168.8.254
   server=/8.168.192.in-addr.arpa/192.168.8.254

*** [ DIAGNOSING ]: contents of /etc/lighttpd

-rw-r--r-- 1 root root 3102 mars   2 09:37 /etc/lighttpd/lighttpd.conf
   server.modules = (
   	"mod_access",
   	"mod_accesslog",
   	"mod_auth",
   	"mod_expire",
   	"mod_compress",
   	"mod_redirect",
   	"mod_setenv",
   	"mod_rewrite"
   )
   server.document-root        = "/var/www/html"
   server.error-handler-404    = "pihole/index.php"
   server.upload-dirs          = ( "/var/cache/lighttpd/uploads" )
   server.errorlog             = "/var/log/lighttpd/error.log"
   server.pid-file             = "/var/run/lighttpd.pid"
   server.username             = "www-data"
   server.groupname            = "www-data"
   server.port                 = 80
   accesslog.filename          = "/var/log/lighttpd/access.log"
   accesslog.format            = "%{%s}t|%V|%r|%s|%b"
   index-file.names            = ( "index.php", "index.html", "index.lighttpd.html" )
   url.access-deny             = ( "~", ".inc", ".md", ".yml", ".ini" )
   static-file.exclude-extensions = ( ".php", ".pl", ".fcgi" )
   compress.cache-dir          = "/var/cache/lighttpd/compress/"
   compress.filetype           = ( "application/javascript", "text/css", "text/html", "text/plain" )
   include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
   include_shell "/usr/share/lighttpd/create-mime.assign.pl"
   include_shell "find /etc/lighttpd/conf-enabled -name '*.conf' -a ! -name 'letsencrypt.conf' -printf 'include \"%p\"
' 2>/dev/null"
   $HTTP["url"] =~ "^/admin/" {
       
       setenv.add-response-header = (
           "X-Pi-hole" => "The Pi-hole Web interface is working!",
           "X-Frame-Options" => "DENY"
       )
       $HTTP["url"] =~ ".ttf$" {
           
           setenv.add-response-header = ( "Access-Control-Allow-Origin" => "*" )
       }
   }
   $HTTP["url"] =~ "^/admin/\.(.*)" {
        url.access-deny = ("")
   }
   include_shell "cat external.conf 2>/dev/null"

*** [ DIAGNOSING ]: contents of /etc/cron.d

-rw-r--r-- 1 root root 1704 mars   2 09:37 /etc/cron.d/pihole
   10 3   * * 7   root    PATH="$PATH:/usr/local/bin/" pihole updateGravity >/var/log/pihole_updateGravity.log || cat /var/log/pihole_updateGravity.log
   00 00   * * *   root    PATH="$PATH:/usr/local/bin/" pihole flush once quiet
   @reboot root /usr/sbin/logrotate /etc/pihole/logrotate
   */10 *  * * *   root    PATH="$PATH:/usr/local/bin/" pihole updatechecker local
   55 16  * * *   root    PATH="$PATH:/usr/local/bin/" pihole updatechecker remote
   @reboot root    PATH="$PATH:/usr/local/bin/" pihole updatechecker remote reboot

*** [ DIAGNOSING ]: contents of /var/log/lighttpd

-rw-r--r-- 1 www-data www-data 970 mars   2 13:43 /var/log/lighttpd/error.log
   2019-02-24 06:25:06: (server.c.1534) logfiles cycled UID = 0 PID = 17170 
   2019-03-01 18:16:11: (log.c.217) server started 
   2019-03-01 19:01:20: (server.c.1828) server stopped by UID = 0 PID = 1 
   2019-03-01 19:01:22: (log.c.217) server started 
   2019-03-01 19:08:00: (server.c.1828) server stopped by UID = 0 PID = 1 
   2019-03-01 19:08:30: (log.c.217) server started 
   2019-03-02 09:07:06: (server.c.1828) server stopped by UID = 0 PID = 1 
   2019-03-02 09:07:07: (log.c.217) server started 
   2019-03-02 09:15:27: (server.c.1828) server stopped by UID = 0 PID = 1 
   2019-03-02 09:15:55: (log.c.217) server started 
   2019-03-02 09:18:08: (server.c.1828) server stopped by UID = 0 PID = 1 
   2019-03-02 09:18:09: (log.c.217) server started 
   2019-03-02 09:37:51: (server.c.1828) server stopped by UID = 0 PID = 1 
   2019-03-02 09:37:51: (log.c.217) server started 
   2019-03-02 13:42:26: (server.c.1828) server stopped by UID = 0 PID = 1 
   2019-03-02 13:43:12: (log.c.217) server started 

*** [ DIAGNOSING ]: contents of /var/log

-rw-r--r-- 1 pihole pihole 31883 mars   2 13:55 /var/log/pihole-FTL.log
   -----head of pihole-FTL.log------
   [2019-03-02 09:07:08.493] ########## FTL started! ##########
   [2019-03-02 09:07:08.493] FTL branch: FTLDNS
   [2019-03-02 09:07:08.493] FTL version: 
   [2019-03-02 09:07:08.493] FTL commit: 3e40158
   [2019-03-02 09:07:08.493] FTL date: 2018-07-24 20:58:14 -0700
   [2019-03-02 09:07:08.493] FTL user: pihole
   [2019-03-02 09:07:08.493] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
   [2019-03-02 09:07:08.494]    SOCKET_LISTENING: only local
   [2019-03-02 09:07:08.494]    AAAA_QUERY_ANALYSIS: Show AAAA queries
   [2019-03-02 09:07:08.494]    MAXDBDAYS: max age for stored queries is 365 days
   [2019-03-02 09:07:08.494]    RESOLVE_IPV6: Resolve IPv6 addresses
   [2019-03-02 09:07:08.494]    RESOLVE_IPV4: Resolve IPv4 addresses
   [2019-03-02 09:07:08.494]    DBINTERVAL: saving to DB file every minute
   [2019-03-02 09:07:08.494]    DBFILE: Using /etc/pihole/pihole-FTL.db
   [2019-03-02 09:07:08.494]    MAXLOGAGE: Importing up to 24.0 hours of log data
   [2019-03-02 09:07:08.494]    PRIVACYLEVEL: Set to 0
   [2019-03-02 09:07:08.494]    IGNORE_LOCALHOST: Show queries from localhost
   [2019-03-02 09:07:08.494]    BLOCKINGMODE: Null IPs for blocked domains
   [2019-03-02 09:07:08.494]    REGEX_DEBUGMODE: Inactive
   [2019-03-02 09:07:08.494] Finished config file parsing
   [2019-03-02 09:07:08.494] Compiled 3 Regex filters and 11 whitelisted domains in 0.2 msec (0 errors)
   [2019-03-02 09:07:08.497] Database successfully initialized
   [2019-03-02 09:07:08.498] Notice: Increasing queries struct size from 0 to 10000
   [2019-03-02 09:07:08.498] Notice: Increasing domains struct size from 0 to 1000
   [2019-03-02 09:07:08.498] Notice: Increasing clients struct size from 0 to 10
   [2019-03-02 09:07:08.498] Notice: Increasing overTime struct size from 0 to 100
   [2019-03-02 09:07:08.498] New forward server: 80.67.169.40 (0/0)
   [2019-03-02 09:07:08.498] Notice: Increasing forwarded struct size from 0 to 4
   [2019-03-02 09:07:08.498] New forward server: 192.168.8.254 (1/4)
   [2019-03-02 09:07:08.498] New forward server: 80.67.169.12 (2/4)
   [2019-03-02 09:07:08.504] Imported 1876 queries from the long-term database
   [2019-03-02 09:07:08.505]  -> Total DNS queries: 1876
   [2019-03-02 09:07:08.505]  -> Cached DNS queries: 210
   [2019-03-02 09:07:08.505]  -> Forwarded DNS queries: 1055
   [2019-03-02 09:07:08.505]  -> Exactly blocked DNS queries: 611

   -----tail of pihole-FTL.log------
   [2019-03-02 13:55:01.625]    AAAA_QUERY_ANALYSIS: Show AAAA queries
   [2019-03-02 13:55:01.625]    MAXDBDAYS: max age for stored queries is 365 days
   [2019-03-02 13:55:01.625]    RESOLVE_IPV6: Resolve IPv6 addresses
   [2019-03-02 13:55:01.625]    RESOLVE_IPV4: Resolve IPv4 addresses
   [2019-03-02 13:55:01.626]    DBINTERVAL: saving to DB file every minute
   [2019-03-02 13:55:01.626]    DBFILE: Using /etc/pihole/pihole-FTL.db
   [2019-03-02 13:55:01.626]    MAXLOGAGE: Importing up to 24.0 hours of log data
   [2019-03-02 13:55:01.626]    PRIVACYLEVEL: Set to 0
   [2019-03-02 13:55:01.626]    IGNORE_LOCALHOST: Show queries from localhost
   [2019-03-02 13:55:01.626]    BLOCKINGMODE: Null IPs for blocked domains
   [2019-03-02 13:55:01.626]    REGEX_DEBUGMODE: Inactive
   [2019-03-02 13:55:01.626] Finished config file parsing
   [2019-03-02 13:55:01.626] Compiled 3 Regex filters and 11 whitelisted domains in 0.2 msec (0 errors)
   [2019-03-02 13:55:01.628] Database successfully initialized
   [2019-03-02 13:55:01.629] Notice: Increasing queries struct size from 0 to 10000
   [2019-03-02 13:55:01.629] Notice: Increasing domains struct size from 0 to 1000
   [2019-03-02 13:55:01.629] Notice: Increasing clients struct size from 0 to 10
   [2019-03-02 13:55:01.629] Notice: Increasing overTime struct size from 0 to 100
   [2019-03-02 13:55:01.629] New forward server: 192.168.8.254 (0/0)
   [2019-03-02 13:55:01.629] Notice: Increasing forwarded struct size from 0 to 4
   [2019-03-02 13:55:01.629] New forward server: 80.67.169.40 (1/4)
   [2019-03-02 13:55:01.629] New forward server: 80.67.169.12 (2/4)
   [2019-03-02 13:55:01.631] New forward server: 1.0.0.1 (3/4)
   [2019-03-02 13:55:01.631] New forward server: 208.67.222.222 (4/4)
   [2019-03-02 13:55:01.631] Notice: Increasing forwarded struct size from 4 to 8
   [2019-03-02 13:55:01.631] Imported 1153 queries from the long-term database
   [2019-03-02 13:55:01.631]  -> Total DNS queries: 1153
   [2019-03-02 13:55:01.631]  -> Cached DNS queries: 109
   [2019-03-02 13:55:01.631]  -> Forwarded DNS queries: 842
   [2019-03-02 13:55:01.631]  -> Exactly blocked DNS queries: 202
   [2019-03-02 13:55:01.631]  -> Unknown DNS queries: 0
   [2019-03-02 13:55:01.631]  -> Unique domains: 217
   [2019-03-02 13:55:01.631]  -> Unique clients: 8
   [2019-03-02 13:55:01.631]  -> Known forward destinations: 5
   [2019-03-02 13:55:01.631] Successfully accessed setupVars.conf

*** [ DIAGNOSING ]: contents of /dev/shm

*** [ DIAGNOSING ]: Locale
    LANG=fr_FR.UTF-8

*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 pihole pihole 899640 mars   2 13:55 /var/log/pihole.log
   -----head of pihole.log------
   Mar  2 09:14:30 dnsmasq[7486]: demarré, version 2.76 (taille de cache 10000)
   Mar  2 09:14:30 dnsmasq[7486]: options à la compilation : IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify
   Mar  2 09:14:30 dnsmasq[7486]: attention : l'option « resolv-file » sera ignorée car « no-resolv » a été spécifié
   Mar  2 09:14:30 dnsmasq[7486]: using nameserver 192.168.8.254#53 for domaine 8.168.192.in-addr.arpa 
   Mar  2 09:14:30 dnsmasq[7486]: using nameserver 192.168.8.254#53 for domaine lcrprod.fr 
   Mar  2 09:14:30 dnsmasq[7486]: utilise le serveur de nom 1.0.0.1#53
   Mar  2 09:14:30 dnsmasq[7486]: utilise le serveur de nom 1.1.1.1#53
   Mar  2 09:14:30 dnsmasq[7486]: utilise le serveur de nom 149.112.112.11#53
   Mar  2 09:14:30 dnsmasq[7486]: utilise le serveur de nom 9.9.9.11#53
   Mar  2 09:14:30 dnsmasq[7486]: utilise le serveur de nom 149.112.112.10#53
   Mar  2 09:14:30 dnsmasq[7486]: utilise le serveur de nom 9.9.9.10#53
   Mar  2 09:14:30 dnsmasq[7486]: utilise le serveur de nom 149.112.112.112#53
   Mar  2 09:14:30 dnsmasq[7486]: utilise le serveur de nom 9.9.9.9#53
   Mar  2 09:14:30 dnsmasq[7486]: utilise le serveur de nom 208.67.222.222#53
   Mar  2 09:14:30 dnsmasq[7486]: mauvaise adresse dans /etc/hosts ligne 6
   Mar  2 09:14:30 dnsmasq[7486]: mauvaise adresse dans /etc/hosts ligne 7
   Mar  2 09:14:30 dnsmasq[7486]: mauvaise adresse dans /etc/hosts ligne 8
   Mar  2 09:14:30 dnsmasq[7486]: mauvaise adresse dans /etc/hosts ligne 9
   Mar  2 09:14:30 dnsmasq[7486]: mauvaise adresse dans /etc/hosts ligne 10
   Mar  2 09:14:30 dnsmasq[7486]: mauvaise adresse dans /etc/hosts ligne 11

`

You are running an older development version of FTL, which contains a version of dnsmasq prior to 2.80. The security fixes in 01-pihole.conf work with dnsmasq 2.80, which is contained in the current FTL.

Run the following to get all the versions on the same branch:

pihole checkout ftl master

Thank’s for this solution.

It’s work for me.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.