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
Configure Azure DNS to host custom domains for your web apps and enable users to access them via personalized domain names. You can create Azure DNS records that allow users to access your web app using either `www.contoso.com` or `contoso.com` as a fully qualified domain name (FQDN).
18
18
19
-
To do this, you have to create three records:
19
+
To add a custom domain to your web app, you have to create three records:
20
20
21
-
* A root "A" record pointing to contoso.com
22
-
* A root "TXT" record for verification
23
-
* A "CNAME" record for the www name that points to the A record
21
+
* A root **`A`** record pointing to contoso.com
22
+
* A root **`TXT`** record for verification
23
+
* A **`CNAME`** record for the www name that points to the A record
24
24
25
25
In this tutorial, you learn how to:
26
26
@@ -54,7 +54,7 @@ If you don’t have an Azure subscription, create a [free account](https://azure
54
54
55
55
- Azure Cloud Shell or Azure PowerShell.
56
56
57
-
The steps in this tutorial run the Azure PowerShell cmdlets interactively in [Azure Cloud Shell](/azure/cloud-shell/overview). To run the commands in the Cloud Shell, select **Open Cloudshell** at the upper-right corner of a code block. Select **Copy** to copy the code and then paste it into Cloud Shell to run it. You can also run the Cloud Shell from within the Azure portal.
57
+
The steps in this tutorial run the Azure PowerShell cmdlets interactively in [Azure Cloud Shell](/azure/cloud-shell/overview). To run the commands in the Cloud Shell, select **Open Cloud shell** at the upper-right corner of a code block. Select **Copy** to copy the code and then paste it into Cloud Shell to run it. You can also run the Cloud Shell from within the Azure portal.
58
58
59
59
You can also [install Azure PowerShell locally](/powershell/azure/install-azure-powershell) to run the cmdlets. The steps in this article require Azure PowerShell module version 5.4.1 or later. Run `Get-Module -ListAvailable Az` to find your installed version. If you need to upgrade, see [Update the Azure PowerShell module](/powershell/azure/install-Az-ps#update-the-azure-powershell-module).
60
60
@@ -182,7 +182,7 @@ az network dns record-set a add-record \
182
182
App Services uses this record only at configuration time to verify that you own the custom domain. You can delete this TXT record after your custom domain is validated and configured in App Service.
183
183
184
184
> [!NOTE]
185
-
> If you want to verify the domain name, but not route production traffic to the web app, you only need to specify the TXT record for the verification step. Verification does not require an A or CNAME record in addition to the TXT record.
185
+
> If you want to verify the domain name, but not route production traffic to the web app, you only need to specify the TXT record for the verification step. Verification doesn't require an A or CNAME record in addition to the TXT record.
186
186
187
187
# [Portal](#tab/azure-portal)
188
188
@@ -238,7 +238,7 @@ az network dns record-set txt add-record \
238
238
239
239
## Create the CNAME record
240
240
241
-
If your domain is already managed by Azure DNS (see [DNS domain delegation](dns-domain-delegation.md)), you can use the following example to create a CNAME record for contoso.azurewebsites.net. The CNAME created in this example has a "time to live" of 600 seconds in DNS zone named "contoso.com" with the alias for the web app contoso.azurewebsites.net.
241
+
You can create a CNAME record for contoso.azurewebsites.net if Azure DNS already manages your domain (see [DNS domain delegation](dns-domain-delegation.md)). This example creates a CNAME record with a "time to live" of 600 seconds in the DNS zone named "contoso.com" and sets the alias to contoso.azurewebsites.net.
242
242
243
243
# [Portal](#tab/azure-portal)
244
244
@@ -292,7 +292,7 @@ az network dns record-set cname set-record \
292
292
293
293
## Test the new records
294
294
295
-
You can validate the records were created correctly by querying the "www.contoso.com" and "contoso.com" using nslookup, as shown below:
295
+
You can validate that you created the records correctly by querying "www.contoso.com" and "contoso.com" using nslookup, as shown in the following example:
296
296
297
297
```
298
298
PS C:\> nslookup
@@ -349,13 +349,13 @@ Add the custom host names to your web app:
349
349
| Setting | Value |
350
350
|---------|-------|
351
351
| Domain provider | Select **All other services**|
352
-
| TLS/SSL certificate | Select **None** (you can add a TLS/SSL certificate later) |
352
+
| TLS/SSL certificate | Select **None** (you can add an TLS/SSL certificate later) |
353
353
| TLS/SSL type | Select **SNI SSL**|
354
354
| Domain | Enter your domain name (for example, **contoso.com**) |
355
355
356
-
The domain validation will see the records you created in the previous steps.
356
+
The domain validation sees the records you created in the previous steps.
357
357
358
-
1. Select **Validate**. Azure will validate that the DNS records you created are properly configured.
358
+
1. Select **Validate**. Azure validates that the DNS records you created are properly configured.
359
359
360
360
1. Select **Add**.
361
361
@@ -396,7 +396,7 @@ az webapp config hostname add \
396
396
Open a browser and browse to `http://www.<your domain name>` and `http://<your domain name>`.
397
397
398
398
> [!NOTE]
399
-
> Make sure you include the `http://` prefix, otherwise your browser may attempt to predict a URL for you.
399
+
> Make sure you include the `http://` prefix. Your browser might attempt to predict a URL for you.
400
400
401
401
You should see the same page for both URLs. For example:
0 commit comments