You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-vmware/native-dns-forward-lookup-zone.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Private and Public DNS forward lookup zone configuration
3
3
description: Learn about DNS forward lookup zone for Azure VMware Solution Generation 2 private clouds.
4
4
ms.topic: how-to
5
5
ms.service: azure-vmware
6
-
ms.date: 3/14/2025
6
+
ms.date: 4/15/2025
7
7
ms.custom: engagement-fy25
8
8
# 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.
9
9
---
@@ -18,15 +18,15 @@ Gen 2 private cloud successfully deployed.
18
18
19
19
## DNS forward lookup zone configuration options
20
20
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.
22
22
23
23
**Public**: The public DNS forward lookup zone allows domain names to be resolved using any public DNS servers.
24
24
25
25
**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.
26
26
27
27
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.
28
28
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":::
30
30
31
31
## Configuring Private DNS for your Azure VMware Solution Generation 2 Private Cloud
32
32
@@ -56,7 +56,7 @@ You can now resolve your private cloud DNS records from any workload using the I
56
56
57
57
### Enable Resolution for private cloud Workload Virtual Machines
58
58
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.
60
60
61
61
1. In your Resource group, open your private cloud.
0 commit comments