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/static-web-apps/apex-domain-azure-dns.md
+7-63Lines changed: 7 additions & 63 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,77 +25,21 @@ The following procedure requires you to copy settings from an Azure DNS zone you
25
25
26
26
1. Under *Settings*, select **Custom domains**.
27
27
28
-
1. Select **+ Add**, and then select **Custom Domain on Azure DNS** from the dropdown menu.
28
+
1. Select **+ Add**, and then select **Custom Domain on Azure DNS** from the drop-down menu.
29
29
30
-
1.In the *Enter domain* tab, enter your apex domain name.
30
+
1.Select your apex domain name from the *DNS zone* drop-down.
31
31
32
-
For instance, if your domain name is `example.com`, enter `example.com` into this box (without any subdomains).
32
+
If this list is empty, [create a public zone in Azure DNS](../dns/dns-getstarted-portal.md).
33
33
34
-
1. Select **Next**.
34
+
1. Select **Add**.
35
35
36
-
1. In the *Validate + Configure* tab, enter the following values.
37
-
38
-
| Setting | Value |
39
-
|---|---|
40
-
| Domain name | This value should match the domain name you entered in the previous step. |
41
-
| Hostname record type | Select **TXT**. |
42
-
43
-
1. Select **Generate code**.
44
-
45
-
Wait as the code is generated. It make take a minute or so to complete.
46
-
47
-
1. Once the `TXT` record value is generated, **copy** (next to the generated value) the code to the clipboard.
36
+
Wait as the DNS record and custom domain records are added for your static web app. It may take a minute or so to complete.
48
37
49
38
1. Select **Close**.
50
39
51
-
1. Go to your Azure DNS zone instance.
52
-
53
-
1. Select **+ Record set**.
54
-
55
-
1. Enter the following values in the *Add record set* window.
56
-
57
-
| Setting | Property |
58
-
|---|---|
59
-
| Name | Enter **@**|
60
-
| Type | Select **TXT - Text record type**. |
61
-
| TTL | Keep default value. |
62
-
| TTL unit | Keep default value. |
63
-
| Value | Paste in the `TXT` record value in your clipboard from your static web app. |
64
-
65
-
1. Select **OK**.
66
-
67
-
1. Return to your static web app in the Azure portal.
68
-
69
-
1. Under *Settings*, select **Custom domains**.
70
-
71
-
Observe the *Status* for the row of your apex domain. Once the validation is complete, then your apex domain is publicly available.
72
-
73
-
While this validation is running, create an ALIAS record to finalize the configuration.
74
-
75
-
## Set up ALIAS record
76
-
77
-
1. Return to the Azure DNS zone in the Azure portal.
78
-
79
-
2. Select **+ Record set**.
80
-
81
-
3. Enter the following values in the *Add record set* window.
82
-
83
-
| Setting | Property |
84
-
|---|---|
85
-
| Name | Enter **@**|
86
-
| Type | Select **A - Alias to IPv4 address**|
87
-
| Alias record set | Select **Yes**. |
88
-
| Alias type | Select **Azure resource**|
89
-
| Choose a subscription | Select your Azure subscription. |
90
-
| Azure resource | Select the name of your static web app. |
91
-
| TTL | Keep default value. |
92
-
| TTL unit | Keep default value. |
93
-
94
-
4. Select **OK**.
95
-
96
-
5. Open a new browser tab and go to your apex domain.
40
+
Observe the *Status* for the row of your apex domain. While this validation is running, the necessary CNAME or TXT and ALIAS records are created for you automatically. Once the validation is complete, your apex domain is publicly available.
97
41
98
-
After the DNS records are updated, you should see your static web app in the browser. Also, inspect the location to verify that your site is served securely using `https`.
42
+
Open a new browser tab and go to your apex domain. You should see your static web app in the browser. Also, inspect the location to verify that your site is served securely using `https`.
0 commit comments