dotnet CDN tracking issue

[richlander]

We are making important changes to the dotnet CND, due to azureedge.net domains no longer being supported/available, per #9671.

The following are the tasks we intend to take on with target timelines. All of this is expected to evolve as we learn more.

Phase 1 (January):

• Remove azureedge.net domains from install script install-scripts#559
• Use new URIs for latest links arcade#15365
• Deploy install scripts to dotnetcli account install-scripts#558
• Remove "no cdn" concept from install script. install-scripts#563
• Publish guidance for using .NET CDNs, install scripts, and other resources for installer/archive acquition #9673
• Use CDN domains in releases-index.json #9669
• Return 301s for install script files #9682
• Update historical links to new domain #9683

Phase 2 (February-March):

• Use builds.dotnet.microsoft.com not download.visualstudio.microsoft.com #9675

Phase 3 (April?):

• Plan to disable azureedge.net domains #9676

Related:

• Test dotnet CDN Performance #9677
• .NET Install Domains and URLs Update actions/setup-dotnet#570

[allschu]

I don't know exactly what is going on the last few days, but we have a very hard time in reaching https://dot.net/v1/dotnet-install.sh from our Bitbucket pipelines.

+ curl -sSL https://dot.net/v1/dotnet-install.sh --output dotnet-install.sh

curl: (56) Recv failure: Connection timed out

Could this be part of this issue?

[baronfel]

The .NET Website uses a different routing infrastructure before it gets to the new CDN urls - see dotnet/install-scripts#582 (comment) for more details. I though this was resolved already, but can investigate with the internal team that controls this infra for us again.

[mairaw]

My monitoring is alerting that the redirection service is still having issues. I contacted the team again.

[allschu]

Yes please, thank you

[richlander]

We have a backlog item to switch redirection services. We are planning on moving to Azure Front Door.

[allschu]

Any updates? still have a lot of failures