Missing DNS Entry For Manager FQDN alarm when RFC 2317 DNS in use
search cancel

Missing DNS Entry For Manager FQDN alarm when RFC 2317 DNS in use

book

Article ID: 405861

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • You have implemented RFC 2317 type DNS, and you are receiving alarms from the NSX manager.
  • After the changes, you are receiving the following error related to missing FQDN. 
  • In the log /var/log/phonehome-coordinator/phonehome-coordinator.log of the impacted manager(s), you see the following log entries:
    <Time stamp> FATAL pool-91-thread-1 MonitoringServiceImpl 76524 MONITORING [nsx@6876 alarmId="########-####-####-####-##############" alarmState="OPEN" comp="nsx-manager" entId="########-####-####-####-##############" errorCode="MP701099" eventFeatureName="manager_health" eventSev="CRITICAL" eventState="On" eventType="missing_dns_entry_for_manager_fqdn" level="FATAL" nodeId="########-####-####-####-##############" subcomp="monitoring"] The DNS configuration for Manager node <name> (########-####-####-####-##############) is incorrect. The Manager node is dual-stack and/or CA-signed API certificate is used, but the IP address(es) of the Manager node do not resolve to an FQDN or resolve to different FQDNs.

Environment

VMware NSX
VMware NSX-T Data Center

Cause

RFC 2317 DNS is currently unsupported by NSX.

Resolution

Leverage a compliant DNS implementation.

Additional Information

Verify the DNS resolution is working as expected using the following command. 

dig -x <NSX Manager IP> +short | sed 's/\.$//g' | grep "\." | head -1
 
Powered by Wolken Software