AdGuard Home: Network-wide ad- and tracker-blocking DNS server
91–100 of 258 posts
Re: AdGuard Home: Network-wide ad- and tracker-blocking DNS server
#92The primary use case for these is for blocking ads on devices that don't allow running a real browser and yet still shows ads, such as "smart home" devices, TVs, etc.
Re: AdGuard Home: Network-wide ad- and tracker-blocking DNS server
#93Re: AdGuard Home: Network-wide ad- and tracker-blocking DNS server
#94Earlier quoted context omitted.
I've used ControlD [ https://controld.com/ ] for this and liked it. Does anyone know how NextDNS compares to it? ControlD has worked well for me, outside a few UI complaints I have with their site. I do have some concerns with trust as I don't know much about ControlD, and I'd rather use the most trusted service for this.
I've been a NextDNS user for years now, and am trying out ControlD (last week) before I commit to switching. NextDNS development seems to have stalled and there are a number of conveniences missing, such as being able to label allowlist entries (ControlD supports this). Also, running the NextDNS app on a device that use a different profile then the one on my home router results in constant issues when the device wake…
So ControlD would be significantly more than NextDNS for me personally.
Re: AdGuard Home: Network-wide ad- and tracker-blocking DNS server
#95Re: AdGuard Home: Network-wide ad- and tracker-blocking DNS server
#96For example if the box with Adguard Home or pihole crashes, can you configure your router or your devices in a way that would instead go to say cloudflare or google DNS?
Re: AdGuard Home: Network-wide ad- and tracker-blocking DNS server
#97I ran a competing project[0] on my home network for a few years before I discovered NextDNS[1]. What I lost in performance (requests don't leave my house) I gained in portability: ALL my devices can take advantage – at home and away – and time-saved. PiHole works 90% of the time, but when it did stop working, I'd have to spend a bit of time fixing it. At $20/year, I simply couldn't compete with NextDNS. Note: This is…
I'm curious what issues you ran into with Pi-hole? I was running my instance for years without a single hiccup. I ended up moving to AdGuard Home about a year ago though because I wanted to run it on my OPNSense box. I have an automatic WireGuard VPN set up on my devices to VPN into my home network when I'm not connected to my SSID, so my local DNS still works remotely.
Exact same setup for me also.
I also run Tailscale since I have run into some remote networks that blocked wireguard's port.
Re: AdGuard Home: Network-wide ad- and tracker-blocking DNS server
#98I currently use browser based blocking and find a lot of sites don’t work at all. Typically SPAs.
But if I have to use them, I can disable the adblocker in two clicks. How does that compare?
Re: AdGuard Home: Network-wide ad- and tracker-blocking DNS server
#99AdGuard Home: Network-wide ads and trackers blocking DNS server - https://news.ycombinator.com/item?id=33387678 - Oct 2022 (113 comments)
Show HN: AdGuard Home – an open source network-wide ad blocker - https://news.ycombinator.com/item?id=18238503 - Oct 2018 (2 comments)
Re: AdGuard Home: Network-wide ad- and tracker-blocking DNS server
#100Earlier quoted context omitted.
I've been a NextDNS user for years now, and am trying out ControlD (last week) before I commit to switching. NextDNS development seems to have stalled and there are a number of conveniences missing, such as being able to label allowlist entries (ControlD supports this). Also, running the NextDNS app on a device that use a different profile then the one on my home router results in constant issues when the device wake…
It looks like cost is not comparable. ControlD pricing is per user and a router costs $5/month, but NextDNS is a flat $20/year. So ControlD would be significantly more than NextDNS for me personally.