You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/app-service/environment/using-an-ase.md
+16-9Lines changed: 16 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: ccompy
5
5
6
6
ms.assetid: a22450c4-9b8b-41d4-9568-c4646f4cf66b
7
7
ms.topic: article
8
-
ms.date: 3/26/2020
8
+
ms.date: 5/10/2020
9
9
ms.author: ccompy
10
10
ms.custom: seodec18
11
11
---
@@ -117,15 +117,22 @@ The SCM URL is used to access the Kudu console or for publishing your app by usi
117
117
118
118
### DNS configuration
119
119
120
-
When you use an External ASE, apps made in your ASE are registered with Azure DNS. With an ILB ASE, you must manage your own DNS.
120
+
When you use an External ASE, apps made in your ASE are registered with Azure DNS. There are no additional steps then in an External ASE for your apps to be publicly available. With an ILB ASE, you must manage your own DNS. You can do this in your own DNS server or with Azure DNS private zones.
121
121
122
-
To configure DNS with your ILB ASE:
122
+
To configure DNS in your own DNS server with your ILB ASE:
123
123
124
-
create a zone for <ASE name>.appserviceenvironment.net
125
-
create an A record in that zone that points * to the ILB IP address
126
-
create an A record in that zone that points @ to the ILB IP address
127
-
create a zone in <ASE name>.appserviceenvironment.net named scm
128
-
create an A record in the scm zone that points * to the ILB IP address
124
+
1. create a zone for <ASEname>.appserviceenvironment.net
125
+
1. create an A record in that zone that points * to the ILB IP address
126
+
1. create an A record in that zone that points @ to the ILB IP address
127
+
1. create a zone in <ASEname>.appserviceenvironment.net named scm
128
+
1. create an A record in the scm zone that points * to the ILB IP address
129
+
130
+
To configure DNS in Azure DNS Private zones:
131
+
132
+
1. create an Azure DNS private zone named <ASEname>.appserviceenvironment.net
133
+
1. create an A record in that zone that points * to the ILB IP address
134
+
1. create an A record in that zone that points @ to the ILB IP address
135
+
1. create an A record in that zone that points *.scm to the ILB IP address
129
136
130
137
The DNS settings for your ASE default domain suffix do not restrict your apps to only being accessible by those names. You can set a custom domain name without any validation on your apps in an ILB ASE. If you then want to create a zone named *contoso.net*, you could do so and point it to the ILB IP address. The custom domain name works for app requests but doesn't for the scm site. The scm site is only available at *<appname>.scm.<asename>.appserviceenvironment.net*.
131
138
@@ -151,7 +158,7 @@ The publishing endpoints for apps in an ILB ASE use the domain that the ILB ASE
151
158
152
159
## Storage
153
160
154
-
An ASE has 1 TB of storage for all the apps in the ASE. An App Service plan in the Isolated pricing SKU has a limit of 250 GB by default. If you have five or more App Service plans, be careful not to exceed the 1-TB limit of the ASE. If you need more than the 250-GB limit in one App Service plan, contact support to adjust the App Service plan limit to a maximum of 1 TB. When the plan limit is adjusted, there's still a limit of 1 TB across all the App Service plans in the ASE.
161
+
An ASE has 1 TB of storage for all the apps in the ASE. An App Service plan in the Isolated pricing SKU has a limit of 250 GB. In an ASE, 250 GB of storage is added per App Service plan up to the 1TB limit. You can have more App Service plans than just four, but there is no more storage added beyond the 1 TB limit.
0 commit comments