I’m responsible for a bunch of IoT hardware, and every firmware spec I write includes a note on not using the DNS servers provided via DHCP. While sure there are companies explicitly doing this to avoid filtering, at least in my case it’s because a significant proportion of DHCP servers are configured to send DNS to your ISP, and ISP provided DNS is almost universally terrible. They’ll ignore TTLs, rewrite NXDOMAIN r…
What DNS do you hardcode? Google's? Or do you advice the use to set it up himself? I am very suspicious of the push for https and the like. I feel it is mainly about hiding the payload from me not any third party.
72% of smart TVs and 46% of game consoles hardcode DNS settings
31–40 of 673 posts
Re: 72% of smart TVs and 46% of game consoles hardcode DNS settings
#32Just don't buy smart TV, or any of that IoT crap. It is possible to buy 58 inch dumb TV, connect that to a machine you own.
Re: 72% of smart TVs and 46% of game consoles hardcode DNS settings
#33I’m responsible for a bunch of IoT hardware, and every firmware spec I write includes a note on not using the DNS servers provided via DHCP. While sure there are companies explicitly doing this to avoid filtering, at least in my case it’s because a significant proportion of DHCP servers are configured to send DNS to your ISP, and ISP provided DNS is almost universally terrible. They’ll ignore TTLs, rewrite NXDOMAIN r…
How do you deal with NAT64? It's a real thing with some consumer ISPs. I can see myself using it as well, maybe even just to see which devices don't use DNS. Here's another idea: generate a unique IPv6 address per DNS request, route them to the correct destination, filter other IPs. Not really scalable, but usable on small networks/VLANs.
Re: 72% of smart TVs and 46% of game consoles hardcode DNS settings
#34Earlier quoted context omitted.
You're right to be suspicious. The DNS-over-HTTPS model favors those who run the servers (because they get exclusive access to monetizable end user name resolution data) and those who control the resolvers. You might control the resolver on your personal computer (for now). You probably don't control it on your phone. You most likely won't control it on your embedded devices.
The root evil here is that you can't change the root certificates in such devices. Even if you controlled its DNS, the device could still just be programmed to fail if it doesn't reach its analytics/ad/whatever server.
If it doesn't see internet it just blocks itself and goes to a screen "Oops I have no internet".
So you can forget about watching movies from your local server using the VLC app as well. Ridiculous.
Re: 72% of smart TVs and 46% of game consoles hardcode DNS settings
#35I’m responsible for a bunch of IoT hardware, and every firmware spec I write includes a note on not using the DNS servers provided via DHCP. While sure there are companies explicitly doing this to avoid filtering, at least in my case it’s because a significant proportion of DHCP servers are configured to send DNS to your ISP, and ISP provided DNS is almost universally terrible. They’ll ignore TTLs, rewrite NXDOMAIN r…
Netgear, at one point, also decided that hard-coding an IP address (for NTP, not DNS) was the best solution [0].
--
[0]: https://en.wikipedia.org/wiki/NTP_server_misuse_and_abuse#Ne...
Re: 72% of smart TVs and 46% of game consoles hardcode DNS settings
#36Earlier quoted context omitted.
So if every single piece of hardware or software followed this one crazy trick the world would be better because some people at a tech company wouldn’t have to field as many support questions?
Yes, support is supremely expensive. This is especially true in the hardware IoT space under discussion. Some large fraction of any semi-successful hardware company will exist to field a constant onslaught of support emails, handling returns, warranties, and social media. It’s a big money sink. Margins are already razor thin in hardware, so yeah anything that can be done to reduce your support costs is welcomed.
However, these IoT companies add these features mainly to benefit from selling the acquired data. The users are not asking for this. They're making it difficult for themselves.
Re: 72% of smart TVs and 46% of game consoles hardcode DNS settings
#37Just don't buy smart TV, or any of that IoT crap. It is possible to buy 58 inch dumb TV, connect that to a machine you own.
Is it? I’m still holding onto my TV from 2014 because it doesn’t have “smart” functionality. Every time I look at new ones I can’t find good dumb ones.
I wouldn’t be surprised if manufacturers start selling TVs that need to be activated online before first use, but I don’t know of any that do that already.
Re: 72% of smart TVs and 46% of game consoles hardcode DNS settings
#38Just don't buy smart TV, or any of that IoT crap. It is possible to buy 58 inch dumb TV, connect that to a machine you own.
Is it? I’m still holding onto my TV from 2014 because it doesn’t have “smart” functionality. Every time I look at new ones I can’t find good dumb ones.
Another option is to buy a monitor not a TV, but again because of market scale you'll pay a lot more for a monitor that large. They don't sell enough to consumers for volume savings to kick in, and they are aimed at commercial use so there is at least a little more "make it good rather than cheap" incentive than there is in other markets.
Re: 72% of smart TVs and 46% of game consoles hardcode DNS settings
#39I’m responsible for a bunch of IoT hardware, and every firmware spec I write includes a note on not using the DNS servers provided via DHCP. While sure there are companies explicitly doing this to avoid filtering, at least in my case it’s because a significant proportion of DHCP servers are configured to send DNS to your ISP, and ISP provided DNS is almost universally terrible. They’ll ignore TTLs, rewrite NXDOMAIN r…
Re: 72% of smart TVs and 46% of game consoles hardcode DNS settings
#40[flagged]
It's also very hard to figure out what exactly they do before making the purchase, and many vendors change their stance with devices already in the field. Look at TP-Link for example: They suddenly stopped allowing local access to their Kasa switches 2 weeks ago. No more integration with Home Assistant. Yes, they have decided to revert it already. That doesn't mean they can't do it again. I had bought 7 of these plugs because they offered local access. Now I'm a lot less sure of this brand. But the money is already sunk into it.
https://home-assistant-guide.com/2020/11/17/tp-link-kasa-sma...