101–110 of 138 posts
I have a docker-compose.yml locally with: dnsmasq -> pihole -> stubby The first dnsmasq is for local .test domains for dev. Works well for when i'm not on one of my networks.
Why not configure your local .test domains in your Pi-hole? That's also dnsmasq, you can use the same configuration options.
On the go is the key here.
Can someone explain how the use case differs from simply using a well-curated hosts file? (like Steven Black's)
You can even find comments about it on this thread
Earlier quoted context omitted.
How is it supposed to be harder to hack? I thought the main point is to have the blocking enabled in the whole network, including devices like smartphones.
Because the Pi-Hole doesn't run untrusted code, like a personal computer does (e.g. Javascript, installed applications, etc.). Same holds for smartphones.
With it, I would simply switch to one of the many pi-holed/filtered DOH services[0] out there, or even roll my own on a cheap VPS.
On iOS there is DNSCloak which is excellent, Android 9+ has built-in support (Private DNS).
[0]: like pi-dns.com or blahdns.com
Or if you already run dsnmasq you can: - uncomment this in your dnsmasq.conf: addn-hosts=/etc/banner_add_hosts - put this in a file in /etc/cron.daily: wget -O /etc/banner_add_hosts 'https://pgl.yoyo.org/adservers/serverlist.php?showintro=0&mimetype=plaintext'
I've been using https://nextdns.io/ for a while and I really like it. You can do DNS over HTTPS through Firefox (sadly not on an OS level in Windows for example, but that's fine -- I'm sure OS level support works better on Linux), and it supports a lot of user-level customization. You can add and remove entire blocklists, you can black/white-list specific domains, see logs of your blocks, some analytics, create your…
Android 9 and later natively supports "Private DNS" which is DNS over TLS.
All work fine with NextDNS and I have multiple profiles for each hardware I use it on. Eg, I use more block lists on my phone than my other devices.
Earlier quoted context omitted.
I recently spent a bunch of time comparing NextDNS vs PiHole. The reality is their features-sets are pretty close, but I eventually settled on NextDNS and here were some of my takeaways: NextDNS Pros: * Can use NextDNS on any network (thanks to their apps or just regular DNS-over-HTTP/TLS). * (Could get similar functionality on PiHole with a remote hosted PiHole + VPN, but much more complex to setup) * NextDNS allows…
-NextDNS is a product with a free tier. It will always be limited in that sense. +Pihole is free and open. It is also yours to build,manage,customize as you please. -NextDNS is also further away, meaning there will be much more latency for all your DNS queries. It is usually best to run your own resolver, or have a local DNS server in your network. +Pihole sits on a device on your network. You can also enable recursi…
But your local PI resolver would likely have to pass on your request to an upstream DNS server if it isn't cached. Although its negligible, this extra hop would add latency. This is assuming the result isn't in the OS or browser DNS cache.
Earlier quoted context omitted.
-NextDNS is a product with a free tier. It will always be limited in that sense. +Pihole is free and open. It is also yours to build,manage,customize as you please. -NextDNS is also further away, meaning there will be much more latency for all your DNS queries. It is usually best to run your own resolver, or have a local DNS server in your network. +Pihole sits on a device on your network. You can also enable recursi…
> NextDNS is also further away, meaning there will be much more latency for all your DNS queries. It is usually best to run your own resolver, or have a local DNS server in your network. But your local PI resolver would likely have to pass on your request to an upstream DNS server if it isn't cached. Although its negligible, this extra hop would add latency. This is assuming the result isn't in the OS or browser DNS…
I've been using https://nextdns.io/ for a while and I really like it. You can do DNS over HTTPS through Firefox (sadly not on an OS level in Windows for example, but that's fine -- I'm sure OS level support works better on Linux), and it supports a lot of user-level customization. You can add and remove entire blocklists, you can black/white-list specific domains, see logs of your blocks, some analytics, create your…
I’ve just looked into this - it looks excellent. Can I ask: is this an all-round superior solution to running your own pi-hole? I set up dual redundant pi-holes on raspberry pi 4s on my home network but switching all devices to NextDNS would give me access to filtered DNS even when away from home, plus save me the trouble of running two raspis (including two Ubuntu instances) just for that purpose. Could anyone knowl…