adding clarity

Author: greg-lindsay

articles/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances.md

@@ -109,6 +109,9 @@ When two auto-registered PTR records are returned as shown above, then forward l
 
 Reverse DNS lookups are scoped to a given virtual network even if it is peered to other virtual networks. Reverse DNS queries for IP addresses of virtual machines located in peered virtual networks will return **NXDOMAIN**.
 
+> [!NOTE]
+> Reverse DNS (PTR) records are not stored in a forward private DNS zone. Reverse DNS records are stored in a reverse DNS (in-addr.arpa) zone. The default reverse DNS zone associated with a vnet is not viewable or editable.
+
 You can disable the reverse DNS function in a virtual network by creating your own reverse lookup zone using [Azure DNS private zones](../dns/private-dns-overview.md), and then linking this zone to your virtual network. For example, if the IP address space of your virtual network is 10.20.0.0/16, then you can create a empty private DNS zone **20.10.in-addr.arpa** and link it to the virtual network. This zone will override the default reverse lookup zones for the virtual network and since this zone is empty you will get **NXDOMAIN** for your reverse DNS queries, unless you manually create these entries. Auto-registration of PTR records is not supported, so if you wish to create entries, these must be entered manually. You must also disable auto-registration in the vnet if it is enabled for other zones due to [restrictions](private-dns-autoregistration.md#restrictions) that permit only one private zone to be linked if autoregistration is enabled. See the [Quickstart guide](../dns/private-dns-getstarted-portal.md) for details on how to create a private DNS zone and link it to a virtual network.
 
 > [!NOTE]