Azure ASE and ASP deployment

Question

When deploy Azure App service environment with bicep code it did not deploy the ase.appserviceenvironment.net DNS record. Would it resolve the application and kudu console if I create DNS zone and add them manually after the deployment? If so does it take an hour for DNS change to propagate?

Answer 1

Hi @Prasant Chettri

Yes, you can manually create the DNS records for your Azure App Service Environment (ASE) if they were not automatically created during the deployment. Here are the steps you can follow:

1. Create a zone for your custom domain.
2. Create an A record in that zone that points * to the inbound IP address used by your ASE.
3. Create an A record in that zone that points @ to the inbound IP address used by your ASE.

This should help resolve the application and Kudu console. However, please note that any changes to DNS records need some time to propagate across the internet. This is known as DNS propagation and it takes more than an hour to propagate.

DNS propagation refers to the time required for DNS servers worldwide to update their cached information for a domain name. The amount of time it takes for DNS propagation can vary based on several factors, including the Time to Live (TTL) of the DNS record, the record type, the DNS cache, and network conditions. Typically, DNS changes will propagate within a few hours, but it can take up to 24-48 hours for everything to propagate across the Internet.

Hope that helps.

Grace