PiHole Stopped Allowing Custom .conf and .hosts Files

Hello,

I have a PiHole that has been functioning perfectly for months until recently. I cannot figure out why this is the case since it had been working well for so long and now I cannot get it to work again. Any help would be appreciated.

I am running a lancache and have used the scripts from this github to create a .conf file with corresponding .hosts files for each service I am caching. This was working wonderfully until a few days ago when I noticed the caching was not working.

The script generates a .conf file like so:

addn-hosts=/etc/dnsmasq.d/arenanet.hosts
addn-hosts=/etc/dnsmasq.d/blizzard.hosts
addn-hosts=/etc/dnsmasq.d/bsg.hosts

and the hosts files are formated like so:

192.168.1.101 dist.blizzard.com
192.168.1.101 dist.blizzard.com.edgesuite.net
192.168.1.101 llnw.blizzard.com

The .conf file and the hosts files were all placed in /etc/dnsmasq.d/ where the 01-pihole.conf file is located so my /etc/dnsmasq.d/ folder looked like this:

pi@Pi-Hole:/etc/dnsmasq.d $ ls
01-pihole.conf  blizzard.hosts  cityofheroes.hosts  epicgames.hosts  hirez.hosts    neverwinter.hosts  nintendo.hosts  renegadex.hosts  rockstar.hosts  square.hosts  teso.hosts    uplay.hosts     wargaming.net.hosts   xboxlive.hosts
arenanet.hosts  bsg.hosts       daybreak.hosts      frontier.hosts   lancache.conf  nexusmods.hosts    origin.hosts    riot.hosts       sony.hosts      steam.hosts   twitch.hosts  warframe.hosts  windowsupdates.hosts

After placing the files in /etc/dnsmasq.d/ and running sudo service pihole-FTL restart, DNS and FTL are not working. The output of journalctl -u pihole-FTL | tail -20 shows:

Sep 21 15:01:31 Pi-Hole systemd[1]: Stopping LSB: pihole-FTL daemon...
Sep 21 15:01:32 Pi-Hole pihole-FTL[18143]: .
Sep 21 15:01:32 Pi-Hole pihole-FTL[18143]: Stopped
Sep 21 15:01:32 Pi-Hole systemd[1]: pihole-FTL.service: Succeeded.
Sep 21 15:01:32 Pi-Hole systemd[1]: Stopped LSB: pihole-FTL daemon.
Sep 21 15:01:32 Pi-Hole systemd[1]: Starting LSB: pihole-FTL daemon...
Sep 21 15:01:32 Pi-Hole pihole-FTL[18151]: Not running
Sep 21 15:01:32 Pi-Hole su[18169]: (to pihole) root on none
Sep 21 15:01:32 Pi-Hole su[18169]: pam_unix(su:session): session opened for user pihole by (uid=0)
Sep 21 15:01:33 Pi-Hole pihole-FTL[18151]: **dnsmasq: bad option at line 1 of /etc/dnsmasq.d/blizzard.conf**
Sep 21 15:01:33 Pi-Hole su[18169]: pam_unix(su:session): session closed for user pihole
Sep 21 15:01:33 Pi-Hole systemd[1]: Started LSB: pihole-FTL daemon.

Expected Behaviour:

Using custom hosts files for DNS resolution

Actual Behaviour:

FTL won't start because of "bad option"

Let's take a look at the complete contents of your /etc/dnsmasq directory. Please post the output of the following command which will show all uncommented lines:

sudo grep -v '#\|^$' -R /etc/dnsmasq.*

Thnaks for the fast reply. Here's the output

pi@Pi-Hole:~ $ sudo grep -v '#\|^$' -R /etc/dnsmasq.*
/etc/dnsmasq.conf:conf-dir=/etc/dnsmasq.d
/etc/dnsmasq.conf.old:conf-dir=/etc/dnsmasq.d
/etc/dnsmasq.d/sony.hosts:192.168.1.101 gs2.ww.prod.dl.playstation.net
/etc/dnsmasq.d/sony.hosts:192.168.1.101 gs2.sonycoment.loris-e.llnwd.net
/etc/dnsmasq.d/xboxlive.hosts:192.168.1.101 assets1.xboxlive.com
/etc/dnsmasq.d/xboxlive.hosts:192.168.1.101 assets2.xboxlive.com
/etc/dnsmasq.d/xboxlive.hosts:192.168.1.101 dlassets.xboxlive.com
/etc/dnsmasq.d/xboxlive.hosts:192.168.1.101 xboxone.loris.llnwd.net
/etc/dnsmasq.d/xboxlive.hosts:192.168.1.101 xboxone.vo.llnwd.net
/etc/dnsmasq.d/xboxlive.hosts:192.168.1.101 xbox-mbr.xboxlive.com
/etc/dnsmasq.d/xboxlive.hosts:192.168.1.101 assets1.xboxlive.com.nsatc.net
/etc/dnsmasq.d/xboxlive.hosts:192.168.1.101 xvcf1.xboxlive.com
/etc/dnsmasq.d/square.hosts:192.168.1.101 patch-dl.ffxiv.com
/etc/dnsmasq.d/nexusmods.hosts:192.168.1.101 filedelivery.nexusmods.com
/etc/dnsmasq.d/arenanet.hosts:192.168.1.101 assetcdn.101.arenanetworks.com
/etc/dnsmasq.d/arenanet.hosts:192.168.1.101 assetcdn.102.arenanetworks.com
/etc/dnsmasq.d/arenanet.hosts:192.168.1.101 assetcdn.103.arenanetworks.com
/etc/dnsmasq.d/arenanet.hosts:192.168.1.101 live.patcher.bladeandsoul.com
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/arenanet.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/blizzard.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/bsg.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/cityofheroes.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/daybreak.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/epicgames.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/frontier.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/hirez.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/nexusmods.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/neverwinter.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/nintendo.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/origin.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/renegadex.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/riot.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/rockstar.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/sony.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/square.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/steam.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/uplay.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/teso.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/twitch.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/warframe.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/wargaming.net.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/windowsupdates.hosts
/etc/dnsmasq.d/lancache.conf:addn-hosts=/etc/dnsmasq.d/xboxlive.hosts
/etc/dnsmasq.d/blizzard.hosts:192.168.1.101 dist.blizzard.com
/etc/dnsmasq.d/blizzard.hosts:192.168.1.101 dist.blizzard.com.edgesuite.net
/etc/dnsmasq.d/blizzard.hosts:192.168.1.101 llnw.blizzard.com
/etc/dnsmasq.d/blizzard.hosts:192.168.1.101 edgecast.blizzard.com
/etc/dnsmasq.d/blizzard.hosts:192.168.1.101 blizzard.vo.llnwd.net
/etc/dnsmasq.d/blizzard.hosts:192.168.1.101 blzddist1-a.akamaihd.net
/etc/dnsmasq.d/blizzard.hosts:192.168.1.101 blzddist2-a.akamaihd.net
/etc/dnsmasq.d/blizzard.hosts:192.168.1.101 blzddist3-a.akamaihd.net
/etc/dnsmasq.d/blizzard.hosts:192.168.1.101 blzddist4-a.akamaihd.net
/etc/dnsmasq.d/blizzard.hosts:192.168.1.101 level3.blizzard.com
/etc/dnsmasq.d/blizzard.hosts:192.168.1.101 nydus.battle.net
/etc/dnsmasq.d/blizzard.hosts:192.168.1.101 edge.blizzard.top.comcast.net
/etc/dnsmasq.d/blizzard.hosts:192.168.1.101 cdn.blizzard.com
/etc/dnsmasq.d/origin.hosts:192.168.1.101 origin-a.akamaihd.net
/etc/dnsmasq.d/origin.hosts:192.168.1.101 lvlt.cdn.ea.com
/etc/dnsmasq.d/bsg.hosts:192.168.1.101 cdn-11.eft-store.com
/etc/dnsmasq.d/bsg.hosts:192.168.1.101 cl-453343cd.gcdn.co
/etc/dnsmasq.d/steam.hosts:192.168.1.101 lancache.steamcontent.com
/etc/dnsmasq.d/steam.hosts:192.168.1.101 content.steampowered.com
/etc/dnsmasq.d/steam.hosts:192.168.1.101 content1.steampowered.com
/etc/dnsmasq.d/steam.hosts:192.168.1.101 content2.steampowered.com
/etc/dnsmasq.d/steam.hosts:192.168.1.101 content3.steampowered.com
/etc/dnsmasq.d/steam.hosts:192.168.1.101 content4.steampowered.com
/etc/dnsmasq.d/steam.hosts:192.168.1.101 content5.steampowered.com
/etc/dnsmasq.d/steam.hosts:192.168.1.101 content6.steampowered.com
/etc/dnsmasq.d/steam.hosts:192.168.1.101 content7.steampowered.com
/etc/dnsmasq.d/steam.hosts:192.168.1.101 content8.steampowered.com
/etc/dnsmasq.d/steam.hosts:192.168.1.101 cs.steampowered.com
/etc/dnsmasq.d/steam.hosts:192.168.1.101 client-download.steampowered.com
/etc/dnsmasq.d/steam.hosts:192.168.1.101 hsar.steampowered.com.edgesuite.net
/etc/dnsmasq.d/steam.hosts:192.168.1.101 akamai.steamstatic.com
/etc/dnsmasq.d/steam.hosts:192.168.1.101 content-origin.steampowered.com
/etc/dnsmasq.d/steam.hosts:192.168.1.101 clientconfig.akamai.steamtransparent.com
/etc/dnsmasq.d/steam.hosts:192.168.1.101 steampipe.akamaized.net
/etc/dnsmasq.d/steam.hosts:192.168.1.101 edgecast.steamstatic.com
/etc/dnsmasq.d/steam.hosts:192.168.1.101 steam.apac.qtlglb.com.mwcloudcdn.com
/etc/dnsmasq.d/steam.hosts:192.168.1.101 cm.steampowered.com
/etc/dnsmasq.d/steam.hosts:192.168.1.101 cdn1-sea1.valve.net
/etc/dnsmasq.d/steam.hosts:192.168.1.101 cdn2-sea1.valve.net
/etc/dnsmasq.d/steam.hosts:192.168.1.101 steam-content-dnld-1.apac-1-cdn.cqloud.com
/etc/dnsmasq.d/steam.hosts:192.168.1.101 steam-content-dnld-1.eu-c1-cdn.cqloud.com
/etc/dnsmasq.d/steam.hosts:192.168.1.101 edge.steam-dns.top.comcast.net
/etc/dnsmasq.d/steam.hosts:192.168.1.101 edge.steam-dns-2.top.comcast.net
/etc/dnsmasq.d/steam.hosts:192.168.1.101 steam.naeu.qtlglb.com
/etc/dnsmasq.d/steam.hosts:192.168.1.101 steampipe-kr.akamaized.net
/etc/dnsmasq.d/steam.hosts:192.168.1.101 steam.ix.asn.au
/etc/dnsmasq.d/steam.hosts:192.168.1.101 steam.eca.qtlglb.com
/etc/dnsmasq.d/steam.hosts:192.168.1.101 steam.cdn.on.net
/etc/dnsmasq.d/steam.hosts:192.168.1.101 update5.dota2.wmsj.cn
/etc/dnsmasq.d/steam.hosts:192.168.1.101 update2.dota2.wmsj.cn
/etc/dnsmasq.d/steam.hosts:192.168.1.101 update6.dota2.wmsj.cn
/etc/dnsmasq.d/steam.hosts:192.168.1.101 update3.dota2.wmsj.cn
/etc/dnsmasq.d/steam.hosts:192.168.1.101 update1.dota2.wmsj.cn
/etc/dnsmasq.d/steam.hosts:192.168.1.101 update4.dota2.wmsj.cn
/etc/dnsmasq.d/steam.hosts:192.168.1.101 update5.csgo.wmsj.cn
/etc/dnsmasq.d/steam.hosts:192.168.1.101 update2.csgo.wmsj.cn
/etc/dnsmasq.d/steam.hosts:192.168.1.101 update4.csgo.wmsj.cn
/etc/dnsmasq.d/steam.hosts:192.168.1.101 update3.csgo.wmsj.cn
/etc/dnsmasq.d/steam.hosts:192.168.1.101 update6.csgo.wmsj.cn
/etc/dnsmasq.d/steam.hosts:192.168.1.101 update1.csgo.wmsj.cn
/etc/dnsmasq.d/steam.hosts:192.168.1.101 st.dl.bscstorage.net
/etc/dnsmasq.d/steam.hosts:192.168.1.101 cdn.mileweb.cs.steampowered.com.8686c.com
/etc/dnsmasq.d/daybreak.hosts:192.168.1.101 pls.patch.daybreakgames.com
/etc/dnsmasq.d/teso.hosts:192.168.1.101 live.patcher.elderscrollsonline.com
/etc/dnsmasq.d/twitch.hosts:192.168.1.101 d3rmjivj4k4f0t.cloudfront.net
/etc/dnsmasq.d/twitch.hosts:192.168.1.101 addons.forgesvc.net
/etc/dnsmasq.d/twitch.hosts:192.168.1.101 media.forgecdn.net
/etc/dnsmasq.d/twitch.hosts:192.168.1.101 files.forgecdn.net
/etc/dnsmasq.d/renegadex.hosts:192.168.1.101 rxp-lv.cncirc.net
/etc/dnsmasq.d/renegadex.hosts:192.168.1.101 cronub.fairplayinc.uk
/etc/dnsmasq.d/renegadex.hosts:192.168.1.101 amirror.tyrant.gg
/etc/dnsmasq.d/renegadex.hosts:192.168.1.101 mirror.usa.tyrant.gg
/etc/dnsmasq.d/renegadex.hosts:192.168.1.101 renx.b-cdn.net
/etc/dnsmasq.d/wargaming.net.hosts:192.168.1.101 dl1.wargaming.net
/etc/dnsmasq.d/wargaming.net.hosts:192.168.1.101 dl2.wargaming.net
/etc/dnsmasq.d/wargaming.net.hosts:192.168.1.101 wg.gcdn.co
/etc/dnsmasq.d/wargaming.net.hosts:192.168.1.101 wgusst-na.wargaming.net
/etc/dnsmasq.d/wargaming.net.hosts:192.168.1.101 wgusst-eu.wargaming.net
/etc/dnsmasq.d/wargaming.net.hosts:192.168.1.101 update-v4r4h10x.worldofwarships.com
/etc/dnsmasq.d/wargaming.net.hosts:192.168.1.101 wgus-wotasia.wargaming.net
/etc/dnsmasq.d/wargaming.net.hosts:192.168.1.101 dl-wot-ak.wargaming.net
/etc/dnsmasq.d/wargaming.net.hosts:192.168.1.101 dl-wot-gc.wargaming.net
/etc/dnsmasq.d/wargaming.net.hosts:192.168.1.101 dl-wot-se.wargaming.net
/etc/dnsmasq.d/wargaming.net.hosts:192.168.1.101 dl-wot-cdx.wargaming.net
/etc/dnsmasq.d/wargaming.net.hosts:192.168.1.101 dl-wows-ak.wargaming.net
/etc/dnsmasq.d/wargaming.net.hosts:192.168.1.101 dl-wows-gc.wargaming.net
/etc/dnsmasq.d/wargaming.net.hosts:192.168.1.101 dl-wows-se.wargaming.net
/etc/dnsmasq.d/wargaming.net.hosts:192.168.1.101 dl-wows-cdx.wargaming.net
/etc/dnsmasq.d/wargaming.net.hosts:192.168.1.101 dl-wowp-ak.wargaming.net
/etc/dnsmasq.d/wargaming.net.hosts:192.168.1.101 dl-wowp-gc.wargaming.net
/etc/dnsmasq.d/wargaming.net.hosts:192.168.1.101 dl-wowp-se.wargaming.net
/etc/dnsmasq.d/wargaming.net.hosts:192.168.1.101 dl-wowp-cdx.wargaming.net
/etc/dnsmasq.d/warframe.hosts:192.168.1.101 content.warframe.com
/etc/dnsmasq.d/rockstar.hosts:192.168.1.101 patches.rockstargames.com
/etc/dnsmasq.d/hirez.hosts:192.168.1.101 hirez.http.internapcdn.net
/etc/dnsmasq.d/frontier.hosts:192.168.1.101 cdn.zaonce.net
/etc/dnsmasq.d/01-pihole.conf:addn-hosts=/etc/pihole/local.list
/etc/dnsmasq.d/01-pihole.conf:addn-hosts=/etc/pihole/custom.list
/etc/dnsmasq.d/01-pihole.conf:localise-queries
/etc/dnsmasq.d/01-pihole.conf:no-resolv
/etc/dnsmasq.d/01-pihole.conf:cache-size=10000
/etc/dnsmasq.d/01-pihole.conf:log-queries
/etc/dnsmasq.d/01-pihole.conf:log-facility=/var/log/pihole.log
/etc/dnsmasq.d/01-pihole.conf:local-ttl=2
/etc/dnsmasq.d/01-pihole.conf:log-async
/etc/dnsmasq.d/01-pihole.conf:server=8.8.8.8
/etc/dnsmasq.d/01-pihole.conf:server=8.8.4.4
/etc/dnsmasq.d/01-pihole.conf:server=208.67.222.222
/etc/dnsmasq.d/01-pihole.conf:server=208.67.220.220
/etc/dnsmasq.d/01-pihole.conf:domain-needed
/etc/dnsmasq.d/01-pihole.conf:bogus-priv
/etc/dnsmasq.d/01-pihole.conf:interface=eth0
/etc/dnsmasq.d/01-pihole.conf:server=/use-application-dns.net/
/etc/dnsmasq.d/nintendo.hosts:192.168.1.101 ccs.cdn.wup.shop.nintendo.com
/etc/dnsmasq.d/nintendo.hosts:192.168.1.101 ccs.cdn.wup.shop.nintendo.net
/etc/dnsmasq.d/nintendo.hosts:192.168.1.101 ccs.cdn.wup.shop.nintendo.net.edgesuite.net
/etc/dnsmasq.d/nintendo.hosts:192.168.1.101 geisha-wup.cdn.nintendo.net
/etc/dnsmasq.d/nintendo.hosts:192.168.1.101 geisha-wup.cdn.nintendo.net.edgekey.net
/etc/dnsmasq.d/nintendo.hosts:192.168.1.101 idbe-wup.cdn.nintendo.net
/etc/dnsmasq.d/nintendo.hosts:192.168.1.101 idbe-wup.cdn.nintendo.net.edgekey.net
/etc/dnsmasq.d/nintendo.hosts:192.168.1.101 ecs-lp1.hac.shop.nintendo.net
/etc/dnsmasq.d/nintendo.hosts:192.168.1.101 receive-lp1.dg.srv.nintendo.net
/etc/dnsmasq.d/nintendo.hosts:192.168.1.101 wup.eshop.nintendo.net
/etc/dnsmasq.d/nintendo.hosts:192.168.1.101 hac.lp1.d4c.nintendo.net
/etc/dnsmasq.d/nintendo.hosts:192.168.1.101 hac.lp1.eshop.nintendo.net
/etc/dnsmasq.d/riot.hosts:192.168.1.101 l3cdn.riotgames.com
/etc/dnsmasq.d/riot.hosts:192.168.1.101 worldwide.l3cdn.riotgames.com
/etc/dnsmasq.d/riot.hosts:192.168.1.101 riotgamespatcher-a.akamaihd.net
/etc/dnsmasq.d/riot.hosts:192.168.1.101 riotgamespatcher-a.akamaihd.net.edgesuite.net
/etc/dnsmasq.d/riot.hosts:192.168.1.101 dyn.riotcdn.net
/etc/dnsmasq.d/epicgames.hosts:192.168.1.101 cdn1.epicgames.com
/etc/dnsmasq.d/epicgames.hosts:192.168.1.101 cdn.unrealengine.com
/etc/dnsmasq.d/epicgames.hosts:192.168.1.101 cdn1.unrealengine.com
/etc/dnsmasq.d/epicgames.hosts:192.168.1.101 cdn2.unrealengine.com
/etc/dnsmasq.d/epicgames.hosts:192.168.1.101 cdn3.unrealengine.com
/etc/dnsmasq.d/epicgames.hosts:192.168.1.101 download.epicgames.com
/etc/dnsmasq.d/epicgames.hosts:192.168.1.101 download2.epicgames.com
/etc/dnsmasq.d/epicgames.hosts:192.168.1.101 download3.epicgames.com
/etc/dnsmasq.d/epicgames.hosts:192.168.1.101 download4.epicgames.com
/etc/dnsmasq.d/epicgames.hosts:192.168.1.101 epicgames-download1.akamaized.net
/etc/dnsmasq.d/neverwinter.hosts:192.168.1.101 level3.nwhttppatch.crypticstudios.com
/etc/dnsmasq.d/uplay.hosts:192.168.1.101 cdn.ubi.com
/etc/dnsmasq.d/windowsupdates.hosts:192.168.1.101 windowsupdate.com
/etc/dnsmasq.d/windowsupdates.hosts:192.168.1.101 dl.delivery.mp.microsoft.com
/etc/dnsmasq.d/windowsupdates.hosts:192.168.1.101 update.microsoft.com
/etc/dnsmasq.d/windowsupdates.hosts:192.168.1.101 do.dsp.mp.microsoft.com
/etc/dnsmasq.d/windowsupdates.hosts:192.168.1.101 microsoft.com.edgesuite.net
/etc/dnsmasq.d/windowsupdates.hosts:192.168.1.101 amupdatedl.microsoft.com
/etc/dnsmasq.d/windowsupdates.hosts:192.168.1.101 amupdatedl2.microsoft.com
/etc/dnsmasq.d/windowsupdates.hosts:192.168.1.101 amupdatedl3.microsoft.com
/etc/dnsmasq.d/windowsupdates.hosts:192.168.1.101 amupdatedl4.microsoft.com
/etc/dnsmasq.d/windowsupdates.hosts:192.168.1.101 amupdatedl5.microsoft.com
/etc/dnsmasq.d/cityofheroes.hosts:192.168.1.101 cdn.homecomingservers.com
/etc/dnsmasq.d/cityofheroes.hosts:192.168.1.101 nsa.tools

