Skip to content

Commit 179130f

Browse files
Merge pull request #231745 from Zsoldier/patch-9
Update configure-dns-azure-vmware-solution.md
2 parents f455d59 + 342a11a commit 179130f

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

articles/azure-vmware/configure-dns-azure-vmware-solution.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -76,6 +76,18 @@ The diagram shows that the NSX-T Data Center DNS Service can forward DNS queries
7676

7777
1. Repeat the above steps for other FQDN zones, including any applicable reverse lookup zones.
7878

79+
## Change Default T1 DNS Forwarder Zone
80+
1. In your Azure VMware Solution private cloud, under **Workload Networking**, select **DNS** > **DNS zones** > Check **TNT##-DNS-FORWARDER-ZONE**. Then select **Edit**.
81+
82+
![AVS-DNS](https://user-images.githubusercontent.com/7501186/226980095-b0576824-e1b7-46dc-b726-58670e4e3096.png)
83+
84+
85+
2. Change DNS server entries to valid reachable IP addresses. Then select **OK**
86+
87+
![Edit_DNS_Zone](https://user-images.githubusercontent.com/7501186/226980023-8b92fce9-310e-4934-9045-238bcd5d921f.png)
88+
89+
>[!IMPORTANT]
90+
>A DNS endpoint that is unreachable by the NSX-T DNS server will result in an NSX-T alarm stating that the endpoint is unreachable. In cases of the default configuration provided with AVS, this is due to internet that is disabled by default. The alarm can be acknowledged and ignored, or the default configuration above can be changed to a valid endpoint.
7991
8092
## Verify name resolution operations
8193

0 commit comments

Comments
 (0)