NSX Edges report "Unknown" State in NSX UI

Products

• VMware NSX

Issue/Introduction

• NSX Edge reports "Unknown" state in the NSX UI.
• Edge to Manager (MPA) connectivity reports down.
• Ping test from the Edge node to the Manager node fails when using the FQDN.
• Logs from /var/log/syslog
  2025-09-16T08:13:12.610Z <Edgename> NSX 5131 - [nsx@6876 comp="nsx-edge" subcomp="nsx-proxy" s2comp="nsx-net" tid="5155" level="WARNING"] StreamConnection[32100 Resolving to ssl://<Manager Name>:1234 sid:-1] Couldn't resolve 'ssl://<Manager Name>:1234' (error: 2-Host not found (non-authoritative), try again later)
2025-09-16T08:13:12.610Z <Edgename> NSX 5131 - [nsx@6876 comp="nsx-edge" subcomp="nsx-proxy" s2comp="nsx-net" tid="5155" level="WARNING"] StreamConnection[32100 Error to ssl://<Manager Name>:1234 sid:-1] Error 2-Host not found (non-authoritative), try again later
2025-09-16T08:13:12.610Z <Edgename> NSX 5131 - [nsx@6876 comp="nsx-edge" subcomp="nsx-proxy" s2comp="nsx-rpc" tid="5155" level="WARNING"] RpcConnection[32100 Connecting to ssl://<Manager Name>:1234 0] Couldn't connect to ssl://<Manager Name>:1234 (error: 2-Host not found (non-authoritative), try again later)
2025-09-16T08:13:12.610Z <Edgename> NSX 5131 - [nsx@6876 comp="nsx-edge" subcomp="nsx-proxy" s2comp="nsx-rpc" tid="5155" level="WARNING"] RpcTransport[0] Unable to connect to ssl://<Manager Name>:1234: 2-Host not found (non-authoritative), try again later

Environment

VMware NSX

Cause

Edge devices are configured with invalid or unreachable DNS servers. This prevents successful FQDN resolution of the NSX Manager.As a result, MPA connectivity fails and edges appear in an unknown state.

Resolution

• Verify  the current DNS configuration using the command from Edge node CLI 
  • get name-servers
    
    
• Delete the incorrect name server 
  • del name-server <dns-serverIP>
    
    
• Update the name server configuration from CLI
  • set name-servers <dns-serverIP>
    
    
• Post checks
  • Run get name-servers to confirm changes.
  • Run nslookup <nsx-manager-fqdn> to validate name resolution.
  • Run get manager to confirm Manager connection.
  • Verify in the NSX UI that Edge devices show a "Success" state.

Note: Name server updates made in the UI will not be applied to the Edge  because the Manager-to-Edge connectivity is unavailable.