1
 
 

Highlights Security fixes

Two security vulnerabilities in the web interface have been patched in this release.

https://github.com/pi-hole/web/security/advisories/GHSA-6xp4-jw73-f4qp: fixed with d328f14
https://github.com/pi-hole/web/security/advisories/GHSA-8rw8-vjgp-rwj6: fixed with 1a0c6f4

Performance improvements

Faster startup (FTL #2725)

FTL now imports historical queries from the database asynchronously on startup. Previously, DNS resolution was blocked until the entire query history had been loaded into memory. Now, FTL begins accepting DNS queries immediately and imports history in a dedicated background thread. The garbage collector is held off until the import is complete to ensure data consistency.

Low-memory hardware optimizations (FTL #2757)

A new database.forceDisk configuration option forces FTL’s in-memory SQLite3 database to live on disk instead of in RAM. This can notably reduce FTL’s memory footprint, which is beneficial on resource-constrained hardware such as older Raspberry Pi models. On NVMe-backed systems no measurable performance difference was observed, though some slowdown may be seen on slower storage.

Faster gravity updates (FTL #2710)

Several cumulative efficiency gains have been applied to the main domain validation loop that runs during pihole -g. While each individual improvement is modest, they add up across every entry in your blocklists and allowlists:

A lookup table now validates domain characters using a single comparison per character, replacing multiple branching comparisons
IP address testing is short-circuited: IPv4 tests only run if the token starts with a digit, and IPv6 tests only run if a colon is present within the first 5 characters
The unicode BOM check is now performed once per file rather than once per line

In testing with ~5 million domains across several lists, gravity update time dropped from ~27s to ~23s (roughly a 16% reduction in real time, and ~22% reduction in CPU time).

2
 
 

Firefox MV3 extension for Pi-hole v6's REST API.

Features:

  • Real-time stats in toolbar
  • Toggle blocking with timer
  • Track domains per tab (first/third-party)
  • Add to allow/denylist Query log
Settings Domain Sidebar >
Settings Domain Sidebar

Requires Firefox 142+ and Pi-hole v6.

Looking for feedback and feature requests!

3
4
 
 

Lately my home internet service has been experiencing brief periods of failure and I'm trying to understand what the root problem is and if there's anything I can do to fix it.

I have two piholes running on my home network providing DNS service and blocking. Lately I've been encountering brief internet outages, approximately once a day for the last week. Work laptop disconnects from VPN saying no internet and other devices show no internet either. Cable modem doesn't show it's lost connection though, and logging into my router it shows it has internet connectivity. Trying to ping a website shows the dns resolution isn't working. I can ping by IP address but not name. The outage usually resolves itself in approx 5 minutes, sometimes a little longer.

My piholes are setup to use Google, Cloudflare and Open DNS for dns service so I'm puzzled how my dns resolution suddenly starts failing. In theory if one's down, it'll use the others right? So how am I experiencing a dns outage? Is this a problem with something outside my network or something internal, or is there anything else I should do to diagnose and fix it?

5
 
 

I'm trying to figure out how to set up Pi-hole for the first time and I think I'm doing something wrong, or missing some important step(s).

I figured that using Docker would be the easiest way to get it running so I started with the sample yaml I found on the pi-hole/docker-pi-hole github page. Then I went to my router's DHCP settings and set the primary DNS to the host's IP (I'm not sure if that's the correct one to use though*).

screenshotMy router's DHCP settings

Eventually I was able to confirm that a site I blocked was blocked when visiting it from the host PC, but my phone and other devices on my network could still visit the site.

Then I tried copying the same IP to the secondary DNS, but then I could no longer access the internet on other devices.

I also tried disabling the router's DHCP server to use Pi-hole instead. I used the same default gateway IP I found in the router's settings, but I lost internet on the other devices with that as well.

I know very little about configuring network stuff so I'm not sure what I might've done wrong.

*I also tried using the IP address I found in the Pi-hole's system information section as the primary DNS, but then the site I blacklisted was no longer getting blocked on the host machine.

6
 
 

Hi everyone!
I am a newish user. Installed pihole on my Pi 3B almost 3 months ago and since then I have had issues when playing games - notably CS2.
When I route my traffic thru Pihole I experience a significant increase in latency and jitter. It varies from noticable to insufferable. DHCP is turned on only on the router. Pi handles just then DNS and filtering.
If I disable Pihole and change the DNS to 1.1.1.1, there is almost no jitter and the latency is fine.
I've scowered the internet for answers, but most people blame having DHCP on both router and Pi, which I don't have enabled. Any ideas what I could check or change? Some even suggested enabling IPv6 support, but that didn't do anything.
The Pi is updated to the lates Pihole version as of today. It is enclosed in a plastic case and cooling, so temps aren't an issue.
On my PC I am running Fedora 42 with CachyOS kernel.
Thanks!

7
 
 

I have a pihole server on my network. It used to block the ads on my roku's homescreen and only empty placeholders would show up.

I bought a new Roku player and it doesn't seem to have any of the ads on the homescreen blocked by the pihole. Configuring the "secret menus" doesn't really do anything, as far as I can tell.

Does anyone have any updated methods for blocking ads on the Roku homescreen?

8