Hi Everyone!

This post is continuation of a series about Azure App Service Environment (ASE v2). Over the time, I will updated this page with links to individual posts :

Deploy App Service Environment in Microsoft Azure

Create a WebApp in App Service Environment

This Post - Access App Service Environment Hosted WebApp from Azure Network and from On-Prem

Deploy a WebApp with Azure Sql in App Service Environment using Managed Identity and Private endpoint

Add Custom Domain for App Service Environment Hosted WebApp

In the previous post we have deployed a webapp in the ASE, but the webapp is not accessible, more precisely we are not able to resolute the DNS name. In this post we will see how to resolute the ASE hosted webapp DNS, so let’s get started.

In general, when you are deploying any PaaS services in Microsoft Azure, it comes with routeable DNS name. So, once resource is created you can access it using url. But, in case of internal App Service Environment you have to manage your own DNS. you can do it in your own DNS server or you can leverage Azure DNS private zones.

Note: When you are using External ASE, apps made in your ASE are registered with Azure DNS. There are no additional steps required in an External ASE for your apps to be publicly available.

In this blog post, I will implement with Azure DNS private zones, however I will start with steps in case you are managing your DNS server.

To configure DNS in your own DNS server
  1. Create a zone for intranet.appserviceenvironment.net (i.e < ASENAME >.appserviceenvironment.net)
  2. Create an A record in that zone that points * to the ILB IP address i.e 10.20.30.11
  3. Create an A record in that zone that points @ to the ILB IP address i.e 10.20.30.11
  4. Create a zone in .appserviceenvironment.net named scm
  5. Create an A record in the scm zone that points * to the ILB IP address i.e 10.20.30.11

If you are not sure about, how did I get IP and the ASE name, I would suggest to check this post.

To configure DNS in Azure DNS Private zones

First step will be to create a Azure DNS Private Zone with ASE domain name, to do that go to portal and search for Azure DNS Private zones and deploy a new zone with below details -

Resource Group : dns-sandbox

Name : intranet.appserviceenvironment.net Create Azure Private DNS Zone Once deployed, Click on + Record Set as shown below - Create Azure Private DNS Zone We will need to add below entires -

  • A record in that zone that points * to the ILB IP address i.e 10.20.30.11
  • A record in that zone that points @ to the ILB IP address i.e 10.20.30.11
  • A record in that zone that points *.scm to the ILB IP address i.e 10.20.30.11

Once done, it should look like this DNS records for ASE

Now, let’s try to do nslookup intranet.appserviceenvironment.net from either on-premise or azure vm nslookup failed Oops! it still fails. That’s because we missed to link this zone to virtual network. In our case we will link with hub-vnet. To do that Click on Virtual Network links from side bar and link it. Once completed, it should look like this Linked DNS Zone with hub-vent

Try to access the webapp from Azure VM and from on-prem (provided you have DNS forwarder set up correctly, in case you need help check this post) it started working!

WebApp is accessible using DNS Let’s see the certificate provided by Azure, seems working! WebApp is accessible using DNS

Also,check the scm site. SCM is accessible

All looks good finally. In the next post we will create a new webapp with Azure Sql and deploy it through Visual Studio.