2
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 26 Nov 2023
2 points (75.0% liked)
Homelab
371 readers
2 users here now
Rules
- Be Civil.
- Post about your homelab, discussion of your homelab, questions you may have, or general discussion about transition your skill from the homelab to the workplace.
- No memes or potato images.
- We love detailed homelab builds, especially network diagrams!
- Report any posts that you feel should be brought to our attention.
- Please no shitposting or blogspam.
- No Referral Linking.
- Keep piracy discussion off of this community
founded 1 year ago
MODERATORS
I think pi holes only go so far. Unless you also block outbound DNS and have IPS/IDS setup to catch and block it on other ports and via encapsulation inside https... it's just another loosing battle.
If I was a TV manufacturer I'd give absolute fuck all about the DNS address assigned to the TV by your router.... or ANY DNS server that has a RFC1918 address. I'd be writing code that would try to hit DNS on the internet that I can use, possibly on a different port than 53 or via HTTPS tunnel.. I'd also have a few DNS entries hardcoded to IP's owned by the TV manufacturer or a subsidiary or even something in Azure/AWS....aside from trying the obvious 1.1.1.1 and 8.8.8.8 and ensuring the records I need are on those servers..
If you want to create a deny all rule and then spend weeks surfing firewall logs, creating allow rules randomly and via trial and error because half the shit doesn't work on the TV and you didn't write the code so you basically are guesing and googling what it needs to talk to.... have at it. Or. Never connect the TV to the internet. Ever.