Pi-hole v4.2 Available With Shared Memory, New Blocking Modes, And More
We’re always happy when we can release a new version of Pi-hole, so today we’re announcing v4.2 of Pi-hole. Thank you to to our patrons and everyone else who continue to support us. Along with many other things, we’ve merged in the upstream code from
dnsmasq v2.80. For anyone who doesn’t know, FTLDNS (
pihole-FTL) is just our fork of
We have released a small hotfix which addresses possible crashes experienced for users without
libcap capabilities (running FTLDNS under
root). For most users, this update will not change anything.
New Blocking Mode
We’ve added a new blocking mode (
NODATA), where blocked requested are replied with a status code of
AAAA records are empty. It’s unclear if there are advantages to this mode over others, but you’re welcome to experiment with it.
In preparation of the new API we are working on, FTLDNS will now store its data in a shared-memory space, so that the API can come in and read from that memory to fulfill requests. In short, this means FTLDNS will be even lighter as it doesn’t have to care about sending the statistics to some requester. Instead, it will concentrate on generating the statistics and the API can read FTL’s data directly, resulting in reduced delays in the API.
wpad Vulnerability Fix
We previously mentioned how you could work around a vulnerability regarding
wpad entries. This fix is now in place as suggested by
Fixes And Tweaks
- We updated SQLite to 3.26.0
- We fixed the query status if a forwarded query was partially replied to from the cache
- We now prevent multiple static DHCP entries with same IP
- And more…
Docker Version Also Updated
We heard your feedback and we made sure to coordinate better to release our traditional install and our Docker install together. The docker image will be released when testing is complete.
[…] Hole 4.2 […]
I have this problem with the last update
[✓] Checking for php5-cgi
[✓] Checking for php5-sqlite
[✓] Enabling lighttpd service to start on reboot…
[i] FTL Checks…
[✓] Detected ARM-hf architecture (armv7+)
[i] Checking for existing FTL binary…
curl: (6) Could not resolve host: ftl.pi-hole.net
[i] Checksums do not match, downloading from ftl.pi-hole.net.
[✗] Downloading and Installing FTL
Error: Unable to get latest release location from GitHub
[✗] FTL Engine not installed
I’m seeing that an update is available on the Pi Hole TFTPi display that still shows up after I have run a pihole -up, and rebooted. I thought the last time I did that that the update flag disappeared. When I run pihole -up the command it says I am updated. Keli
Comments are closed.