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/app-service-web-tutorial-custom-domain.md
+29-46Lines changed: 29 additions & 46 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,70 +64,53 @@ The DNS record type you need to add with your domain provider depends on the dom
64
64
65
65
## 2. Create the DNS records
66
66
67
-
1. Sign in to the website of your domain provider.
67
+
[!INCLUDE [Access DNS records with domain provider](../../includes/app-service-web-access-dns-records.md)]
68
68
69
-
You can use Azure DNS to manage DNS records for your domain and configure a custom DNS name for Azure App Service. For more information, see [Tutorial: Host your domain in Azure DNS](../dns/dns-delegate-domain-azure-dns.md).
69
+
Select the type of record to create and follow the instructions. You can use either a [CNAME record](https://en.wikipedia.org/wiki/CNAME_record) or an [A record](https://en.wikipedia.org/wiki/List_of_DNS_record_types#A) to map a custom DNS name to App Service.
70
70
71
-
1. Find the page for managing DNS records.
71
+
# [A](#tab/a)
72
72
73
-
Every domain provider has its own DNS records interface, so consult the provider's documentation. Look for areas of the site labeled **Domain Name**, **DNS**, or **Name Server Management**.
74
-
75
-
Often, you can find the DNS records page by viewing your account information and then looking for a link such as **My domains**. Go to that page, and then look for a link that's named something like **Zone file**, **DNS Records**, or **Advanced configuration**.
73
+
- For a root domain like `contoso.com`, create two records according to the following table:
74
+
75
+
| Record type | Host | Value | Comments |
76
+
| - | - | - |
77
+
| A | `@` | The app's IP address shown in the **Add custom domain** dialog. | The domain mapping itself (`@` typically represents the root domain). |
78
+
| TXT | `asuid` | The domain verification ID shown in the **Add custom domain** dialog. | For root domain, App Service accesses `asuid` TXT record to verify your ownership of the custom domain. |
76
79
77
-
The following screenshot is an example of a DNS records page:
80
+
78
81
79
-
82
+
- To map a subdomain like `www.contoso.com` with an A record instead of a recommended CNAME record, your A record and TXT record should look like the following table instead:
80
83
81
-
1. Select **Add** or the appropriate widget to create a record.
84
+
|Record type|Host|Value| Comments |
85
+
|--- |--- |--- |--- |
86
+
|A|\<subdomain\> (for example, www)|IP address shown in the **Add custom domain** dialog.||
87
+
|TXT|asuid.\<subdomain\> (for example, asuid.www)|The domain verification ID shown in the **Add custom domain** dialog.||
82
88
83
-
1. Select the type of record to create and follow the instructions. You can use either a [CNAME record](https://en.wikipedia.org/wiki/CNAME_record) or an [A record](https://en.wikipedia.org/wiki/List_of_DNS_record_types#A) to map a custom DNS name to App Service.
89
+
84
90
85
-
# [A](#tab/a)
91
+
# [CNAME](#tab/cname)
86
92
87
-
-For a root domain like `contoso.com`, create two records according to the following table:
93
+
For a subdomain like `www` in `www.contoso.com`, create two records according to the following table:
88
94
89
95
| Record type | Host | Value | Comments |
90
96
| - | - | - |
91
-
| A |`@`| The app's IP address shown in the **Add custom domain** dialog. | The domain mapping itself (`@` typically represents the root domain). |
92
-
| TXT |`asuid`| The domain verification ID shown in the **Add custom domain** dialog. | For root domain, App Service accesses `asuid` TXT record to verify your ownership of the custom domain. |
93
-
94
-
95
-
96
-
- To map a subdomain like `www.contoso.com` with an A record instead of a recommended CNAME record, your A record and TXT record should look like the following table instead:
97
-
98
-
|Record type|Host|Value| Comments |
99
-
|--- |--- |--- |--- |
100
-
|A|\<subdomain\> (for example, www)|IP address shown in the **Add custom domain** dialog.||
101
-
|TXT|asuid.\<subdomain\> (for example, asuid.www)|The domain verification ID shown in the **Add custom domain** dialog.||
102
-
103
-
104
-
105
-
# [CNAME](#tab/cname)
106
-
107
-
For a subdomain like `www` in `www.contoso.com`, create two records according to the following table:
97
+
| CNAME | `<subdomain>` (for example, `www`) | `<app-name>.azurewebsites.net` | The domain mapping itself. |
98
+
| TXT | `asuid.<subdomain>` (for example, `asuid.www`) | The verification ID shown in the **Add custom domain** dialog. | App Service accesses the `asuid.<subdomain>` TXT record to verify your ownership of the custom domain. |
108
99
109
-
| Record type | Host | Value | Comments |
110
-
| - | - | - |
111
-
| CNAME |`<subdomain>` (for example, `www`) |`<app-name>.azurewebsites.net`| The domain mapping itself. |
112
-
| TXT |`asuid.<subdomain>` (for example, `asuid.www`) | The verification ID shown in the **Add custom domain** dialog. | App Service accesses the `asuid.<subdomain>` TXT record to verify your ownership of the custom domain. |
100
+
113
101
114
-
115
-
116
-
# [Wildcard (CNAME)](#tab/wildcard)
102
+
# [Wildcard (CNAME)](#tab/wildcard)
117
103
118
-
For a wildcard name like `*` in `*.contoso.com`, create two records according to the following table:
104
+
For a wildcard name like `*` in `*.contoso.com`, create two records according to the following table:
119
105
120
-
| Record type | Host | Value | Comments |
121
-
| - | - | - |
122
-
| CNAME |`*`|`<app-name>.azurewebsites.net`| The domain mapping itself. |
123
-
| TXT |`asuid`| The domain verification ID shown in the **Add custom domain** dialog. | App Service accesses the `asuid` TXT record to verify your ownership of the custom domain. |
| TXT | `asuid` | The domain verification ID shown in the **Add custom domain** dialog. | App Service accesses the `asuid` TXT record to verify your ownership of the custom domain. |
124
110
125
-
126
-
127
-
-----
111
+
128
112
129
-
> [!NOTE]
130
-
> For certain providers, such as GoDaddy, changes to DNS records don't become effective until you select a separate **Save Changes** link.
Copy file name to clipboardExpand all lines: articles/app-service/manage-custom-dns-migrate-domain.md
+56-49Lines changed: 56 additions & 49 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ tags: top-support-issue
5
5
6
6
ms.assetid: 10da5b8a-1823-41a3-a2ff-a0717c2b5c2d
7
7
ms.topic: article
8
-
ms.date: 08/25/2020
8
+
ms.date: 01/13/2023
9
9
ms.custom: seodec18
10
10
11
11
---
@@ -21,90 +21,94 @@ If you're not worried about downtime in DNS resolution, see [Map an existing cus
21
21
22
22
To complete this how-to, [make sure that your App Service app is not in FREE tier](manage-scale-up.md#scale-up-your-pricing-tier).
23
23
24
-
## Bind the domain name preemptively
24
+
## 1. Get a domain verification ID
25
25
26
26
When you bind a custom domain preemptively, you accomplish both of the following before making any changes to
27
27
your existing DNS records:
28
28
29
-
- Verify domain ownership
30
-
- Enable the domain name for your app
29
+
- Verify domain ownership by adding a domain verification ID with your domain provider.
30
+
- Enable the domain name in your App service app.
31
31
32
32
When you finally migrate your custom DNS name from the old site to the App Service app, there will be no downtime in DNS resolution.
33
33
34
-
[!INCLUDE [Access DNS records with domain provider](../../includes/app-service-web-access-dns-records.md)]
34
+
1. In the [Azure portal](https://portal.azure.com), open the management page of the App Service app.
35
35
36
-
### Get domain verification ID
36
+
1. In the left pane of your app page, select **Custom domains**.
37
+
1. Copy the ID in the **Custom Domain Verification ID** box in the **Custom Domains** page for the next steps.
37
38
38
-
Get the domain verification ID for you app by following the steps at [Configure a custom domain](app-service-web-tutorial-custom-domain.md#1-configure-a-custom-domain).
39
+
:::image type="content" source="./media/manage-custom-dns-migrate-domain/get-domain-verification-id.png" alt-text="Screenshot that shows the ID in the Custom Domain Verification ID box.":::
39
40
40
-
### Create domain verification record
41
+
##2. Create the DNS records
41
42
42
-
To verify domain ownership, add a TXT record for domain verification. The hostname for the TXT record depends on the type of DNS record type you want to map. See the following table (`@` typically represents the root domain):
43
+
[!INCLUDE [Access DNS records with domain provider](../../includes/app-service-web-access-dns-records.md)]
43
44
44
-
| DNS record example | TXT Host | TXT Value |
45
-
| - | - | - |
46
-
|\@ (root) |_asuid_| Domain verification ID shown in the **Add custom domain** dialog. |
47
-
| www (sub) |_asuid.www_| Domain verification ID shown in the **Add custom domain** dialog. |
48
-
|\* (wildcard) |_asuid_| Domain verification ID shown in the **Add custom domain** dialog. |
45
+
Add a TXT record for domain verification. The hostname for the TXT record depends on the type of DNS record type you want to map. See the following table (`@` typically represents the root domain):
49
46
50
-
In your DNS records page, note the record type of the DNS name you want to migrate. App Service supports mappings from CNAME and A records.
47
+
| DNS record example | TXT Host | TXT Value |
48
+
| - | - | - |
49
+
| \@ (root) | _asuid_ | Domain verification ID shown in the **Custom domains** management page. |
50
+
| www (sub) | _asuid.www_ | Domain verification ID shown in the **Custom domains** management page. |
51
+
| \* (wildcard) | _asuid_ | Domain verification ID shown in the **Custom domains** management page. |
52
+
53
+
> [!NOTE]
54
+
> Wildcard `*` records won't validate subdomains with an existing CNAME's record. You may need to explicitly create a TXT record for each subdomain.
55
+
56
+
## 3. Enable the domain for your app
51
57
52
-
> [!NOTE]
53
-
> Wildcard `*` records won't validate subdomains with an existing CNAME's record. You may need to explicitly create a TXT record for each subdomain.
58
+
1. Back in the **Custom domains** page, select **Add custom domain**.
54
59
55
-
### Enable the domain for your app
60
+
:::image type="content" source="./media/app-service-web-tutorial-custom-domain/add-custom-domain.png" alt-text="A screenshot showing how to open the Add custom domain dialog.":::
56
61
57
-
1.In the [Azure portal](https://portal.azure.com), in the left navigation of the app page, select **Custom domains**.
62
+
1.For **Domain provider**, select **All other domain services** to configure a third-party domain.
1. For **TLS/SSL certificate**, select **App Service Managed Certificate** if your app is in **Basic** tier or higher. If you want to remain in **Shared** tier, select **Add certificate later**.
60
65
61
-
1.In the **Custom domains** page, select **Add custom domain**.
66
+
1.For **TLS/SSL type**, select the binding type you want.
1. Type the fully qualified domain name you want to migrate, that corresponds to the TXT record you create, such as `contoso.com`, `www.contoso.com`, or `*.contoso.com`. Select **Validate**.
70
+
1. Type the fully qualified domain name you want to migrate, that corresponds to the TXT record you created, such as `contoso.com`, `www.contoso.com`, or `*.contoso.com`.
66
71
67
-
The **Add customdomain** button is activated.
72
+
:::image type="content" source="./media/app-service-web-tutorial-custom-domain/add-custom-domain.png" alt-text="Screenshot that shows how to open the Add custom domain dialog.":::
68
73
69
-
1.Make sure that **Hostname record type** is set to the DNS record type you want to migrate. Select **Add hostname**.
74
+
1.Select **Validate**. Although the dialog shows two records you need for the custom domain to be functional for your app, the validation passes with just the domain verification ID (the TXT record).
70
75
71
-
76
+
:::image type="content" source="./media/app-service-web-tutorial-custom-domain/configure-custom-domain-validate.png" alt-text="A screenshot showing how to validate your DNS record settings in the Add a custom domain dialog.":::
72
77
73
-
It might take some time for the new hostname to be reflected in the app's**Custom domains** page. Try refreshing the browser to update the data.
78
+
1. If the **Domain validation** section shows green check marks, then you've configured the domain verification ID correctly. Select**Add**. If it shows any red X, fix any errors in your domain provider's website.
74
79
75
-
80
+
:::image type="content" source="./media/app-service-web-tutorial-custom-domain/configure-custom-domain-add.png" alt-text="A screenshot showing the Add button activated after validation.":::
76
81
77
-
Your custom DNS name is now enabled in your Azure app.
82
+
1. You should see the custom domain added to the list. You may also see a red X with **No binding**.
78
83
79
-
## Remap the active DNS name
84
+
If you selected **App Service Managed Certificate** earlier, wait a few minutes for App Service to create the managed certificate for your custom domain. When the process is complete, the red X becomes a green check mark with **Secured**. If you selected **Add certificate later**, this red X will remain until you [add a private certificate for the domain](configure-ssl-certificate.md) and [configure the binding](configure-ssl-bindings.md).
80
85
81
-
The only thing left to do is remapping your active DNS record to point to App Service. Right now, it still points to your old site.
86
+
:::image type="content" source="./media/app-service-web-tutorial-custom-domain/add-custom-domain-complete.png" alt-text="A screenshot showing the custom domains page with the new secured custom domain.":::
82
87
88
+
> [!NOTE]
89
+
> Unless you configure a certificate binding for your custom domain, Any HTTPS request from a browser to the domain will receive an error or warning, depending on the browser.
90
+
83
91
<aname="info"></a>
84
92
85
-
### Copy the app's IP address (A record only)
86
-
87
-
If you are remapping a CNAME record, skip this section.
88
-
89
-
To remap an A record, you need the App Service app's external IP address, which is shown in the **Custom domains** page.
93
+
## 4. Remap the active DNS name
90
94
91
-
In the **Custom domains** page, copy the app's IP address.
92
-
93
-
94
-
95
-
### Update the DNS record
95
+
The only thing left to do is remapping your active DNS record to point to App Service. Right now, it still points to your old site.
96
96
97
-
Back in the DNS records page of your domain provider, select the DNS record to remap.
97
+
1. (A record only) You need the App Service app's external IP address. In the **Custom domains** page, copy the app's IP address.
98
98
99
-
For the `contoso.com` root domain example, remap the A or CNAME record like the examples in the following table:
99
+
:::image type="content" source="./media/app-service-web-tutorial-custom-domain/mapping-information.png" alt-text="A screenshot showing how to copy the App Service app's exterinal IP address.":::
100
100
101
-
| FQDN example | Record type | Host | Value |
102
-
| - | - | - | - |
103
-
| contoso.com (root) | A |`@`| IP address from [Copy the app's IP address](#info)|
Copy file name to clipboardExpand all lines: includes/app-service-web-access-dns-records-no-h.md
+8-9Lines changed: 8 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,26 +2,25 @@
2
2
author: cephalin
3
3
ms.service: app-service
4
4
ms.topic: include
5
-
ms.date: 11/03/2016
5
+
ms.date: 01/16/2023
6
6
ms.author: cephalin
7
7
ms.subservice: web-apps
8
8
---
9
-
> [!NOTE]
10
-
> You can use Azure DNS to configure a custom DNS name for Azure App Service. For more information, see [Use Azure DNS to provide custom domain settings for an Azure service](../articles/dns/dns-custom-domain.md#app-service-web-apps).
11
-
>
12
-
>
13
-
14
9
1. Sign in to the website of your domain provider.
15
10
16
-
1. Find the page for managing DNS records. Every domain provider has its own DNS records interface, so consult the provider's documentation. Look for areas of the site labeled **Domain Name**, **DNS**, or **Name Server Management**.
11
+
You can use Azure DNS to manage DNS records for your domain and configure a custom DNS name for Azure App Service. For more information, see [Tutorial: Host your domain in Azure DNS](../dns/dns-delegate-domain-azure-dns.md).
12
+
13
+
1. Find the page for managing DNS records.
17
14
18
-
Often, you can find the DNS records page by viewing your account information and then looking for a link such as **My domains**. Go to that page, and then look for a link that's named something like **Zone file**, **DNS Records**, or **Advanced configuration**.
15
+
Every domain provider has its own DNS records interface, so consult the provider's documentation. Look for areas of the site labeled **Domain Name**, **DNS**, or **Name Server Management**.
16
+
17
+
Often, you can find the DNS records page by viewing your account information and then looking for a link such as **My domains**. Go to that page, and then look for a link that's named something like **Zone file**, **DNS Records**, or **Advanced configuration**.
19
18
20
19
The following screenshot is an example of a DNS records page:
21
20
22
21
23
22
24
-
1.In the example screenshot, select **Add**to create a record. Some providers have different links to add different record types. Again, consult the provider's documentation.
23
+
1.Select **Add**or the appropriate widget to create a record.
25
24
26
25
> [!NOTE]
27
26
> For certain providers, such as GoDaddy, changes to DNS records don't become effective until you select a separate **Save Changes** link.
0 commit comments