4 ms·
$ ip -4 addr show | grep eth0 # nothing $ dig news.ycombinator.com AAAA +short 64:ff9b::d1d8:e6f0 $ wget -6 https://news.ycombinator.com -O /dev/null
by Dagger2 7y ago
$ ip -4 addr show | grep eth0
# nothing
$ dig news.ycombinator.com AAAA +short
64:ff9b::d1d8:e6f0
$ wget -6 https://news.ycombinator.com -O /dev/null
Resolving news.ycombinator.com (news.ycombinator.com)... 64:ff9b::d1d8:e6f0
Connecting to news.ycombinator.com (news.ycombinator.com)|64:ff9b::d1d8:e6f0|:443... connected.
HTTP request sent, awaiting response... 200 OK
[...] ‘/dev/null’ saved [34663]
WFM!
- zzzcpan 7y agoIt's a translated with DNS64 ipv4 address into a NAT64 ipv6. They have 64:ff9b prefix.
- Dagger2 7y agoIndeed it is, and it works fine. v4-only websites aren't a problem for running v6-only.
- gerdesj 7y agoI am now at home and tried your experiment but I have IPv4 as well as IPv6. The wget forced to v6 does not work here. That's a bug somewhere. My eyes are no longer happy 8( ... 8) ... ahh, all OK now!
- Dagger2 7y agoI have a NAT64 translator handling the translation, plus a DNS64 server to point clients to it. You probably don't have those, because it's typically easier to run native v4 instead. I just wanted to make the point that v4-only websites are totally not a problem.
- cesarb 7y ago> I just wanted to make the point that v4-only websites are totally not a problem. They will be once DoH breaks DNS64, unless Cloudflare invents a way to make it somehow work (perhaps hosting their own NAT64 gateway?).
- Dagger2 7y agoSince they seem to want to take over the internet, I guess that would be right up their street. Clients can also synthesize the DNS64 records themselves locally, or use 464xlat.