No, because the law cares about intent, not technical details. Having my property do DNS over HTTPS because that’s what I, the owner, wanted is fine; having my property do DNS over HTTPS because that’s what some non-owner entity wanted against my will as the owner is not.
They do, but thankfully with pfSense you can do DNS overrides with firewall rules to force all network devices to use local DNS, blocking everything else.
I’m surprised it didn’t just have google’s DNS hardcoded to bypass your pihole.
That ought to be illegal.
(No, seriously: disobeying DNS the owner set by DHCP ought to count as “exceeding authorized access” under the CFAA.)
Counter point on that, that might affect the legality of DNS over HTTPS
No, because the law cares about intent, not technical details. Having my property do DNS over HTTPS because that’s what I, the owner, wanted is fine; having my property do DNS over HTTPS because that’s what some non-owner entity wanted against my will as the owner is not.
Rather: they are free to do protocol negotiation with the DNS server I supply. If it speaks DoH, go for it.
They do, but thankfully with pfSense you can do DNS overrides with firewall rules to force all network devices to use local DNS, blocking everything else.
https://dominetec.com.br/en/redirect-all-dns-requests-to-pfsense-router
Neat! Trying this in a few minutes. Be lovely having everything go through my local Pihole VM.
next move is theirs… knight to queen’s dns-over-https
There are several DoH IP lists on github. Find one that is staying updated and use it as an alias to block them all
Chromecasts do that. I had to intercept port 53 on the router to fix it.
DNS over ssl.
I redirect all out going dns requests to my self hosted DNS server.
Only one I can’t block is DoH. DoT is easily blocked and my firewall picks up on it.