Merge pull request #275786 from greg-lindsay/dns-react

updating 11 articles for REACT portal UI change

Author: denrea

articles/dns/delegate-subdomain.md

@@ -5,7 +5,7 @@ services: dns
 author: greg-lindsay
 ms.service: dns
 ms.topic: how-to
-ms.date: 11/28/2023
+ms.date: 06/07/2024
 ms.author: greglin
 ---
 
@@ -24,7 +24,7 @@ To delegate an Azure DNS subdomain, the parent public domain must first be deleg
 
 ## Delegate a subdomain
 
-The **engineering.adatum.com** subdomain can already exist. If it doesn't exist, it is created.
+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.
 
 To delegate the **engineering** subdomain under **adatum.com**:
 
@@ -39,7 +39,7 @@ To delegate the **engineering** subdomain under **adatum.com**:
 
    [ ![A screenshot showing contents of the child zone.](./media/delegate-subdomain/child-zone-contents.png) ](./media/delegate-subdomain/child-zone-contents.png#lightbox)
 
-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).
+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).
 
    [ ![A screenshot showing contents of the parent zone.](./media/delegate-subdomain/parent-zone-contents.png) ](./media/delegate-subdomain/parent-zone-contents.png#lightbox)
 

articles/dns/dns-delegate-domain-azure-dns.md

@@ -5,15 +5,15 @@ services: dns
 author: greg-lindsay
 ms.service: dns
 ms.topic: tutorial
-ms.date: 05/29/2024
+ms.date: 06/07/2024
 ms.author: greglin
 ms.custom: template-tutorial
 #Customer intent: As an experienced network administrator, I want to configure Azure DNS, so I can host DNS zones.
 ---
 
 # Tutorial: Host your domain in Azure DNS
 
-You can use Azure DNS to host your DNS domain and manage your DNS records. By hosting your domains in Azure, you can manage your DNS records by using the same credentials, APIs, tools, and billing as your other Azure services.
+You can use Azure DNS to host your DNS domain and manage your DNS records. By hosting your domains in Azure, you can manage your DNS records using the same credentials, APIs, tools, and billing as your other Azure services.
 
 Suppose you buy the domain `contoso.com` from a domain name registrar and then create a zone with the name `contoso.com` in Azure DNS. Since you're the owner of the domain, your registrar offers you the option to configure the name server (NS) records for your domain. The registrar stores the NS records in the `.com` parent zone. Internet users around the world are then directed to your domain in your Azure DNS zone when they try to resolve DNS records in `contoso.com`.
 
@@ -46,7 +46,7 @@ If you don’t have an Azure subscription, create a [free account](https://azure
 * A domain name that you can host in Azure DNS. You must have full control of this domain. Full control includes the ability to set the name server (NS) records for the domain.
 
 > [!NOTE]
-> In this tutorial, `contoso.com` is used as an example domain name. Replace `contoso.com` with your own domain name.
+> In this tutorial, `contoso.xyz` is used as an example domain name. Replace `contoso.xyz` with your own domain name.
 
 ## Sign in to Azure
 
@@ -55,50 +55,45 @@ Sign in to the [Azure portal](https://portal.azure.com).
 ## Create a DNS zone
 
 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.
-
-1. In **DNS zones**, select **+ Create**.
-
-1. In the **Create DNS zone** page, enter or select the following information in the **Basics** tab:
+2. In **DNS zones**, select **+ Create**.
+3. In the **Create DNS zone** page, enter or select the following information in the **Basics** tab:
 
     | Setting | Value |
     | ------- | ----- |
     | **Project details**  |       |
     | Subscription | Select your Azure subscription.|
-    | Resource group | Select **Create new** </br> In **Name**, enter **myResourceGroup** </br> Select **OK**. |
+    | Resource group | Choose an existing resource group or select **Create new** and enter a name for the new resource group. For example: **myResourceGroup**. |
     | **Instance details** |       |
     | 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). |
-    | Name | Enter your DNS zone name. |
-    | 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. |
+    | Name | Enter your DNS zone name. For example: **contoso.xyz**.|
+    | 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. |
 
-    :::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.":::
+    :::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.":::
 
 1. Select **Review + create**.    
 1. Select **Create**.
 
    > [!NOTE] 
-   > 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).
+   > 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).
 
 ## Retrieve name servers
 
-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.
-
-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.
+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.
 
-1. In **DNS zones**, select **contoso.com**.
+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.
+2. In **DNS zones**, select the name of your zone. For example: **contoso.xyz**.
+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`:
 
-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`:
-
-    :::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":::
+[ ![Screenshot showing the overview of DNS zone contoso.xyz.](./media/dns-delegate-domain-azure-dns/contoso.xyz.overview.png) ](./media/dns-delegate-domain-azure-dns/contoso.xyz.overview.png)
 
 Azure DNS automatically creates authoritative NS records in your zone for the assigned name servers.
 
 ## Delegate the domain
 
