var/log/proton/nsxapi.log file indicate issues with DNS:Example 1 - DNS takes long time to respond
HH:MM:SS.sssZ INFO http-nio-127.0.0.1-####-exec-6 Utils #####- [nsx@#### comp="nsx-manager" level="INFO" reqId="########-####-####-####-############" subcomp="manager" username="admin"] Executing script: /opt/vmware/nsx-common/python/nsx_utils/ip_utils.py -d4 ##-nsx-manager.systems.##.####
HH:MM:SS.sssZ INFO http-nio-127.0.0.1-####-exec-6 Utils ##### - [nsx@#### comp="nsx-manager" level="INFO" reqId="########-####-####-####-############" subcomp="manager" username="admin"] getIpv4FromFqdn(): script returned Ipv4: ##.#.#.##
We can observe above that ip_utils.py took 15 seconds to respond.Example 2 - DNS does not respond :
HH:MM:SS.sssZ INFO EventSource-1-2 Utils #### - [nsx@#### comp="nsx-manager" level="INFO" subcomp="manager"] getIpv4FromFqdn() invoked with FQDN ;; communications error to ##.##.##.##53: timed out
VMware NSX 3.x,4.x
Problems with DNS configuration can lead to this issue. For example, DNS configuration is pointing to a server that does not exist or is unavailable.
Access to the NSX-T Manager command line with admin user
get name-serversset name-server <New-DNS-server>del name-server <Old-DNS-Server>Note: This configuration must be applied to all NSX-T Manager nodes.
If this issue occurs even while a secondary DNS is configured then please see NSX management cluster DNS issues observed while secondary DNS is functional and present.
If you believe you have encountered this issue and need assistance in diagnosing the root cause, please open a support case with Broadcom Support and refer to this KB article.
For more information, see Creating and managing Broadcom support cases.