72% of smart TVs and 46% of game consoles hardcode DNS settings

Re:72% of smart TVs and 46% of game consoles hardcode DNS se... by MayeulC on Saturday December 05, 2020 @08:21AM (#25314347)

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.

[ Parent | on HN ]

Re:72% of smart TVs and 46% of game consoles hardcode DNS se... by jon-wood on Saturday December 05, 2020 @08:32AM (#25314409)

Currently, we don’t. The devices don’t support IPv6, so it’s not a problem we’ve had to deal with so far.

[ Parent | on HN ]

Re:72% of smart TVs and 46% of game consoles hardcode DNS se... by dingaling on Saturday December 05, 2020 @09:47AM (#25314894)

So you'll only start working on the problem when IPv6-aware devices start failing?

Why wait?

[ Parent | on HN ]

Re:72% of smart TVs and 46% of game consoles hardcode DNS se... by zinekeller on Saturday December 05, 2020 @09:56AM (#25314969)

Not the OP, but you should also be reminded that many of these limitations are brought out by cost-cutting measures that we didn't have control of and could be used to fire us immediately, and even when IPv6 is implemented most IoT backend servers only operate over IPv4 anyway. Another one that you might be angry about is only including 2.4GHz-band WiFi even though 5GHz WiFi is already ubiquitous (although only including 5GHz WiFi is much more questionable ;).

[ Parent | on HN ]

Re:72% of smart TVs and 46% of game consoles hardcode DNS se... by jon-wood on Saturday December 05, 2020 @12:21PM (#25316258)

Exactly this, we’re a small team and have to pick our battles. In practice very few people have IPv6 only connections, and even fewer of the people who buy our products.

[ Parent | on HN ]