Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.
We’re increasing our support for Azure services.
we were not able to assign more than 20 alias record sets, point to a public ip, in azure, can you increase this limit??
like issues with multiple ACL's and SA's if multiple address ranges used.
Apologies. There was apparently a misunderstanding and the status has been corrected.
This specific feedback item is for NAT from private IP space to private IP address
Any update on this would be great +1
Thanks for your feedback
We’ll review this feature to include it on our roadmap.
nice to have this feature instead deleting them
Domain registration is being evaluated and remains on our long term road-map. However, it is not planned for CY 2019.
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.
Admin, Thanks for the response.
So when looked at the below doc it says we need to deploy IPv6 NIC's as well in addition to IPv4 for the VM's, so wondering if thats a mandatory step here!! can't we access IPv4 VM via IPv6 LB from IPV6 client!! yeah looking to know, if something like NAT64 needed on LB??
This is not me but a customer tried this and faces this issue with ipV6 DNS in azure."
"I wanted to try the IPv6 feature on Azure External LB.
I went through some docs and saw Sean Wheeler's template @ https://azure.microsoft.com/en-us/resources/templates/201-load-balancer-ipv6-create/
went and Deployed that template... things worked fine. Until when I tried accessing the IPv6 DNS assigned for LB.
but resulted in Page cannot be displayed ( I have IIS setup for VM's default configs ).
IPv4 works fine but not Ipv6... can someone direct me to right way of troubleshooting or may be some explanation of what could have gone wrong?
When I take a look, everything seems to be fine.
I also tried accessing the link http://ipv6-test.com/validate.php , on entering the IPv6 DNS url , it shows correct Ipv6 address but webpage still fails to load.