edits

Author: greg-lindsay

articles/dns/dns-domain-delegation.md

@@ -11,17 +11,19 @@ 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`.
 

articles/dns/dns-getstarted-portal.md

@@ -5,7 +5,7 @@ description: Use this step-by-step quickstart guide to learn how to create an Az
 services: dns
 author: greg-lindsay
 ms.author: greglin
-ms.date: 05/22/2024
+ms.date: 06/07/2024
 ms.topic: quickstart
 ms.service: dns
 ms.custom: mode-ui
@@ -47,7 +47,7 @@ A DNS zone contains the DNS entries for a domain. To start hosting your domain i
 2. On the **DNS zone** page, select **Create**.
 
 <!-- Reducing the size of this screenshot: (![A screenshot of the DNS zone marketplace.](./media/dns-getstarted-portal/dns-new-zone.png))-->
-  <img src="./media/dns-getstarted-portal/dns-new-zone.png" alt="A screenshot of the DNS zone marketplace." width="50%">
+   <img src="./media/dns-getstarted-portal/dns-new-zone.png" alt="A screenshot of the DNS zone marketplace." width="50%">
 
 3. On the **Create DNS zone** page, type or select the following values:
 
@@ -59,15 +59,15 @@ A DNS zone contains the DNS entries for a domain. To start hosting your domain i
 
    ![A screenshot showing how to create a DNS zone.](./media/dns-getstarted-portal/dns-create-zone.png)
 
-It may take a few minutes to create the zone.
+   It may take a minute to create the zone.
 
 ## Create a DNS record
 
 Next, DNS records are created for your domain inside the DNS zone. A new address record, known as an '**A**' record, is created to resolve a host name to an IPv4 address.
 
 **To create an 'A' record:**
 
-1. In the Azure portal, under **All resources**, open the **contoso.xyz** DNS zone in the **MyResourceGroup** resource group. You can enter *contoso.xyz* in the **Filter by name** box to find it more easily.
+1. In the Azure portal, under **Resources**, open the **contoso.xyz** DNS zone.
 2. At the top of the **contoso.xyz** DNS zone page, select **Record sets** and then select **+ Add**. The **Add a record set** window appears.
 3. In the **Add a record set** window, enter or select the following values:
 

articles/dns/dns-import-export-portal.md

@@ -117,15 +117,17 @@ The following notes provide more details about the zone import process.
 
     ![The adatum.com zone displayed in the DNS Zone Diff Viewer](./media/dns-import-export-portal/diff-viewer.png)
 
-10. Select **Create**. The zone data is imported and the zone is displayed. See the following example:
+10. Select **Create**. A prompt appears to save the existing zone to your local device before it is overwritten. Select **Download and Continue**. The zone data is imported and the zone is displayed. 
+
+11. Select **Recordsets** to view the newly imported resource records. See the following example:
 
     [ ![The adatum.com zone displayed in the overview pane](./media/dns-import-export-portal/adatum-imported.png) ](./media/dns-import-export-portal/adatum-imported.png#lightbox)
 
 ## Export a zone file
 
 1. Open the **DNS zones** overview page and select the zone you wish to export. For example, **adatum.com**. See the following example:
 
-    [ ![The adatum.com zone ready to export](./media/dns-import-export-portal/adatum-export.png) ](./media/dns-import-export-portal/adatum-export.png#lightbox)
+    [ ![The adatum.com zone ready to export](./media/dns-import-export-portal/adatum-overview.png) ](./media/dns-import-export-portal/adatum-overview.png#lightbox)
 
 2. Select **Export**.  The file is downloaded to your default downloads directory as a text file with the name AzurePublicDnsZone-adatum.com`number`.txt where `number` is an autogenerated index number.
 3. Open the file to view the contents. See the following example: