Gargoyle Forum

Early days, but may have cracked it

/etc/dnsmasq.conf
dhcp-option=6,ipaddress1 (address of the pi)

Seems to be working... YAYYY Ill give it a day or two, but ill stop pulling hair for now.

MANY thanks

Sounds good

My pi is now racking up thousands of blacklisted stuff that wasn't there before

I'd like to revert to stock on my tplink 3600... just to troubleshoot the pi
How would I do this please ?

That massive scrolling list of dns requests thing happened to me when I first installed the pihole. Turned out that the problem wasn't that they are blacklisted, rather that some of them were getting caught up in a loop. The answer for me was to uncheck:

connection>basic>network/local lan>FORCE CLIENTS TO USE ROUTER DNS SERVICES

See this post for more details:

https://discourse.pi-hole.net/t/loop-be ... outer/1105

Hope it helps.

Ahh! Good point. I forgot we discussed that loop issue previously

That option never was checked ! but I came to the conclusion that it was overzealous blacklisting of all the Amazon junk was causing the girlfriends fire tablet to constantly "phone home"

Eventually I gave in and completely rebuilt the pi... seems to have sorted it. (famous last words etc)

I had to rebuild my pihole for other reasons but after the rebuild everything worked smoothly. When they updated to the recent version things worked even better.

I still can't quite get the pihole, the router and a wired access point to share hostnames. This takes a level of configuration know-how that I'm, shall we say, working up to.

Glad you got it sorted. The PI is well worth the effort.

It was adding the pi address to dnsmasq. conf that did it for me, as long as all your other kit is on the same network range (and subnet) it should all propagate.

A suggestion I happened across was to disable dchp on the router, and let the pi do it... that should work too (logically) but never tried it... but remember, only have one dchp server !