4 ms·
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.
by MayeulC 6y ago
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.
- jon-wood 6y agoCurrently, we don’t. The devices don’t support IPv6, so it’s not a problem we’ve had to deal with so far.
- moonbug 6y agoGreat work there.
- dingaling 6y agoSo you'll only start working on the problem when IPv6-aware devices start failing? Why wait?
- zinekeller 6y agoNot 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 ;).
- jon-wood 6y agoExactly 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.