backstreetboy
Honorary Master
- Joined
- Jun 15, 2011
- Messages
- 49,397
- Reaction score
- 56,416
On Raspberry Pi OS is the latest Chromium still 88? Had to revert to 86 because 88 was filled with bugs.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
I performed an update/upgrade on Saturday. The current version is 88.0 4324.187 (Official Build).On Raspberry Pi OS is the latest Chromium still 88? Had to revert to 86 because 88 was filled with bugs.
Thanks.I performed an update/upgrade on Saturday. The current version is 88.0 4324.187 (Official Build).

So you got the extra setting to set preferred DNS on the router. Did you try flushing DNS cache on the client? And maybe terminating the DHCP lease and reconnecting the client.I'm needing some help with pi-hole, pretty pleae. I've set it up and everything seems to be working just fine. The issue is I've got the router (Huawei B618) taking care of DHCP and have set DNS on the router to the pi-hole IP. Devices connecting to the router don't seem to be going via pi-hole though?
Thanks. As I mentioned earlier, the client shows the router as the server, not the pi-hole. It works for most of the clients on the network, but some were still not being pushed via the pi-hole - could be DNS cache issues on those clients, but I will give it a couple of days to sort itself out.So you got the extra setting to set preferred DNS on the router. Did you try flushing DNS cache on the client? And maybe terminating the DHCP lease and reconnecting the client.
You can see what DNS server the client is using with "ipconfig /all". Once your Pi-hole shows as the DNS server, you're good to go.
It's also worth flushing the DNS cache via the Pi-Hole server. Also double-checking to ensure that no equipment has a secondary DNS server specified.Thanks. As I mentioned earlier, the client shows the router as the server, not the pi-hole. It works for most of the clients on the network, but some were still not being pushed via the pi-hole - could be DNS cache issues on those clients, but I will give it a couple of days to sort itself out.
This is mine with just 2 of us at home. A lot of the blocking is just Netflix presentation tracking though... I am always annoyed using my mobile on another network, so much junk and ads.Quick update - the Pi-hole is working brilliantly today. I must admit, I'm a bit surprised by the number of queries it's processed so far. Small office of 4 people, and 25 000 queries in the first day

NextDNS might help you with that problem.This is mine with just 2 of us at home. A lot of the blocking is just Netflix presentation tracking though... I am always annoyed using my mobile on another network, so much junk and ads.
Didn't think it was a problem? I use CloudFlare and OpenDNS as the providers on the Pi-Hole. NextDNS seems like an ad blicking DNS which is the job the Pi-Hole is already doing. Or am I missing some benefit of using it?NextDNS might help you with that problem.
When you’re not on your network, it solves ad blocking.Didn't think it was a problem? I use CloudFlare and OpenDNS as the providers on the Pi-Hole. NextDNS seems like an ad blicking DNS which is the job the Pi-Hole is already doing. Or am I missing some benefit of using it?
Think of it as a hosted Pi-Hole, definitely not a replacement for a VPN though.Sorry, it's been a long day at work. You mean using NextDNS on my mobile as the DNS provider?
I do have Blokada installed but it likes to disable itself...
After setting up Pi-Hole at the office, I've got Adguard Home going at home (want to compare the two). Adguard is working as planned, except that all the queries are shown as coming from my external IP (currently 105.186.228.xxx) meaning I can't configure rules per device. Anyone else had this issue?
Only way I could get this to work was to use adguard for DHCP. Router doesn't have many options for it's DHCP / DNS configThat's the IP you get for devices on your home network?
I will assume your DHCP is on your router, and your router is the DNS relay to which you have pointed to AGH. Normally in this setup, the AGH will logs all queries coming from the router's IP instead of clients. Why yours is the external IP is strange.
Anyway, you can set the DNS server on the DHCP settings so that each client will call the AGH directly instead of using the router. This is what I do.