291
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 27 Oct 2026
291 points (99.0% liked)
Technology
89117 readers
3965 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
I'm surprised it didn't just have google's DNS hardcoded to bypass your pihole.
Chromecasts do that. I had to intercept port 53 on the router to fix it.
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.
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’ll get blocked too.
That ought to be illegal.
(No, seriously: disobeying DNS the owner set by DHCP ought to count as "exceeding authorized access" under the CFAA.)
Unfortunately the monkey's paw would curl here and using DNS other than that provided by your ISP would become illegal.
(I know there's a difference between your devices using their network to access the internet and your "purchased" (licensed software running on) your device using your network to access the internet - but the monkey doesn't care)
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.