Migrated from edgio but azureedge.net do not issue certificate and do not work

PN 0

I've migrate from Edgio to Frontdoor using azure tutorial but the certificate still says "issuing" and the domain, when called, says "DNS_PROBE_FINISHED_NXDOMAIN"

Ganesh Patapati 3,530 Reputation points Microsoft Vendor

2025-01-27T21:45:11.1066667+00:00

Hi PN

Greetings!

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

I wanted to check if you had the opportunity to review the answer posted by Vahid Ghafarpour useful in resolving your issue.

If it was helpful, please click "Upvote and Accept Answer" on his post to let us know.

We are here to assist you, so if you have any further questions, please feel free to ask.

Regards,

Ganesh
Ganesh Patapati 3,530 Reputation points Microsoft Vendor

2025-01-28T17:39:29.96+00:00

Hi PN

Greetings!

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

I wanted to check if you had the opportunity to review the answer posted by Vahid Ghafarpour useful in resolving your issue.

If it was helpful, please click "Upvote and Accept Answer" on his post to let us know.

We are here to assist you, so if you have any further questions, please feel free to ask.

Regards,

Ganesh
PN 0 Reputation points

2025-01-28T21:15:21.9833333+00:00

Hi @Vahid Ghafarpour ! Thanks for the help and sorry for not answering quickly. Unfortunately that don't help me because I was migrating from Edgio using azureedge.net domain and I need to support an old app version that uses that one still. I've added a new custom domain with my domain and it worked perfectly! My issue was with the migration from Edgio. The domain is validated on frontdoor but for some reason CNAME was not configured, even I was migrating and it was supposed to.
Ganesh Patapati 3,530 Reputation points Microsoft Vendor

2025-01-28T21:38:13.8433333+00:00
Hello PN

Thanks for the reply!

NOTE: This is a temporary measure due to the sudden and imminent retirement of Azure CDN from Edgio. Relying on domains like *.azureedge.net and *.azurefd.net isn't recommended as it poses availability risks. To ensure greater flexibility and avoid a single point of failure, adopt a custom domain as soon as possible.

*Migrate to Azure Front Door while retaining .azureedge.net domain

Review the feature differences between Azure CDN and Azure Front Door to identify any compatibility gaps.

Ensure you have access to a VM connected to the internet that can run Wget on Linux or Invoke-WebRequest on Windows using PowerShell.

Use a monitoring tool such as CatchPoint or ThousandEyes to verify the availability of your URLs before and after the migration. These tools are ideal because they can monitor the availability of your URLs from different global locations. Alternatively, you can use webpagetest.org, but it provides a limited view from a few locations.

Migration is supported only to Azure Front Door Standard and Premium SKUs.

Bring Your Own Certificate (BYOC) isn't supported for these domains.

Only the .azureedge.net domain is supported.

The *.vo.msecnd.net domain isn't supported.

Refer: https://learn.microsoft.com/en-us/azure/cdn/migrate-cdn-to-front-door-retain-edge-domain?toc=%2Fazure%2Ffrontdoor%2FTOC.json

Please verify your DNS settings to confirm that the CNAME record is accurately directed to your Azure Front Door endpoint.

DNS changes may take some time to propagate. To verify if the CNAME record is correctly attached, please use nslookup or Digweb to check whether the CNAME is mapped.

If the domain is validated but the CNAME is still not configured, it may be necessary to revalidate the domain or check for any errors in the validation process.

If above is unclear and/or you are unsure about something add a comment below.

Hope this helps!

Please let us know if we can be of any further assistance here.

Thanks,

Ganesh
PN 0 Reputation points

2025-01-28T22:03:32.2833333+00:00

Hi @Ganesh Patapati . Unfertunnelly I learned the hard way. I've now configured a new domain and the old azureedge.net will be deprecated, but it still is configured on old apps.

I've migrated following that tutorial and everything appears to be well configured. The domain name is validated and provision succeded. But when I try to access it, I get DNS_PROBE_FINISHED_NXDOMAIN error. The one configured with my domain works fine! It's like the azureedge.net one was validated but the CNAME for it was not configured automatically. If I open the domain, I get "Certificate State" with "Issuing" and "DNS State" with "Certificate needed".

Tried to upload screenshots but got an error.
PN 0 Reputation points

2025-01-28T22:04:45.6366667+00:00

<deleted - posted duplicated>
Ganesh Patapati 3,530 Reputation points Microsoft Vendor

2025-01-29T23:16:14.68+00:00
Hi PN

Good day!

Could you kindly provide the screenshot of the error code? Additionally, if feasible, please share the domain.

Ensure that you have added the necessary TXT records for domain verification for the product server.

Use a DNS lookup tool (like dig web) to verify that the DNS records for domain are correctly set up. You should see the appropriate A or CNAME records pointing to your Azure Front Door.

Regards,

Ganesh
Ganesh Patapati 3,530 Reputation points Microsoft Vendor

2025-01-30T19:32:57.6433333+00:00
Hi PN

Greetings!

Could you kindly provide the screenshot of the error code? Additionally, if feasible, please share the domain.

Ensure that you have added the necessary TXT records for domain verification for the product server.

Use a DNS lookup tool (like dig web) to verify that the DNS records for domain are correctly set up. You should see the appropriate A or CNAME records pointing to your Azure Front Door.

I appreciate your time and look forward to your response.

1 answer

Vahid Ghafarpour 22,430 Reputation points

2025-01-26T02:29:46.23+00:00

The DNS_PROBE_FINISHED_NXDOMAIN error typically indicates a DNS configuration issue

May this thread can help you

https://learn.microsoft.com/en-us/answers/questions/2117935/azure-static-web-apps-custom-domain-are-differentl
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Migrated from edgio but azureedge.net do not issue certificate and do not work

1 answer

Your answer