4 ms·
NAT64/DNS64 allow a v6-only host to connect to v4-only hosts. If you are a T-Mobile US customer this is literally how you have all IPv4 connectivity. Here are A
by snuxoll 7y ago
NAT64/DNS64 allow a v6-only host to connect to v4-only hosts. If you are a T-Mobile US customer this is literally how you have all IPv4 connectivity. Here are AAAA records I get for amazon.com from my T-Mobile iPhone:
amazon.com. 2S IN AAAA 2607:7700::19:0:1:cdfb:f267
amazon.com. 2S IN AAAA 2607:7700::19:0:1:b020:67cd
amazon.com. 2S IN AAAA 2607:7700::19:0:1:b020:62a6
These are NAT64 addresses within TMoUS’ prefix, if I try to ping an IPv4 address it is rewritten automatically as well (though this is a feature of iOS).
If you get people to v6 they can continue to access v4 with numerous transition tools like this, even if dual-stack isn’t an option. You can’t go the other way though.
- commandersaki 7y agoSo NAT64/DNS64 is really about connectivity to v4-only. This only adds more value to the v4 network by giving it more reach. If you want to reach the v6 Internet, the best way is to have a transition mechanism for v4-only hosts to talk to v6.
- snuxoll 7y agoUnfortunately that’s not possible, v6 has plenty of address space so you can carve a /96 out of your network to implement a transition layer so clients can be v6-only before the larger internet. There’s no way to represent the v6 network in 32-bit v4 addresses, so you have to start getting clients to v6 first.
- commandersaki 7y agov4-only means (as specified earlier) that connectivity is over a routable v4 address; a v4 host in a v4-only network can be dual stack, so it's possible to talk to v6 addresses, which this proposal actually addresses.