Domain migration during frontdoor migration

Question

Domain migration during frontdoor migration

David Ondracek 10

Hello,

we are about to migrate our infrastructure from the Front Door (classic) to the Premium tier using the Migration wizard. While everything seems to be ready (migration validation passed without issues), there's one thing we're not quite sure about:

we have several domains pointing via CNAME to the current front door (let's call it 'fd-old'), so we have records like "CNAME products fd-old.azurefd.net". Now when we migrate and select the name "fd-new" as the new frontdoor name during the migration, will we have to do anything for the domains to be migrated? Will the domain be re-mapped automatically?

Thank you!

David

KapilAnanth-MSFT 49,616 Reputation points Microsoft Employee Moderator

2023-01-13T03:33:51.6033333+00:00

Hi @David Ondracek ,

Just checking in to see if the below answer helped. If this answers your query, please don’t forget to click "Accept the answer" and Up-Vote for the same, which might be beneficial to other community members reading this thread. And, if you have any further query do let us know.

Thanks,

Kapil
Tom Plant 16 Reputation points

2023-01-20T03:44:28.03+00:00

I've run into this issue too. After migration, the old domain shows under "Domains > Migrated domains" with a Succeeded provisioning state, deployed cert, and successful DNS state. But it's not associated with any endpoints, and I receive an "Internal domain can only be added to the original route." error when trying to associate.

Metrics show traffic is still routing to the classic Front Door. It's still working, but now we can't make changes because the classic resource is edit-locked.
KapilAnanth-MSFT 49,616 Reputation points Microsoft Employee Moderator

2023-01-23T06:24:55.8433333+00:00

@Tom Plant ,

I am not aware of this behavior.

I believe we will need a specialized 1:1 session, where a support engineer can have a screen share session to pinpoint the issue. If you have a support plan you may file a support ticket, else please do let us know, we will try and help you get a one-time free technical support.

In case you require one-time free support, please send an email with subject line “Attn:kaananth | Domain migration during frontdoor migration” to AzCommunity[at]Microsoft[dot]com

with the following details, I will follow-up with you.

• Reference this Q&A thread URL

• Azure Subscription ID

• Azure resource ID

Note: Please do not share any PII data as a public comment.

Cheers,

Kapil
Tom Plant 16 Reputation points

2023-01-24T02:49:21.7966667+00:00

@KapilAnanth-MSFT it's ok, I just updated the CNAME to the new AFD domain
KapilAnanth-MSFT 49,616 Reputation points Microsoft Employee Moderator

2023-01-24T03:45:23.4633333+00:00

Thanks for the update @Tom Plant .

1 answer

Your answer

KapilAnanth-MSFT 49,616 Reputation points Microsoft Employee Moderator

2023-01-13T03:33:51.6033333+00:00

Hi @David Ondracek ,

Just checking in to see if the below answer helped. If this answers your query, please don’t forget to click "Accept the answer" and Up-Vote for the same, which might be beneficial to other community members reading this thread. And, if you have any further query do let us know.

Thanks,

Kapil
Tom Plant 16 Reputation points

2023-01-20T03:44:28.03+00:00

I've run into this issue too. After migration, the old domain shows under "Domains > Migrated domains" with a Succeeded provisioning state, deployed cert, and successful DNS state. But it's not associated with any endpoints, and I receive an "Internal domain can only be added to the original route." error when trying to associate.

Metrics show traffic is still routing to the classic Front Door. It's still working, but now we can't make changes because the classic resource is edit-locked.
KapilAnanth-MSFT 49,616 Reputation points Microsoft Employee Moderator

2023-01-23T06:24:55.8433333+00:00

@Tom Plant ,

I am not aware of this behavior.

I believe we will need a specialized 1:1 session, where a support engineer can have a screen share session to pinpoint the issue. If you have a support plan you may file a support ticket, else please do let us know, we will try and help you get a one-time free technical support.

In case you require one-time free support, please send an email with subject line “Attn:kaananth | Domain migration during frontdoor migration” to AzCommunity[at]Microsoft[dot]com

with the following details, I will follow-up with you.

• Reference this Q&A thread URL

• Azure Subscription ID

• Azure resource ID

Note: Please do not share any PII data as a public comment.

Cheers,

Kapil
Tom Plant 16 Reputation points

2023-01-24T02:49:21.7966667+00:00

@KapilAnanth-MSFT it's ok, I just updated the CNAME to the new AFD domain
KapilAnanth-MSFT 49,616 Reputation points Microsoft Employee Moderator

2023-01-24T03:45:23.4633333+00:00

Thanks for the update @Tom Plant .

Answer 1

Hi @David Ondracek

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

I understand that you would like to know if the end Points of the AFD would change or not during AFD migration from classic to Premium.

Please note that AFD classic will be having a fd-old.azurefd.net endPoint while AFD standard and premium would have <endpointname>-<hashvalue>.z01.azurefd.net .

i.e, the endPoints would change.

However, the classic Front Door endpoint name will continue to work after migration. But it is recommended to update the CNAME records to the newer endPoint names.

This is documented here

User's image

Thanks,

Kapil

Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.

Share via

Domain migration during frontdoor migration

1 answer

Your answer