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/dns/delegate-subdomain.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: dns
5
5
author: greg-lindsay
6
6
ms.service: dns
7
7
ms.topic: how-to
8
-
ms.date: 05/20/2024
8
+
ms.date: 06/07/2024
9
9
ms.author: greglin
10
10
---
11
11
@@ -24,7 +24,7 @@ To delegate an Azure DNS subdomain, the parent public domain must first be deleg
24
24
25
25
## Delegate a subdomain
26
26
27
-
The **engineering.adatum.com** subdomain can already exist. If it doesn't exist, it is created.
27
+
The **engineering.adatum.com** subdomain can already exist. If it doesn't exist, it is created. The parent domain (in this example: **adatum.com**) must already exist as an Azure-hosted domain.
28
28
29
29
To delegate the **engineering** subdomain under **adatum.com**:
30
30
@@ -39,7 +39,7 @@ To delegate the **engineering** subdomain under **adatum.com**:
39
39
40
40
[](./media/delegate-subdomain/child-zone-contents.png#lightbox)
41
41
42
-
6. Select the parent **adatum.com** zone again and notice that an **NS** record has been added with the name **engineering** and contents the same as NS records in the child zone. You might need to refresh the page. These are the Azure DNS nameservers that are authoritative for the subdomain (child zone).
42
+
6. Select the parent **adatum.com** zone again and then select **Recordsets**. Notice that an **NS** record has been added with the name **engineering** and contents the same as NS records in the child zone. These are the Azure DNS nameservers that are authoritative for the subdomain (child zone).
43
43
44
44
[](./media/delegate-subdomain/parent-zone-contents.png#lightbox)
Copy file name to clipboardExpand all lines: articles/dns/dns-delegate-domain-azure-dns.md
+18-28Lines changed: 18 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,50 +55,45 @@ Sign in to the [Azure portal](https://portal.azure.com).
55
55
## Create a DNS zone
56
56
57
57
1. In the Azure portal, enter *dns zone* in the search box at the top of the portal, and then select **DNS zones** from the search results.
58
-
59
-
1. In **DNS zones**, select **+ Create**.
60
-
61
-
1. In the **Create DNS zone** page, enter or select the following information in the **Basics** tab:
58
+
2. In **DNS zones**, select **+ Create**.
59
+
3. In the **Create DNS zone** page, enter or select the following information in the **Basics** tab:
62
60
63
61
| Setting | Value |
64
62
| ------- | ----- |
65
63
|**Project details**||
66
64
| Subscription | Select your Azure subscription.|
67
-
| Resource group |Select **Create new**</br> In **Name**, enter **myResourceGroup** </br> Select **OK**. |
65
+
| Resource group |Choose an existing resource group or select **Create new**and enter a name for the new resource group. For example: **myResourceGroup**. |
68
66
|**Instance details**||
69
67
| This zone is a child of an existing zone already hosted in Azure DNS | Clear this checkbox since the DNS zone isn't a [child zone](./tutorial-public-dns-zones-child.md). |
70
-
| Name | Enter your DNS zone name. |
71
-
| Resource group location |Select the resource group location. </br> The resource group location doesn't affect your DNS zone service, which is global and not bound to a location. |
68
+
| Name | Enter your DNS zone name. For example: **contoso.xyz**.|
69
+
| Resource group location |If you created a new resource group, choose a location. </br> The resource group location doesn't affect your DNS zone service, which is global and not bound to a location. |
72
70
73
-
:::image type="content" source="./media/dns-delegate-domain-azure-dns/create-parent-dns-zone.png" alt-text="Screenshot of Create D N S zone page showing the settings used in this tutorial to create a parent D N S zone.":::
71
+
:::image type="content" source="./media/dns-delegate-domain-azure-dns/create-parent-dns-zone.png" alt-text="Screenshot of the Create DNS zone page showing the settings used in this tutorial to create a parent DNS zone.":::
74
72
75
73
1. Select **Review + create**.
76
74
1. Select **Create**.
77
75
78
76
> [!NOTE]
79
-
> If the new zone that you are creating is a child zone (e.g. parent zone = `contoso.com` child zone = `child.contoso.com`), then please refer to[Create a child DNS zone tutorial](./tutorial-public-dns-zones-child.md).
77
+
> If the new zone that you are creating is a child zone see[Create a child DNS zone tutorial](./tutorial-public-dns-zones-child.md).
80
78
81
79
## Retrieve name servers
82
80
83
-
Before you can delegate your DNS zone to Azure DNS, you need to know the name servers for your zone. Azure DNS gives name servers from a pool each time a zone is created.
84
-
85
-
1. In the Azure portal, enter *dns zone* in the search box at the top of the portal, and then select **DNS zones** from the search results.
81
+
Before you can delegate your DNS zone to Azure DNS, you need to know the name servers for your zone. Azure DNS assigns name servers from a pool each time a zone is created.
86
82
87
-
1. In **DNS zones**, select **contoso.com**.
83
+
1. In the Azure portal, enter **DNS zones** in the search box at the top of the portal and then select **DNS zones** from the search results.
84
+
2. In **DNS zones**, select the name of your zone. For example: **contoso.xyz**.
85
+
3. On the **Overview** page, retrieve the name servers. In this example, the DNS zone **contoso.xyz** has been assigned name servers `ns1-37.azure-dns.com`, `ns2-37.azure-dns.net`, `ns3-37.azure-dns.org`, and `ns4-37.azure-dns.info`:
88
86
89
-
1. In the **Overview** page, retrieve the name servers. In this example, the DNS zone **contoso.com** has been assigned name servers `ns1-01.azure-dns.com`, `ns2-01.azure-dns.net`, `ns3-01.azure-dns.org`, and `ns4-01.azure-dns.info`:
90
-
91
-
:::image type="content" source="./media/dns-delegate-domain-azure-dns/dns-name-servers-inline.png" alt-text="Screenshot of D N S zone showing assigned Azure name servers" lightbox="./media/dns-delegate-domain-azure-dns/dns-name-servers-expanded.png":::
87
+
[](./media/dns-delegate-domain-azure-dns/contoso.xyz.overview.png)
92
88
93
89
Azure DNS automatically creates authoritative NS records in your zone for the assigned name servers.
94
90
95
91
## Delegate the domain
96
92
97
-
Once the DNS zone gets created and you have the name servers, you'll need to update the parent domain with the Azure DNS name servers. Each registrar has its own DNS management tools to change the name server records for a domain.
98
-
99
-
1. In the registrar's DNS management page, edit the NS records and replace the NS records with the Azure DNS name servers.
93
+
After the DNS zone is created, you must update the parent domain with the Azure DNS name servers by registering the domain with a domain registrar. Each registrar has its own DNS management tools to assign the name server records for a domain. In the example used here, the parent domain is **xyz**.
100
94
101
-
1. When you delegate a domain to Azure DNS, you must use the name servers that Azure DNS provides. Use all four name servers, regardless of the name of your domain. Domain delegation doesn't require a name server to use the same top-level domain as your domain.
95
+
1. In the registrar's DNS management page, create or edit the NS records to assign the Azure DNS name servers.
96
+
2. When you delegate a domain to Azure DNS, you must use the name servers that Azure DNS provides. Use all four name servers, regardless of the name of your domain. Domain delegation doesn't require a name server to use the same top-level domain as your domain.
102
97
103
98
> [!IMPORTANT]
104
99
> When you copy each name server address, make sure you copy the trailing period at the end of the address. The trailing period indicates the end of a fully qualified domain name. Some registrars append the period if the NS name doesn't have it at the end. To be compliant with the DNS RFC, include the trailing period.
@@ -114,25 +109,20 @@ You don't have to specify the Azure DNS name servers. If the delegation is set u
114
109
1. From a command prompt, enter a nslookup command similar to the following example:
115
110
116
111
```
117
-
nslookup -type=SOA contoso.com
112
+
nslookup -type=SOA contoso.xyz
118
113
```
119
114
120
115
1. Verify that your response looks similar to the following nslookup output:
121
116
122
117
```
123
-
Server: ns1-04.azure-dns.com
124
-
Address: 40.90.4.1
125
-
126
-
contoso.com
127
-
primary name server = ns1-04.azure-dns.com
118
+
contoso.xyz
119
+
primary name server = ns1-37.azure-dns.com
128
120
responsible mail addr = azuredns-hostmaster.microsoft.com
0 commit comments