github.com doesn't have an IPV6 address to resolve. I'm starting to get why people have not made the change
Discussion
NAT64 can be used to reach IPv4-only network, the real problem is reaching IPv6-only network from IPv4-only network.
Thanks for the knowledge!
If you are interested, we can implement NAT64 in all of our locations (basically, it is 64:ff9b::/96 IPv6 prefix that performs NAT from IPv6 to IPv4).
To transparently use it, the only thing that required from the customer side is to use DNS64 (for example, 2606:4700:4700::64). This will replace all DNS A records with DNS AAAA from 64:ff9b::/96 IPv6 prefix. If there are original DNS AAAA records, they will be left intact.
how would that work exactly?
As I described previously, DNS64 resolver will replace DNS A records with DNS AAAA records that are IPv4 addresses wrapped in 64:ff9b::/96 IPv6 prefix. This IPv6 prefix is routed to our NAT64 box that will perform NAT between IPv6 and reach IPv4 only networks using shared IPv4.
Your IPv6-only VM <- IPv6 -> Our NAT64 box <- IPv4 -> Github (for example)