-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. 
-
-1. In the registrar's DNS management page, edit the NS records and replace the NS records with the Azure DNS name servers.
+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**.
 
-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.
+1. In the registrar's DNS management page, create or edit the NS records to assign the Azure DNS name servers.
+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.
 
 > [!IMPORTANT]
 > 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
 1. From a command prompt, enter a nslookup command similar to the following example:
 
    ```
-   nslookup -type=SOA contoso.com
+   nslookup -type=SOA contoso.xyz
    ```
 
 1. Verify that your response looks similar to the following nslookup output:
 
    ```
-   Server: ns1-04.azure-dns.com
-   Address: 40.90.4.1
-
-   contoso.com
-           primary name server = ns1-04.azure-dns.com
+   contoso.xyz
+           primary name server = ns1-37.azure-dns.com
            responsible mail addr = azuredns-hostmaster.microsoft.com
            serial = 1
            refresh = 3600 (1 hour)
            retry = 300 (5 mins)
            expire = 604800 (7 days)
            default TTL = 300 (5 mins)
-   ns1-01.azure-dns.com    internet address = 40.90.4.1
-   ns1-01.azure-dns.com    AAAA IPv6 address = 2603:1061::1
    ```
 
 ## Clean up resources

articles/dns/dns-domain-delegation.md

@@ -4,24 +4,26 @@ description: Understand how to change domain delegation and use Azure DNS name s
 services: dns
 author: greg-lindsay
 ms.service: dns
-ms.date: 11/30/2023
+ms.date: 06/07/2024
 ms.author: greglin
 ms.topic: conceptual
 ---
 
 # Delegation of DNS zones with Azure DNS
 
-Azure DNS allows you to host a DNS zone and manage the DNS records for a domain in Azure. In order for DNS queries for a domain to reach Azure DNS, the domain has to be delegated to Azure DNS from the parent domain. Keep in mind Azure DNS isn't the domain registrar. This article explains how domain delegation works and how to delegate domains to Azure DNS.
+Azure DNS allows you to host a DNS domain and manage the DNS zone records. To host your domain in Azure, the zone must be created in Azure and delegated to Azure's authoritative DNS servers with a domain registrar. Azure DNS isn't the domain registrar. This article explains how domain delegation works and how to delegate domains to Azure DNS.
+
+Also see: [Tutorial: Host your domain in Azure DNS](dns-delegate-domain-azure-dns.md).
 
 ## How DNS delegation works
 
 ### Domains and zones
 
-The Domain Name System is a hierarchy of domains. The hierarchy starts from the `root` domain, whose name is simply "`.`".  Below this come top-level domains, such as `com`, `net`, `org`, `uk` or `jp`.  Below these top-level domains are second-level domains, such as `org.uk` or `co.jp`.  And so on. The domains in the DNS hierarchy are hosted using separate DNS zones. These zones are globally distributed, hosted by DNS name servers around the world.
+The Domain Name System (DNS) is a hierarchy of domains. The hierarchy starts from the `root` domain, whose name is simply "`.`".  Below this are top-level domains, such as `com`, `net`, `org`, `uk` or `jp`.  Below these top-level domains are second-level domains, such as `org.uk` or `co.jp`.  And so on. The domains in the DNS hierarchy exist as separate DNS zones. These zones are globally distributed and hosted by DNS name servers around the world. 
 
-**DNS zone** - A domain is a unique name in the Domain Name System, for example `contoso.com`. A DNS zone is used to host the DNS records for a particular domain. For example, the domain `contoso.com` may contain several DNS records such as `mail.contoso.com` (for a mail server) and `www.contoso.com` (for a website).
+**DNS zone** - A public DNS zone has a unique name (for example: **contoso.com**) and consists of a collection of resource records. The DNS zone hosts DNS resource records of varying types. For example, the domain `contoso.com` can contain DNS records such as `mail.contoso.com` (for a mail server) and `www.contoso.com` (for a website).
 
