changing the TV’s DNS servers or disconnecting it from the internet entirely.
Chiming in as an Australian budget VIDAA owner.
I spotted that this TV attempts to query 8.8.8.8, regardless of your DNS settings. I implemented a port 53 (DNS) redirect so those queries get resolved by my local server.
I also figured out which servers are serving up ads/tracking. I fired an email to Pete and got them added to his list. You’re welcome. I’m guessing a pi-hole would work with it.
I fear the day these fucks figure out DOH or something. Not sure there’s any way to suppress or intercept that, short of just blocking all external traffic to the TV.
Setting up DoH, I already provide the expected name AND an IP. No need for plain DNS at any step. There’s no reason a corporate TV can’t do that either.
People like you help to make the internet a better place — which matters a lot to me, because one of my most desperately held beliefs is that it is possible to take the hopefulness of the early internet and combine it with the wisdom of the last few decades to produce a more robust kind of hope
attempts to query 8.8.8.8, regardless of your DNS settings.
Streaming box / stream app makers have been working around local DNS for a long time. Sometimes of course they’re assholes that want to do shitty things and do this to make interdiction harder. But sometimes there are legitimate reasons. Ones I remember… users who don’t really understand what they’re doing can be overly aggressive with blocking and block things that are necessary for a particular service (causing support problems). Sometimes the ISPs DNS servers have shit performance, and using a well known commercial provider like cloudflare or google can improve performance at scale. It’s not always evil.
Chiming in as an Australian budget VIDAA owner.
I spotted that this TV attempts to query 8.8.8.8, regardless of your DNS settings. I implemented a port 53 (DNS) redirect so those queries get resolved by my local server.
I also figured out which servers are serving up ads/tracking. I fired an email to Pete and got them added to his list. You’re welcome. I’m guessing a pi-hole would work with it.
https://pgl.yoyo.org/adservers/serverlist.php
I didn’t install the latest update, and probably never will. My TV contacts the unruly ACR servers, but the later firmware probably contacts nexxen.
I fear the day these fucks figure out DOH or something. Not sure there’s any way to suppress or intercept that, short of just blocking all external traffic to the TV.
You need plain DNS to resolve the DoH server. Just block that.
Setting up DoH, I already provide the expected name AND an IP. No need for plain DNS at any step. There’s no reason a corporate TV can’t do that either.
For other readers here is a tutorial to do DNS capture into a pihole server or other DNS
https://youtu.be/EdzDCkFaskc
People like you help to make the internet a better place — which matters a lot to me, because one of my most desperately held beliefs is that it is possible to take the hopefulness of the early internet and combine it with the wisdom of the last few decades to produce a more robust kind of hope
Streaming box / stream app makers have been working around local DNS for a long time. Sometimes of course they’re assholes that want to do shitty things and do this to make interdiction harder. But sometimes there are legitimate reasons. Ones I remember… users who don’t really understand what they’re doing can be overly aggressive with blocking and block things that are necessary for a particular service (causing support problems). Sometimes the ISPs DNS servers have shit performance, and using a well known commercial provider like cloudflare or google can improve performance at scale. It’s not always evil.
Thank you for this. I will check later today on my own tv to see what its pulling in the background.