Output of the following:

cat /etc/dnsmasq.d/blizzard.hosts

pihole-FTL dnsmasq-test

The first file alphabetically is arenanet so I'll post that one.

pi@Pi-Hole:~ $ pi@Pi-Hole:~ $ cat /etc/dnsmasq.d/arenanet.hosts
192.168.1.101 assetcdn.101.arenanetworks.com
192.168.1.101 assetcdn.102.arenanetworks.com
192.168.1.101 assetcdn.103.arenanetworks.com
192.168.1.101 live.patcher.bladeandsoul.com
pi@Pi-Hole:~ $ pihole-FTL dnsmasq-test

dnsmasq: bad option at line 1 of /etc/dnsmasq.d/arenanet.hosts

You are using an automated system to generate these dnsmasq configurations. Contact the author of the script you are using for a resolution to the problem their script is causing.

Nothing in Pi-hole has changed recently that would not allow configuration files in the /etc/dnsmasq.d directory. It is the contents of the files that are causing the problem.

Hosts files don't go in /etc/dnsmasd.d/

dnsmasq|pihole-FTL have no idea what 192.168.1.101 means as a command.

1 Like

The entries in the configuration files need to follow the requirements of dnsmasq.

http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html

There is a way to specify additional hosts files, or to map IP's to names, but not the way you are doing it.

It can never have worked this way. The only thing I can see is you created the hosts files after starting FTL for the last time. It will always fail when there are HOSTS files in this directory.

The others are right, simply put the hosts files somewhere else (where they will not be tried to be interpreted as conf files) and you are set.

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