The suggestion seems to be a question about IPv6 clients accessing an IPv4-only VM. In Azure, IPv6 traffic from the internet is plumbed directly to native IPv6 endpoints on VMs. There are many advantages to this approach but one disadvantage is the VMs must have IPv6 endpoints and the applications must be IPv6-aware. In the example below, I would guess the web server has not been configured to monitor both the IPv4 and IPv6 endpoints on the VM but that is really a support question.
It is possible to translate between IPv4 and IPv6 (NAT64) which is not currently supported in Azure so we’ll take this suggestion as a vote for NAT64 support.
An error occurred while saving the commentPaul McIntyre commented
IPv6 is pretty much unusable in Azure, Amazon, and GCP. Because their whole setup is built on NAT, it's a total hack. IPv6 should be on by default and should just work, like IPv4 is on by default and we expect it to just work. Without a bunch of load balancing gymnastics.
- Anavi N [MSFT]Paul McIntyre shared this idea ·