GitHub issue 104115

Author: greg-lindsay

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.