Pi-hole only briefly works after reboot

[Sheriff-Blanaba]

Expected Behaviour:

[Blocking majority of ads]

Actual Behaviour:

[Blocks some ads after reboot]

Debug Token:

[ui57aw9rf9]
Pi-hole set up as DHCP aswell as DSN override enabled in router, pointing towards Pi. Query list does not update.

[jacob.salmela]

According to your log, things seem to be working. I see your on Jessie with v2.76 of dnsmasq. Did you follow this?

Install a more recent dnsmasq on Raspbian Jessie

Update: 2018-08-06 As of v4.0, Pi-hole ships with _FTL_DNS, our fork of dnsmasq, which should restore compatibility with Raspbian Jessie. We still recommend installing a newer OS as Jessie is EOL anyway. Please note that this tutorial is only meant for Rasbian Jessie, although it might (to some extend) also help with similar issues on other Debian versions. Do this at your own risk (however, the likeliness of a failure is rather small in our opinion). First step: Download more recent versio…

See also:

Help Us Beta Test FTLDNS

Originally published at: https://pi-hole.net/2018/03/24/help-us-beta-test-ftldns/ In case you missed it, FTLDNS™ is Pi-hole's Faster Than Light (FTL) daemon combined with a DNS/DHCP server (our fork of dnsmasq). So instead of installing dnsmasq as a dependency, we will be distributing all services in a single binary. This will allow us to hook into dnsmasq's functionality at a code- level, as well as ensuring that you are using the latest stable version of the resolver and receive, e.g., i…

[Sheriff-Blanaba]

I've gone ahead and updated to FTL, at this point it seems as if my devices are ignoring the DNS at will, even tho the pi is acting as the DHCP. I've attempted to have my devices directly select the dns as per the pi's IP but that has come to no avail aswell.
New debug token: xpqmn843gm

[jacob.salmela]

So manually setting a device to use Pi-hole for DNS doesn't work? Is that what I understand?