When I setup pihole, the google home speakers I had were making dns requests something like 20k times a day. More than pretty much every other device on my network.
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.
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.
RFC 2132 says DHCP option 6 provides “a list of Domain Name System name servers available to the client”. That’s a MAY use, not a MUST use. You are welcome to block DNS requests to outside servers if you prefer.
RFCs are subordinate to laws. If I, the device and network owner, want my device to use the DNS I set and the device does differently, I want the rogue corp prosecuted and IDGAF what some goddamn RFC says!
Similar for my Google nest, it’s the #1 host in number of daily requests in my network, around one every 500ms
Now it’s on it’s own vlan so there’s nothing that they can report on my network, but it’s really concerning that a thermostat calls home this often. It should be enough to do it once an hour to check the outside temperature and only if it’s enabled.v
When I setup pihole, the google home speakers I had were making dns requests something like 20k times a day. More than pretty much every other device on my network.
I removed them all after that.
I’m surprised it didn’t just have google’s DNS hardcoded to bypass your pihole.
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.
Chromecasts do that. I had to intercept port 53 on the router to fix 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
next move is theirs… knight to queen’s dns-over-https
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.
RFC 2132 says DHCP option 6 provides “a list of Domain Name System name servers available to the client”. That’s a MAY use, not a MUST use. You are welcome to block DNS requests to outside servers if you prefer.
RFCs are subordinate to laws. If I, the device and network owner, want my device to use the DNS I set and the device does differently, I want the rogue corp prosecuted and IDGAF what some goddamn RFC says!
I don’t think you’d be able to find a court receptive to that argument.
Every court that disagrees is tyrannical and needs to be fucking abolished.
Similar for my Google nest, it’s the #1 host in number of daily requests in my network, around one every 500ms
Now it’s on it’s own vlan so there’s nothing that they can report on my network, but it’s really concerning that a thermostat calls home this often. It should be enough to do it once an hour to check the outside temperature and only if it’s enabled.v
Same for Roku, and worse now that they were bought out. Sorry grandma, the Roku is getting cut off. Lol