Skip to content

Commit 782d59f

Browse files
authored
Update native-dns-forward-lookup-zone.md
1 parent 1c109ab commit 782d59f

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Private and Public DNS forward lookup zone configuration
33
description: Learn about DNS forward lookup zone for Azure VMware Solution Generation 2 private clouds.
44
ms.topic: how-to
55
ms.service: azure-vmware
6-
ms.date: 3/14/2025
6+
ms.date: 4/15/2025
77
ms.custom: engagement-fy25
88
# customer intent: As a cloud administrator, I want to configure DNS forward lookup zone for Azure VMware Solution Generation 2 private clouds so that I can manage domain name resolution for private cloud appliances.
99
---
@@ -18,15 +18,15 @@ Gen 2 private cloud successfully deployed.
1818

1919
## DNS forward lookup zone configuration options
2020

21-
Azure VMware Solution allows you to configure DNS forward lookup zones in two ways: public or private. This configuration defines how DNS name resolution for Azure VMware Solution components, such as vCenter, ESX hosts, and NSX Managers, is performed.
21+
Azure VMware Solution allows you to configure DNS forward lookup zones in two ways: public or private. This configuration defines how DNS name resolution for Azure VMware Solution components, such as vCenter Server, ESX hosts, and NSX Manager, is performed.
2222

2323
**Public**: The public DNS forward lookup zone allows domain names to be resolved using any public DNS servers.
2424

2525
**Private**: The private DNS forward lookup zone makes it resolvable only within a private customer environment and provides other security compliance. If a customer chooses Private Forward Lookup Zone, the Software-Defined Data Center (private cloud) Fully Qualified Domain Names (FQDNs) are resolvable from the Virtual Network where the private cloud is provisioned. If need to enable this zone to be resolvable outside of this Virtual Network, such as in a customer on-premises environment, you need to configure an Azure DNS Private Resolver or deploy your own DNS server in your Virtual Network that uses the Azure DNS Service (168.63.129.16) to resolve your private cloud FQDNs.
2626

2727
DNS forward lookup zone can be configured at the time of creation or changed after the private cloud is created. The following diagram shows the configuration page for the DNS forward lookup zone.
2828

29-
:::image type="content" source="./media/native-connectivity/native-connect-dns-lookup.png" alt-text="Diagram showing an Azure VMware Solution DNS forward lookup." lightbox="media/native-connectivity/native-connect-dns-lookup.png":::
29+
:::image type="content" source="./media/native-connectivity/native-connect-dns-lookup.png" alt-text="Diagram showing an Azure VMware Solution Gen 2 DNS forward lookup." lightbox="media/native-connectivity/native-connect-dns-lookup.png":::
3030

3131
## Configuring Private DNS for your Azure VMware Solution Generation 2 Private Cloud
3232

@@ -56,7 +56,7 @@ You can now resolve your private cloud DNS records from any workload using the I
5656

5757
### Enable Resolution for private cloud Workload Virtual Machines
5858

59-
If you need workload Virtual Machines deployed in your private cloud to resolve the private cloud management components you must add a forwarder to NSX.
59+
If you need workload Virtual Machines deployed in your private cloud to resolve the private cloud management components you must add a forwarder to VMware NSX.
6060

6161
1. In your Resource group, open your private cloud.
6262
2. Expand Workload Networking and click on DNS.

0 commit comments

Comments
 (0)