Merge pull request #309370 from yash177-maker1/docs-editor/native-dns-forward-lookup-zone-1765475201

Update native-dns-forward-lookup-zone.md

Author: prmerger-automator[bot]

articles/azure-vmware/native-dns-forward-lookup-zone.md

@@ -100,17 +100,17 @@ After deploying the Azure DNS Private Resolver, you must create a forward lookup
 
 To configure the forward lookup zone:
 
-1. **Identify the DNS zone name** for your private cloud. The zone is typically derived from the Fully Qualified Domain Name (FQDN) of the vCenter Server. For example, if the vCenter Server URL is `https://vc123.avs.com`, the DNS zone name is `avs.com` (everything after `vc123`).
+1. **Identify the DNS zone name** for your private cloud. The zone is typically derived from the Fully Qualified Domain Name (FQDN) of the vCenter Server. For example, if the vCenter Server URL is `https://vc123.avs.azure.com`, the DNS zone name is `avs.azure.com` (everything after `vc123`).
 
 2. **Create a forward lookup zone** in your DNS solution (either your on-premises DNS server or a DNS server you deployed in the Azure Virtual Network of the private cloud). Use the DNS zone name identified above.
 
 3. **Configure a forwarder** in that lookup zone. Point the zone to the IP address of the inbound endpoint of the Azure DNS Private Resolver that you deployed in the Virtual Network of the private cloud. This ensures that any DNS queries for private cloud FQDNs are forwarded to the Azure DNS Private Resolver.
 
 **Example**:
 
-vCenter Server URL: `https://vc123.avs.com`
+vCenter Server URL: `https://vc123.avs.azure.com`
 
-Forward lookup zone to create: `avs.com`
+Forward lookup zone to create: `avs.azure.com`
 
 Forwarder target: IP address of your Azure DNS Private Resolver inbound endpoint