Skip to content

Commit 6ddb242

Browse files
authored
Merge pull request #97730 from domccune/patch-2
Update front-door-wildcard-domain.md
2 parents 29f40a0 + a60b1e7 commit 6ddb242

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/frontdoor/front-door-wildcard-domain.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ For accepting HTTPS traffic on your wildcard domain, you must enable HTTPS on th
5454

5555
## Adding wildcard domains
5656

57-
You can add a wildcard domain under the section for front-end hosts or domains. Similar to subdomains, Azure Front Door (classic) validates that there's CNAME record mapping for your wildcard domain. This DNS mapping can be a direct CNAME record mapping like `*.contoso.com` mapped to `contoso.azurefd.net`. Or you can use afdverify temporary mapping. For example, `afdverify.contoso.com` mapped to `afdverify.contoso.azurefd.net` validates the CNAME record map for the wildcard.
57+
You can add a wildcard domain under the section for front-end hosts or domains. Similar to subdomains, Azure Front Door (classic) validates that there's CNAME record mapping for your wildcard domain. This DNS mapping can be a direct CNAME record mapping like `*.contoso.com` mapped to `endpoint.azurefd.net`. Or you can use afdverify temporary mapping. For example, `afdverify.contoso.com` mapped to `afdverify.endpoint.azurefd.net` validates the CNAME record map for the wildcard.
5858

5959
> [!NOTE]
6060
> Azure DNS supports wildcard records.

0 commit comments

Comments
 (0)