Ipv6 #449
Merged
Ipv6 #449
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Preview link: https://antares-blog-staging-pr-449.azurewebsites.net
|
crosenblatt
reviewed
May 28, 2024
|
|
||
| 1. IPv6 inbound support (multi-tenant) | ||
| 1. IPv6 non-vnet outbound support (multi-tenant) | ||
| 1. IPv6 vnet outbound support (multi-tenant and App Service Environment v3) |
There was a problem hiding this comment.
Has the ASE team confirmed any level of support? We are so far not claiming anything works on ASE
There was a problem hiding this comment.
I am also the ASE team :-) and driving the dialog with swift on supporting IPv6. Message is that they should have swift v2 ready by Oct and we can start implementing then - great risk of delays and no idea how long our implementation will take so a careful guess is mid-CY25. The list is also to say that it is not currently supported, but will be coming. I'll see if I can make it more clear.
| * Only a subset of regions are supported - see the list below. | ||
| * Basic and Standard tier is currently not supported. | ||
| * Functions Consumption may temporarily have extra IP addresses in the DNS result. | ||
| * Functions Consumption and Elastic Premium may not remove the IPv4 address in IPv6 mode. |
There was a problem hiding this comment.
Didn't we determine this was just a DNS caching thing and it goes away?
There was a problem hiding this comment.
I believe this is referring to the issue where old function apps that were created using a secondary flex consumption A record will not have their A record removed in IPv6 mode
|
|
||
| IPv6 inbound requires two things. An IPv6 address that accepts traffic coming in, and a DNS record that returns an IPv6 (AAAA) record. Finally you'll also need a client that can send and receive IPv6 traffic. This means that you may not be able to test it from you local machine since many networks today only support IPv4. | ||
|
|
||
| Our stamps (deployment units) will all have IPv6 addresses added. When these are added, you can start sending traffic to both the IPv4 and IPv6 address. To ensure backwards compatibility, the DNS response for the default host name (_app-name_.azurewebsites.net) will return only the IPv4 address. If you want to change that, we have added a site property called `IPMode` that you can configure to `IPv6` or `IPv4AndIPv6`. If you set it to IPv6 only, your client will need to "understand" IPv6 in order to get a response. Setting it to IPv4 and IPv6 will allow you to have existing clients use IPv4, but allow capable clients to use IPv6. |
There was a problem hiding this comment.
You can call out that an easy way to test is using curl -6
|
|
||
| Our stamps (deployment units) will all have IPv6 addresses added. When these are added, you can start sending traffic to both the IPv4 and IPv6 address. To ensure backwards compatibility, the DNS response for the default host name (_app-name_.azurewebsites.net) will return only the IPv4 address. If you want to change that, we have added a site property called `IPMode` that you can configure to `IPv6` or `IPv4AndIPv6`. If you set it to IPv6 only, your client will need to "understand" IPv6 in order to get a response. Setting it to IPv4 and IPv6 will allow you to have existing clients use IPv4, but allow capable clients to use IPv6. | ||
|
|
||
| If you are using custom domain, you can define your custom DNS records the same way. If you only add an IPv6 (AAAA) record, your clients will need to support IPv6. You can also choose to add both, and finally you can use a CNAME in which case you will use the behavior of `IPMode`. |
There was a problem hiding this comment.
Suggested change
| If you are using custom domain, you can define your custom DNS records the same way. If you only add an IPv6 (AAAA) record, your clients will need to support IPv6. You can also choose to add both, and finally you can use a CNAME in which case you will use the behavior of `IPMode`. | |
| If you are using custom domain, you can define your custom DNS records the same way. If you only add an IPv6 (AAAA) record, your clients will need to support IPv6. You can also choose to add both, and finally you can use a CNAME to the default hostname of the site in which case you will use the behavior of `IPMode`. |
|
|
||
| * Only a subset of regions are supported - see the list below. | ||
| * Basic and Standard tier is currently not supported. | ||
| * Functions Consumption may temporarily have extra IP addresses in the DNS result. |
There was a problem hiding this comment.
Is this referring to the idle backup bug? Those extra IP addresses are not going to be temporary
There was a problem hiding this comment.
Perhaps we can clean them up manually (worth discussing offline)
|
|
||
| ## How does it work | ||
|
|
||
| IPv6 inbound requires two things. An IPv6 address that accepts traffic coming in, and a DNS record that returns an IPv6 (AAAA) record. Finally you'll also need a client that can send and receive IPv6 traffic. This means that you may not be able to test it from you local machine since many networks today only support IPv4. |
There was a problem hiding this comment.
Suggested change
| IPv6 inbound requires two things. An IPv6 address that accepts traffic coming in, and a DNS record that returns an IPv6 (AAAA) record. Finally you'll also need a client that can send and receive IPv6 traffic. This means that you may not be able to test it from you local machine since many networks today only support IPv4. | |
| IPv6 inbound requires two things. An IPv6 address that accepts traffic coming in, and a DNS record that returns an IPv6 (AAAA) record. Finally you'll also need a client that can send and receive IPv6 traffic. This means that you may not be able to test it from your local machine since many networks today only support IPv4. |
seligj95
approved these changes
May 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary