Merge pull request #235859 from greg-lindsay/dns-upd

GitHub issues 104115 and 104706

Author: prmerger-automator[bot]

articles/dns/dns-import-export.md

@@ -6,7 +6,7 @@ services: dns
 author: greg-lindsay
 ms.service: dns
 ms.custom: devx-track-azurecli
-ms.date: 09/27/2022
+ms.date: 04/25/2023
 ms.author: greglin
 ms.topic: how-to
 ---
@@ -31,9 +31,12 @@ Before you import a DNS zone file into Azure DNS, you need to obtain a copy of t
 * If your DNS zone is hosted on Windows DNS, the default folder for the zone files is **%systemroot%\system32\dns**. The full path to each zone file is also shown on the **General** tab of the DNS console.
 * If your DNS zone is hosted using BIND, the location of the zone file for each zone gets specified in the BIND configuration file **named.conf**.
 
+> [!IMPORTANT]
+> If the zone file that you import contains CNAME entries that point to names in another private zone, Azure DNS resolution of the CNAME will fail unless the other zone is also imported, or the CNAME entries are modified.
+
 ## Import a DNS zone file into Azure DNS
 
-Importing a zone file creates a new zone in Azure DNS if the zone doesn't already exist. If the zone exist, then the record sets in the zone file will be merged with the existing record sets.
+Importing a zone file creates a new zone in Azure DNS if the zone doesn't already exist. If the zone exists, then the record sets in the zone file will be merged with the existing record sets.
 
 ### Merge behavior
 

articles/dns/private-dns-scenarios.md

@@ -5,7 +5,7 @@ services: dns
 author: greg-lindsay
 ms.service: dns
 ms.topic: article
-ms.date: 09/27/2022
+ms.date: 04/25/2023
 ms.author: greglin
 ---
 
@@ -22,6 +22,9 @@ You can also do a reverse DNS query (PTR) for the private IP of VNETA-VM1 (10.0.
 
 ![Single Virtual network resolution](./media/private-dns-scenarios/single-vnet-resolution.png)
 
+> [!NOTE]
+> The IP addresses 10.0.0.1 and 10.0.0.2 are examples only. Since Azure reserves the first four addresses in a subnet, the .1 and .2 addresses are not normally assigned to a VM. 
+
 ## Scenario: Name Resolution across virtual networks
 
 In this scenario, you need to associate a private zone with multiple virtual networks. You can implement this solution in various network architectures such as the Hub-and-Spoke model. This configuration is when a central hub virtual network is used to connect multiple spoke virtual networks together. The central hub virtual network can be linked as the registration virtual network and the spoke virtual networks can be linked as resolution virtual networks.