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-wildcard-domain.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.author: sharadag
14
14
15
15
# Wildcard domains
16
16
17
-
Other than apex domains and subdomains, you can map a wildcard domain name to your list of frontend hosts or custom domains in your Azure Front Door Service profile. Having wildcard domains in your Azure Front Door Service configuration simplifies traffic routing behavior for multiple subdomains for an API, application, or website from the same routing rule. You don't need to modify the configuration to add or specify each subdomain separately. As an example, you can define the routing for `customer1.contoso.com`, `customer2.contoso.com`, and `customerN.contoso.com` by using the same routing rule and adding the wildcard domain `*.contoso.com`.
17
+
Other than apex domains and subdomains, you can map a wildcard domain name to your list of front-end hosts or custom domains in your Azure Front Door Service profile. Having wildcard domains in your Azure Front Door Service configuration simplifies traffic routing behavior for multiple subdomains for an API, application, or website from the same routing rule. You don't need to modify the configuration to add or specify each subdomain separately. As an example, you can define the routing for `customer1.contoso.com`, `customer2.contoso.com`, and `customerN.contoso.com` by using the same routing rule and adding the wildcard domain `*.contoso.com`.
18
18
19
19
Key scenarios that are improved with support for wildcard domains include:
20
20
@@ -26,12 +26,12 @@ Key scenarios that are improved with support for wildcard domains include:
26
26
27
27
## Adding wildcard domains
28
28
29
-
You can add a wildcard domain under the section for frontend hosts or domains. Similar to subdomains, Azure Front Door Service validates that there is 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.
29
+
You can add a wildcard domain under the section for front-end hosts or domains. Similar to subdomains, Azure Front Door Service validates that there is 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.
30
30
31
31
> [!NOTE]
32
32
> Azure DNS supports wildcard records.
33
33
34
-
You can add as many single-level subdomains of the wildcard domain in frontend hosts, up to the limit of the frontend hosts. This functionality might be required for:
34
+
You can add as many single-level subdomains of the wildcard domain in front-end hosts, up to the limit of the front-end hosts. This functionality might be required for:
35
35
36
36
- Defining a different route for a subdomain than the rest of the domains (from the wildcard domain).
37
37
@@ -52,7 +52,7 @@ For accepting HTTPS traffic on your wildcard domain, you must enable HTTPS on th
52
52
> [!NOTE]
53
53
> Currently, only using your own custom SSL certificate option is available for enabling HTTPS for wildcard domains. Azure Front Door Service managed certificates can't be used for wildcard domains.
54
54
55
-
You can choose to use the same wildcard certificate from your Azure Key Vault or from Azure Front Door Service managed certificates for subdomains.
55
+
You can choose to use the same wildcard certificate from Azure Key Vault or from Azure Front Door Service managed certificates for subdomains.
56
56
57
57
If a subdomain is added for a wildcard domain that already has a certificate associated with it, then HTTPS for the subdomain can't be disabled. The subdomain uses the certificate binding for the wildcard domain, unless a different Key Vault or Azure Front Door Service managed certificate overrides it.
58
58
@@ -64,13 +64,13 @@ If you don't want a WAF policy to run for a subdomain, you can create a blank WA
64
64
65
65
## Routing rules
66
66
67
-
When configuring a routing rule, you can select a wildcard domain as a frontend host. You can also have different route behavior for wildcard domains and subdomains. As described in [How Front Door does route matching](front-door-route-matching.md), the most specific match for the domain across different routing rules is chosen at runtime.
67
+
When configuring a routing rule, you can select a wildcard domain as a front-end host. You can also have different route behavior for wildcard domains and subdomains. As described in [How Azure Front Door Service does route matching](front-door-route-matching.md), the most specific match for the domain across different routing rules is chosen at runtime.
68
68
69
69
> [!IMPORTANT]
70
-
> You must have matching path patterns across your routing rules, or your clients will see failures. For example, you have two routing rules like Route 1 (`*.foo.com/*` mapped to Backend Pool A) and Route 2 (`bar.foo.com/somePath/*` mapped to Backend Pool B). Then, a request arrives for `bar.foo.com/anotherPath/*`. Azure Front Door Service selects Route 2 based on a more specific domain match, only to find no matching path patterns across the routes.
70
+
> You must have matching path patterns across your routing rules, or your clients will see failures. For example, you have two routing rules like Route 1 (`*.foo.com/*` mapped to back-end pool A) and Route 2 (`bar.foo.com/somePath/*` mapped to back-end pool B). Then, a request arrives for `bar.foo.com/anotherPath/*`. Azure Front Door Service selects Route 2 based on a more specific domain match, only to find no matching path patterns across the routes.
71
71
72
72
## Next steps
73
73
74
-
- Learn how to [create a Front Door profile](quickstart-create-front-door.md).
75
-
- Learn how to [add a custom domain on Front Door](front-door-custom-domain.md).
74
+
- Learn how to [create an Azure Front Door Service profile](quickstart-create-front-door.md).
75
+
- Learn how to [add a custom domain on Azure Front Door Service](front-door-custom-domain.md).
76
76
- Learn how to [enable HTTPS on a custom domain](front-door-custom-domain-https.md).
0 commit comments