Ad blocking with Raspberry Pi and Pi-hole

Re:Ad blocking with Raspberry Pi and Pi-hole by mulmen on Tuesday May 05, 2020 @06:03PM (#23085616)

I can and for well-behaved applications that's good. But how do I know my IoT device is using my DNS-over-HTTPS server and not a hard-coded one? There's no way to know and the only way to block DNS-over-HTTPS is to also block HTTPS.

It's much harder (or impossible) to block only some of the IoT device traffic (like ads). If I want it to function at all I have to let it spy on me and do other rude things.

My solution is to just not have IoT things but in the long run I think that will become impossible. Consumers seem to have made their choice and everything needs an IP address now.

I don't like how DNS-over-HTTPS smells and I wish there was less momentum behind it. This should be solved by OS vendors, not application developers. DNS doesn't belong at this part of the stack.

[ Parent | on HN ]

Re:Ad blocking with Raspberry Pi and Pi-hole by int_19h on Tuesday May 05, 2020 @07:05PM (#23086161)

I think this is rather orthogonal. A non-well-behaved app can use hardcoded DNS servers as well. And if the author is concerned with your ability to intercept and filter it on protocol level, they can always hack their own equivalent of DNS-over-HTTP with a basic REST service.

OTOH I expect non-malicious code to just use the platform/language/framework-standard mechanism to resolve hostnames, and I expect such mechanisms to provide all the necessary customization points, just as they did for DNS.

[ Parent | on HN ]

Re:Ad blocking with Raspberry Pi and Pi-hole by mulmen on Tuesday May 05, 2020 @07:17PM (#23086225)

Agreed, there are multiple issues here.

The solutions are different but a device like a Pi-hole probably has a part to play in both.

[ Parent | on HN ]