Comment on Self-Hosting a DNS Sinkhole is really important
LemmyPlaceDN@europe.pub 4 days ago
I only know the basics of networking, so I’ve been wondering why this “DNS-sinkhole” fubctionality can’t simply be implemented directly in private routers as a simple blocklist instead of adding a new device to your network. Do routers not support this for technical or security reasons?
Routers are usually hardware level optimized for throughput, filtering is inherently computationally expensive compared to routing, especially if you have to keep up multi-gigabit throughput
You could totally do it at the router, it would just become a more expensive piece of hardware and most people choose to cheap out
I doubt a DNS filter would noticeably increase CPU usage. We’re not talking about deep packet inspection here.
Appoxo@lemmy.dbzer0.com 3 days ago The german router “FritzBox” recently did implement this.
A very rudimentary version of it but still.
A Raspberry Pi 3b is adequate to run PiHole to do the job, or implementing AdGuard DNS.
However, these require a little skill and knowledge to implement.
Consumer routers aren’t built to do the job.
I love my Pihole. It blocks ads on my PCs, my iPads, our streaming devices, etc. It also blocks telemetry gathering by other device manufacturers.
glitch1985@lemmy.world 4 days ago
Most consumer routers don’t offer this functionality out of the box, likely because manufacturers don’t consider it essential for most users. There’s no major technical reason it couldn’t be built in though. You can already set up DNS sinkholing with OPNsense or pfSense if you don’t mind running and managing your own router.