mirror of
https://github.com/pi-hole/FTL.git
synced 2026-07-03 03:25:39 +01:00
DL6ER
20164bff26
The API query-count assertions depend on resolving mask.icloud.com, whose mask.icloud.com -> mask.apple-dns.net CNAME chain was recursed to the public internet. dnsmasq fires extra DNSKEY validation queries depending on whether Apple currently DNSSEC-signs icloud.com / apple-dns.net, and Apple toggles this over time. The runtime DS-probing workaround in conftest.py could not reliably model dnsmasq's behaviour (e.g. when Apple returns SERVFAIL on DS), so the suite went flaky again. Serve the icloud.com and apple-dns.net zones from the local authoritative PowerDNS server instead, so the chain resolves hermetically and the query counts are deterministic regardless of Apple's upstream DNSSEC posture. The DS-probing fixture is dropped and the expected counters become fixed constants again. Signed-off-by: DL6ER <dl6er@dl6er.de>
Network-wide ad blocking via your own Linux hardware
FTLDNS (pihole-FTL) provides an interactive API and also generates statistics for Pi-hole®'s Web interface.
- Fast: stats are read directly from memory by coupling our codebase closely with
dnsmasq - Versatile: upstream changes to
dnsmasqcan quickly be merged in without much conflict - Lightweight: runs smoothly with minimal hardware and software requirements such as Raspberry Pi Zero
- Interactive: our API can be used to interface with your projects
- Insightful: stats normally reserved inside of
dnsmasqare made available so you can see what's really happening on your network
Official documentation
The official FTLDNS documentation can be found here.
Installation
FTLDNS (pihole-FTL) is automatically installed when installing Pi-hole.
IMPORTANT
FTLDNS will disable any existing installations of
dnsmasq. This is because FTLDNS isdnsmasq+ Pi-hole's code, so both cannot run simultaneously.