Pi-hole

This has been doing my head in for the longest and it's time to finally solve it.

RandomText.api.met.no provides the weather for my Home Assistant, however Pi-Hole says it's bogus and is being refused Upstream, which is Unbound. I would really like to fix it. Even if I can whitelist it and just ignore the problem I'd be happy. Any suggestions?

Please talk to me like I'm an idiot, because I don't have the foggiest with this.

I did install unbound-anchor but that didn't fix anything.

I'm not sure this is even a Pi-Hole problem, but since it's most apparent there I hoped someone here can point me in a direction to solve the problem.

Every hour from 10 too till about 15 minutes past Pi-Hole has a lot of N/A replies for DNS lookups. At that moment internet slows down, pages load for 10 or 15 seconds or sometimes not at all. When running dig on the host of Pi-Hole it shows that it can't connect to my router. Pi-Hole is hosted as a container on a Intel NUC with Proxmox. The router is a unifi security gateway. As DNS resolvers I use Quad9 and dns0.eu. Pinging IP addresses keep working during this period. Resolving/visiting local domainnames (like pihole or my NAS) keep working.

Where can I start to look for a solution? It almost feels like a cronjob of some sorts, but there is not a lot of traffic going through the network at these times. Also the proxmox host does nothing at that moment.

Just a PSA: for anyone using a MikroTik router, using it for their DHCP server and are having issues with their devices not using Pi-hole.

If you have set the IP of your Pi-hole as the DNS server and are seeing entries in "dynamic servers" then the router is using your ISP's DNS server causing it to bypass your Pi-Hole.

You need to go to the interface that is supplying your internet connection (PPPoE client, DHCP) and turn off the option "use peer dns".

This will disable dynamic servers and route everything to your Pi-hole.

A new update for Pi-Hole is available.

I've noticed that all my Home Assistant integrations that talk to the Internet are getting SERVFAIL from Pi-Hole. For whatever reason, Unbound just hates them, so I'm constantly seeing api.met.no SERVFAIL in the logs. Does anyone know how to fix this?

I have the Pi-Hole acting as the DHCP server and DNS server too and this works fine for 23 hours and then it flops and I don't understand why.

Basically after 24 hours, all devices just disconnect from the router and when I try and reconnect them, they say they're unable to get an IP address.

But before they drop connection, they all report the DNS server as the Pi-Hole.

If I change my DHCP to static and connect to my router, I see that the Pi-Hole is still connected with its static IP just fine.

If I factory reset the router and then add the same SSID and password, the Pi-Hole automatically reconnects and then all devices can reconnect again, so I'm unsure what the issue is.

Can someone break this down. I feel stupid for not understanding what's happening here.

DNS Resolver

cross-posted from: https://lazysoci.al/post/13315467

> I have a Raspberry Pi 02W running Pi-Hole and ordinarily things work perfectly, but I've got something in my house tripping my fuse box which I'm unable to locate. The tripper, not the fuse box. Anyway, what it means is occasionally, I lose power and so my router and my Pi-Hole go down. > > I've configured my /etc/dhcpcd.conf so that my RPi02W can have a static IP > > interface wlan0 > static ip_address=192.168.1.100/24 > static routers=192.168.1.1 > static domain_name_servers=194.168.4.100 194.168.8.100 > > And have rebooted to confirm it's fine, and it's fine. > > However when the router goes down and I bring everything back up, the Pi-Hole can't reconnect to the router. I can log in to the router and see it connect briefly, but it's only briefly and then nothing. I even try enabling DHCP on the router and it still refuses to reconnect. Ultimately the only way to get it to reconnect is to factory reset the router, change the password back to my usual password, wait for the RPi02W to connect and then disable the DHCP again. Needless to say it's a pain in the arse. > > What am I doing wrong? How do I fix this?

#Solution I switched the DNS servers from Virgin Media to 8.8.8.8 and that seems to fix it. Not sure why, but it does.

Anyone using this set-up? Before I sort out my router, I'm kinda stuck with it. I can get it to work by connecting my PiHole, disabling DHCP and then reconnecting all devices manually. Only issue is that if anything happens to cause the PiHole machine to lose connection, no other device can connect to the router.

Since a few days/weeks I couldn't get images from catbox.moe when I was using my WiFi with pihole. The reason was that the default DNS Quad9 (filtered) was blocking it.

It took me a while to figure out how pihole actually sets the DNS.

So in the Web you go to settings and then to DNS and then tick in for example Google.

I've had some luck blocking ads on Hulu but it seems to be an ever evolving situation. Is anyone having decent success blocking Hulu ads with pi-hole? What domains do you block and which ones are required?

Hi all, I used to have pihole on an actual rasperry pi for a long time with no problems, and have recently switched to docker. However, a couple of weeks after doing so I noticed that there are now an excessive amount of requests to location.services.mozilla.com - nearly 86000 in the last 24 hours alone.

I have always used Firefox, but this seems like weird behaviour. I have Pihole set up as the DNS server in the router settings, but am not using the pihole as a DHCP server.

Let me know what logs to post, if any. Thanks.

I recently got Pihole setup up and it’s working fine so far for everything that actually uses it. However, I know Roku uses hardcoded DNS to direct its requests to Google DNS. I can set a static route in my router that forwards all traffic for 8.8.8.8 and .4.4 to my pihole address, and I even start to see Roku requests on the pihole dashboard, but the Roku itself just completely shits the bed and acts as if it has no internet connectivity at all.

I’m using a number of block lists from Firebog, and I do see quite a few blocks for Roku addresses in those. Are there certain essential domains that need to be whitelisted for Roku to work? Or have they just finally managed to get their device to just not work with any sort of traffic filtering?

Hello everyone!

I set up a pi-hole yesterday. I initially wanted to block youtube ads on my samsung tv but thought it was a good thing all around and I had an old raspberry collecting dust in the basement, so i just went for it. The installation worked fine and it seems to be blocking ads as supposed. But not the youtube ads. I only read about this being an issue on pi holes later. So I went on and added this list to mi pihole by following the steps as recommended. But yet, I still get a lot of ads through yt. Can somebody help me please?

This community has been abandoned by its creator. It needs one or more new moderators to bring it back to life! If you are interested in becoming a moderator, leave a comment in this post.

You can message @kersploosh@sh.itjust.works with any questions.

Hay @All !

Just wanted to start a conversation in this community ;)

What filter lists do you use?

I am using:

Feel free to ask other questions!

PS.: #1 :P edit: fix spoiler