Skip to content

Commit 36a6419

Browse files
committed
freshness review 3/24
1 parent 02b4782 commit 36a6419

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/frontdoor/apex-domain.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,13 +5,13 @@ services: frontdoor
55
author: johndowns
66
ms.service: frontdoor
77
ms.topic: conceptual
8-
ms.date: 02/07/2023
8+
ms.date: 03/31/2024
99
ms.author: jodowns
1010
---
1111

1212
# Apex domains in Azure Front Door
1313

14-
Apex domains, also called *root domains* or *naked domains*, are at the root of a DNS zone and don't contain subdomains. For example, `contoso.com` is an apex domain.
14+
Apex domains, also called *root domains*, or *naked domains*, are at the root of a Domain Name System (DNS) zone and don't contain subdomains. For example, `contoso.com` is an apex domain.
1515

1616
Azure Front Door supports apex domains, but requires special considerations. This article describes how apex domains work in Azure Front Door.
1717

@@ -26,9 +26,9 @@ Azure Front Door doesn't expose the frontend public IP address associated with y
2626
> [!WARNING]
2727
> Don't create an A record with the public IP address of your Azure Front Door endpoint. Your Azure Front Door endpoint's public IP address might change and we don't provide any guarantees that it will remain the same.
2828
29-
However, this problem can be resolved by using alias records in Azure DNS. Unlike CNAME records, alias records are created at the zone apex. You can point a zone apex record to an Azure Front Door profile that has public endpoints. Multiple application owners can point to the same Azure Front Door endpoint that's used for any other domain within their DNS zone. For example, `contoso.com` and `www.contoso.com` can point to the same Azure Front Door endpoint.
29+
However, this problem can be resolved by using alias records in Azure DNS. Unlike CNAME records, alias records are created at the zone apex. You can point a zone apex record to an Azure Front Door profile that has public endpoints. Multiple application owners can point to the same Azure Front Door endpoint used for any other domain within their DNS zone. For example, `contoso.com` and `www.contoso.com` can point to the same Azure Front Door endpoint.
3030

31-
Mapping your apex or root domain to your Azure Front Door profile uses *CNAME flattening*, sometimes called *DNS chasing*. CNAME flattening is where a DNS provider recursively resolves CNAME entries until it resolves an IP address. This functionality is supported by Azure DNS for Azure Front Door endpoints.
31+
Mapping your apex or root domain to your Azure Front Door profile uses *CNAME flattening*, sometimes called *DNS chasing*. CNAME flattening is where a DNS provider recursively resolves CNAME entries until it resolves an IP address. Azure DNS supports this functionality for Azure Front Door endpoints.
3232

3333
> [!NOTE]
3434
> Other DNS providers support CNAME flattening or DNS chasing. However, Azure Front Door recommends using Azure DNS for hosting your apex domains.
@@ -40,14 +40,14 @@ To validate a domain, you need to create a DNS TXT record. The name of the TXT r
4040
For example, suppose you want to use the apex domain `contoso.com` with Azure Front Door. First, you should add the domain to your Azure Front Door profile, and note the TXT record value that you need to use. Then, you should configure a DNS record with the following properties:
4141

4242
| Property | Value |
43-
|-|-|
43+
|--|--|
4444
| Record name | `_dnsauth` |
4545
| Record value | *use the value provided by Azure Front Door* |
4646
| Time to live (TTL) | 1 hour |
4747

48-
## Azure Front Door-managed TLS certificate rotation
48+
## Azure Front Door-managed Transport Layer Security (TLS) certificate rotation
4949

50-
When you use an Azure Front Door-managed certificate, Azure Front Door attempts to automatically rotate (renew) the certificate. Before it does so, Azure Front Door checks whether the DNS CNAME record is still pointed to the Azure Front Door endpoint. Apex domains don't have a CNAME record pointing to an Azure Front Door endpoint, so the auto-rotation for managed certificate fails until the domain ownership is revalidated.
50+
When you use an Azure Front Door-managed certificate, Azure Front Door attempts to automatically rotate (renew) the certificate. Before it does so, Azure Front Door checks whether the DNS CNAME record is still pointed to the Azure Front Door endpoint. Apex domains don't have a CNAME record pointing to an Azure Front Door endpoint, so the autorotation for managed certificate fails until the domain ownership is revalidated.
5151

5252
Select the **Pending revalidation** link and then select the **Regenerate** button to regenerate the TXT token. After that, add the TXT token to the DNS provider settings.
5353

0 commit comments

Comments
 (0)