Re:A cartoon intro to DNS over HTTPS (2018)
by canofbars on Sunday October 20, 2019 @03:52AM
(#21302766)
You just have to make your Pi Hole a proxy. You configure your OS/Firefox to connect to the pi for dns and the pi makes the request for the dns record.
[ Parent
| on HN ]
All this assumes though that the devices can be configured to do that. While that's likely for browsers, it's less likely for smart TVs or other IoT devices, especially if you don't trust the devices in the first place.
(Edit: removed bit about root CA certs because I misunderstood)
Re:A cartoon intro to DNS over HTTPS (2018)
by KozmoNau7 on Sunday October 20, 2019 @06:14AM
(#21303260)
The Chromecast in particular defaults to 8.8.8.8, ignoring your DHCP-assigned DNS servers.
I've completely blocked any outbound traffic to 8.8.8.8 and 8.8.4.4 from my network.
how about setup iptables to forward all DNS traffic to self-hosted Pi-hole?
if the certificates are pinned, you're screwed. Even if they aren't, it's a matter of luck if your smart$thing accepts self-signed certificates for $thingsdomain.