-**Domain registrar** - A domain registrar is a company who can provide Internet domain names. They verify if the Internet domain you want to use is available and allow you to purchase it. Once the domain name is registered, you're the legal owner for the domain name. If you already have an Internet domain, you'll use the current domain registrar to delegate to Azure DNS.
+**Domain registrar** - A domain registrar is an organization that can provide Internet (public) domain names. They verify if the Internet domain you want to use is available and provide the ability to purchase it. When you register a domain name, you're the legal owner for that domain. If you already have an Internet domain, you can use your current domain registrar to delegate this domain to Azure DNS.
 
 For more information about accredited domain registrars, see [ICANN-Accredited Registrars](https://www.icann.org/registrar-reports/accredited-list.html).
 
@@ -32,29 +34,29 @@ There are two types of DNS servers:
 * An *authoritative* DNS server hosts DNS zones. It answers DNS queries for records in those zones only.
 * A *recursive* DNS server doesn't host DNS zones. It answers all DNS queries by calling authoritative DNS servers to gather the data it needs.
 
-Azure DNS provides an authoritative DNS service.  It doesn't provide a recursive DNS service. Cloud Services and VMs in Azure are automatically configured to use a recursive DNS service that is provided separately as part of Azure's infrastructure. For information on how to change these DNS settings, see [Name Resolution in Azure](../virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances.md#name-resolution-that-uses-your-own-dns-server).
+Azure DNS provides an authoritative DNS service.  It doesn't provide a public recursive DNS service. For information about Azure's private DNS recursive service, see [What is Azure DNS Private Resolver](dns-private-resolver-overview.md). By default, cloud services and VMs in Azure are configured to use a recursive DNS service that is provided separately as part of Azure's infrastructure. For information on how to change these DNS settings, see [Name Resolution in Azure](../virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances.md#name-resolution-that-uses-your-own-dns-server).
 
 DNS clients in PCs or mobile devices typically call a recursive DNS server to do any DNS queries the client applications need.
 
-When a recursive DNS server receives a query for a DNS record such as `www.contoso.com`, it first needs to find the name server hosting the zone for the `contoso.com` domain. To find the name server, it starts at the root name servers, and from there finds the name servers hosting the `com` zone. It then queries the `com` name servers to find the name servers hosting the `contoso.com` zone.  Finally, it's able to query these name servers for `www.contoso.com`.
+When a recursive DNS server receives a query for a DNS record such as `www.contoso.com`, it first needs to find the authoritative name server hosting the `contoso.com` domain. To find the name server, it starts at the root name servers, and from there finds the name servers hosting the `com` domain. It then queries the `com` name servers to find the name servers hosting the `contoso.com` domain.  Finally, it's able to query these name servers for `www.contoso.com`.
 
 This procedure is called resolving the DNS name. Strictly speaking, DNS resolution includes more steps such as following CNAMEs, but that's not important to understanding how DNS delegation works.
 
-How does a parent zone point to the name servers for a child zone? It does this using a special type of DNS record called an NS record (NS stands for 'name server'). For example, the root zone contains NS records for `com` and shows the name servers for the `com` zone. In turn, the `com` zone contains NS records for `contoso.com`, which shows the name servers for the `contoso.com` zone. Setting up the NS records for a child zone in a parent zone is called delegating the domain.
+How does a parent zone point to the name servers for a child zone? It does this using a special type of DNS record called an NS record (NS stands for 'name server'). For example, the root zone contains NS records for `com` and shows the name servers for the `com` domain. In turn, the `com` domain contains NS records for `contoso.com` that display name servers for the `contoso.com` domain. Setting up the NS records for a child zone in a parent zone is called delegating the domain.
 
-The following image shows an example DNS query. The `contoso.net` and `partners.contoso.net` are Azure DNS zones.
+The following image shows an example DNS query. The `contoso.net` and `partners.contoso.net` zones are public DNS domains that have been delegated to Azure's authoritative DNS servers.
 
-![Dns-nameserver](./media/dns-domain-delegation/image1.png)
+![A conceptual diagram showing low DNS delegation works.](./media/dns-domain-delegation/delegation-diagram.png)
 
 1. The client requests `www.partners.contoso.net` from their local DNS server.
-2. The local DNS server doesn't have the record so it makes a request to their root name server.
-3. The root name server doesn't have the record, but knows the address of the `.net` name server, it provides that address to the DNS server
+2. The local DNS server doesn't have the record so it makes a request to the root name server.
+3. The root name server doesn't have the record, but knows the address of the `.net` name server, which it provides to the local DNS server
 4. The local DNS server sends the request to the `.net` name server.
-5. The `.net` name server doesn't have the record but does know the address of the `contoso.net` name server. In this case, it responds with the address of the name server for the DNS zone hosted in Azure DNS.
-6. The local DNS server sends the request to the name server for the `contoso.net` zone hosted in Azure DNS.
-7. The zone `contoso.net` doesn't have the record but knows the name server for `partners.contoso.net` and responds with the address. In this case, it's a DNS zone hosted in Azure DNS.
-8. The local DNS server sends the request to the name server for the `partners.contoso.net` zone.
-9. The `partners.contoso.net` zone has the A record and responds with the IP address.
+5. The `.net` name server doesn't have the record but does know the address of the `contoso.net` name server. In this case, it responds with the address of the name server for the DNS domain hosted in Azure DNS.
+6. The local DNS server sends the request to the name server for the `contoso.net` domain hosted in Azure DNS.
+7. The zone `contoso.net` doesn't have the record but knows the name server for `partners.contoso.net` and responds with the address. In this case, it's a DNS domain hosted in Azure DNS.
+8. The local DNS server sends the request to the name server for the `partners.contoso.net` domain.
+9. The `partners.contoso.net` zone has the A record for `www` and responds with the IP address.
 10. The local DNS server provides the IP address to the client.
 11. The client connects to the website `www.partners.contoso.net`.