DNS forwarder vmwNsxTDataCenterIntentPath(vmwNsxTDataCenterDNSId) did not receive a timely response from upstream server vmwNsxTDataCenterDNSUpstreamIP. Compute instance connectivity to timed out FQDNs may be impacted. Action required: 1. Invoke the NSX API GET /api/v1/dns/forwarders/vmwNsxTDataCenterDNSId/nslookup? address=<address>&server_ip=vmwNsxTDataCenterDNSUpstreamIP&source_ip=<source_ip>. This API request triggers a DNS lookup to the upstream server in the DNS forwarder's network namespace. <address> is the IP address or FQDN in the same domain as the upstream server. <source_ip> is an IP address in the upstream server's zone. If the API returns a connection timed out response, there is likely a network error or upstream server problem. Check why DSN lookups are not reaching the upstream server or why the upstream server is not returning a response. If the API response indicates the upstream server is answering, proceed to step 2. 2. Invoke the NSX API GET /api/v1/dns/forwarders/vmwNsxTDataCenterDNSId/nslookup? address=<address>. This API request triggers a DNS lookup to the DNS forwarder. If the API returns a valid response, the upstream server may have recovered and this alarm should get resolved within a few minutes. If the API returns a connection timed out response, proceed to step 3. 3. Invoke the NSX CLI command `get dns-forwarder vmwNsxTDataCenterDNSId live-debug server-ip vmwNsxTDataCenterDNSUpstreamIP`. This command triggers live debugging on the upstream server and logs details and statistics showing why the DNS forwarder is not getting a response.