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/frontdoor/front-door-custom-domain.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: frontdoor
5
5
author: duongau
6
6
ms.service: azure-frontdoor
7
7
ms.topic: how-to
8
-
ms.date: 04/04/2023
8
+
ms.date: 08/12/2024
9
9
ms.author: duau
10
10
#Customer intent: As a website owner, I want to add a custom domain to my Front Door configuration so that my users can use my custom domain to access my content.
11
11
---
@@ -40,7 +40,7 @@ A custom domain can only be associated with one Front Door profile at a time. Ho
40
40
41
41
## Map the temporary afdverify subdomain
42
42
43
-
When you map an existing domain that is in production, there are things consider. While you're registering your custom domain in the Azure portal, a brief period of downtime for the domain may occur. To avoid interruption of web traffic, map your custom domain to your Front Door default frontend host with the Azure afdverify subdomain first to create a temporary CNAME mapping. Your users can access your domain without interruption when the DNS mapping occurs.
43
+
When you map an existing domain that is in production, there are things consider. While you're registering your custom domain in the Azure portal, a brief period of downtime for the domain might occur. To avoid interruption of web traffic, map your custom domain to your Front Door default frontend host with the Azure afdverify subdomain first to create a temporary CNAME mapping. Your users can access your domain without interruption when the DNS mapping occurs.
44
44
45
45
If you're using your custom domain for the first time with no production traffic, you can directly map your custom domain to your Front Door. You can skip ahead to [Map the permanent custom domain](#map-the-permanent-custom-domain).
46
46
@@ -50,7 +50,7 @@ To create a CNAME record with the afdverify subdomain:
50
50
51
51
2. Find the page for managing DNS records by consulting the provider's documentation or searching for areas of the web site labeled **Domain Name**, **DNS**, or **Name server management**.
52
52
53
-
3. Create a CNAME record entry for your custom domain and complete the fields as shown in the following table (field names may vary):
53
+
3. Create a CNAME record entry for your custom domain and complete the fields as shown in the following table (field names might vary):
@@ -78,7 +78,7 @@ For example, the procedure for the GoDaddy domain registrar is as follows:
78
78
79
79
- Type: Leave *CNAME* selected.
80
80
81
-
- Host: Enter the subdomain of your custom domain to use, including the afdverify subdomain name. For example, afdverify.www.
81
+
- Host: Enter the subdomain of your custom domain for use, including the afdverify subdomain name. For example, afdverify.www.
82
82
83
83
- Points to: Enter the host name of your default Front Door frontend host, including the afdverify subdomain name. For example, afdverify.contoso-frontend.azurefd.net.
84
84
@@ -91,7 +91,7 @@ For example, the procedure for the GoDaddy domain registrar is as follows:
91
91
92
92
## Associate the custom domain with your Front Door
93
93
94
-
After you've registered your custom domain, you can then add it to your Front Door.
94
+
After you register your custom domain, you can then add it to your Front Door.
95
95
96
96
1. Sign in to the [Azure portal](https://portal.azure.com/) and browse to the Front Door containing the frontend host that you want to map to a custom domain.
97
97
@@ -112,22 +112,22 @@ After you've registered your custom domain, you can then add it to your Front Do
112
112
113
113
## Verify the custom domain
114
114
115
-
After you've completed the registration of your custom domain, verify that the custom domain references your default Front Door frontend host.
115
+
After you complete the registration of your custom domain, verify that the custom domain references your default Front Door frontend host.
116
116
117
117
In your browser, navigate to the address of the file by using the custom domain. For example, if your custom domain is robotics.contoso.com, the URL to the cached file should be similar to the following URL: http:\//robotics.contoso.com/my-public-container/my-file.jpg. Verify that the result is that same as when you access the Front Door directly at *<Front Door host>*.azurefd.net.
118
118
119
119
120
120
## Map the permanent custom domain
121
121
122
-
If you've verified that the afdverify subdomain has been successfully mapped to your Front Door, you can then map the custom domain directly to your default Front Door frontend host.
122
+
To proceed with mapping the custom domain directly to your default Front Door frontend host, you need to ensure that the afdverify subdomain was successfully mapped to your Front Door. Once verified, you can proceed with mapping the custom domain.
123
123
124
124
To create a CNAME record for your custom domain:
125
125
126
126
1. Sign in to the web site of the domain provider for your custom domain.
127
127
128
128
2. Find the page for managing DNS records by consulting the provider's documentation or searching for areas of the web site labeled **Domain Name**, **DNS**, or **Name Server Management**.
129
129
130
-
3. Create a CNAME record entry for your custom domain and complete the fields as shown in the following table (field names may vary):
130
+
3. Create a CNAME record entry for your custom domain and complete the fields as shown in the following table (field names might vary):
@@ -141,7 +141,7 @@ To create a CNAME record for your custom domain:
141
141
142
142
4. Save your changes.
143
143
144
-
5. If you're previously created a temporary afdverify subdomain CNAME record, delete it.
144
+
5. If you previously created a temporary afdverify subdomain CNAME record, delete it.
145
145
146
146
6. If you're using this custom domain in production for the first time, follow the steps for [Associate the custom domain with your Front Door](#associate-the-custom-domain-with-your-front-door) and [Verify the custom domain](#verify-the-custom-domain).
147
147
@@ -177,7 +177,7 @@ For example, the procedure for the GoDaddy domain registrar is as follows:
177
177
178
178
In the preceding steps, you added a custom domain to a Front Door. If you no longer want to associate your Front Door with a custom domain, you can remove the custom domain by doing these steps:
179
179
180
-
1. Go to your DNS provider, delete the CNAME record for the custom domain or update the CNAME record for the custom domain to a non Front Door endpoint.
180
+
1. Go to your DNS provider, delete the CNAME record for the custom domain, or update the CNAME record for the custom domain to a non Front Door endpoint.
181
181
182
182
> [!Important]
183
183
> To prevent dangling DNS entries and the security risks they create, starting from April 9th 2021, Azure Front Door requires removal of the CNAME records to Front Door endpoints before the resources can be deleted. Resources include Front Door custom domains, Front Door endpoints or Azure resource groups that has Front Door custom domain(s) enabled.
0 commit comments