Azure / Azure/azure-quickstart-templates
201-load-balancer-ipv6-create does not assign ipv6 address
- Dominant language
- Bicep
- Stars
- 14.9k
- Forks
- 16.2k
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 6
Description
I created VM using this template on 2 locations - southafricanorth and centralus. According to https://azure.microsoft.com/en-us/updates/ipv6-for-azure-vms/ , IPV6 is supported on Central US. IPV4 addresses were correctly assigned, but IPV6 not:
```
$ nslookup ipv4.southafricanorth.cloudapp.azure.com
Name: ipv4.southafricanorth.cloudapp.azure.com
Address: 40.127.3.15
$ nslookup ipv6.southafricanorth.cloudapp.azure.com
Name: ipv6.southafricanorth.cloudapp.azure.com
Address: ::
$ nslookup ipv4.centralus.cloudapp.azure.com
Name: ipv4.centralus.cloudapp.azure.com
Address: 52.176.100.161
$ nslookup ipv6.centralus.cloudapp.azure.com
Name: ipv6.centralus.cloudapp.azure.com
Address: ::
```
In azure dashboard ipv6 address was displayed as -.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by opening the 201-load-balancer-ipv6-create template and compare its IPv4 and IPv6 configuration against Azure's IPv6-for-VM guidance. Reproduce the reported nslookup results in Central US; done means the template assigns an IPv6 address and the IPv6 hostname no longer resolves to ::.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100