Setting up Pi-hole

Heads up if you use Pi-hole with DNS-over-HTTPS via cloudflared.

Cloudflare have removed the old cloudflared proxy-dns feature from newer versions of cloudflared. If your Pi-hole is configured to forward DNS to 127.0.0.1#5053, and cloudflared updates to a new version, DNS can partially break.

The awkward bit is that Pi-hole may still look healthy. The dashboard can still show queries, blocked domains, active clients, and normal-looking graphs, because Pi-hole is still receiving requests and can still block domains locally. But normal allowed lookups may fail or time out because Pi-hole is forwarding them to cloudflared on port 5053, and cloudflared is no longer running that service.

Quick checks:

On the Pi-hole, run:

grep -n "^PIHOLE_DNS" /etc/pihole/setupVars.conf

If you see:

127.0.0.1#5053

then check whether anything is listening there:

sudo ss -lntup | grep ':5053'

If nothing is listening, DNS-over-HTTPS is broken and Pi-hole’s upstream resolver is dead.

Also check:

systemctl status cloudflared --no-pager

If the log says DNS Proxy is no longer supported since version 2026.2.0, that’s the problem.

The simplest fix is to stop using cloudflared for Pi-hole DNS and set Pi-hole back to normal upstream DNS servers such as Google, Quad9, Cloudflare, OpenDNS, etc. In the Pi-hole web interface, go to Settings → DNS, remove 127.0.0.1#5053, choose normal upstream DNS servers, save, then disable cloudflared:

sudo systemctl disable --now cloudflared

Then test:

dig @PIHOLE_IP google.com

If that returns an answer instead of timing out, it’s fixed.


Thanks to chatgpt for helping me find this (and writing that summary above).
I run pihole on a docker container, how do i do the above?
 
I run pihole on a docker container, how do i do the above?
I thought you had an RB5009. ie containers, Technitium is in the menu. Not sure if it is built with QUIC but you can pull the latest that includes it anyway.
h3://dns.adguard-dns.com/dns-query (94.140.14.14)
h3://dns.adguard-dns.com/dns-query (94.140.15.15)
h3://cloudflare-dns.com/dns-query (1.1.1.1)
h3://cloudflare-dns.com/dns-query (1.0.0.1)
I have Technitium on RPI 4 which works well with h3 and Quic 853. I still prefer to hide it in with 443 h3 traffic though not all providers support it. If you do go Technitium on an RPi4 minimum you will need the Libraries As already said cloudflared is not supported anymore!
 
Last edited:
I've had PiHole running for about 6 months now. It is just the basic install running on Raspian OS and I'm curious if there are any other things I can do with the Raspberry Pi at the same time as running Pi Hole? I haven't been through the thread as it is quite long :D.
 
I've had PiHole running for about 6 months now. It is just the basic install running on Raspian OS and I'm curious if there are any other things I can do with the Raspberry Pi at the same time as running Pi Hole? I haven't been through the thread as it is quite long :D.
The better question is what can't you do with an RPi. They can do just about anything you can imagine, besides compute intensive tasks like transcoding and AI.

Do some Googling and see if anything tickles your fancy. There is another RPi thread on here somewhere along the lines of what are you doing with your Pi. That would also be a useful resource.
 
The better question is what can't you do with an RPi. They can do just about anything you can imagine, besides compute intensive tasks like transcoding and AI.

Do some Googling and see if anything tickles your fancy. There is another RPi thread on here somewhere along the lines of what are you doing with your Pi. That would also be a useful resource.
Thank you. I'll have a hunt around.
 
I use adguard and ublock origin browser extension and I haven't seen a Youtube ad for years.
That's because uBO uses scriptlets and cosmetic filtering on the page itself. It's impossible to block same-domain ads without also blocking the desired content also hosted on that domain (i.e. videos!). DNS blocking is for third party trackers, analytics, beacons, and those first-party ads that are identifiable (eg by subdomain). A browser extension is for the rest, and they're complementary. uBO in at least Medium Mode with good network blocking rules is a real time, memory and bandwidth saver. Set up properly, you'll save a lot of requests even leaving the browser (and thus prevent them hitting the DNS server at all), which is faster than waiting for a null response from upstream.
 
Last edited:
Back
Top Bottom