Please follow the below template, it will help us to help you!
/etc/dnsmasq.d/01-pihole.conf should result in an NXDOMAIN response when the upstream DNS resolver (in this case, Norton ConnectSafe ) supplies
126.96.36.199 as the response for a non-existent domain.
I did restart the
pihole-FTL service after editing the cofiguration file. I’m also aware that any reinstall/upgrade to pihole will overwrite these changes. For now, it’s just a test.
FTLDNS compiled without the 10000 cache-size limit that was hardcoded into dnsmasq?
/etc/dnsmasq.d/01-pihole.conf since I have a block list of over 2 million domains and experienced this:
grep 'cachesize' /var/log/pihole.log gives
May 11 21:13:26 dnsmasq: started, version pi-hole-2.79 cachesize 500000 which if I’m not mistaken seems to confirm that the cache size was indeed increased?
On querying a non-existent domain, FTLDNS provides 188.8.131.52 as the response instead of an NXDOMAIN response although
bogus-nxdomain=184.108.40.206 was set in
I would have included the debug token, but running the debug through the web interface just hangs. The
pihole -d script hangs on
*** [ DIAGNOSING ]: Dashboard and block page
*** [ DIAGNOSING ]: FTL version
[✓] FTL: vDev-b133b65 (How do I update Pi-hole?)
*** [ DIAGNOSING ]: dnsmasq version
*** [ DIAGNOSING ]: lighttpd version
*** [ DIAGNOSING ]: php version
*** [ DIAGNOSING ]: Operating system
[✓] Raspbian GNU/Linux 9 (stretch)
*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected
*** [ DIAGNOSING ]: Processor