Symptoms

FQDN monitors may be stuck in status 'fqdn-checking' in environments with an unreliable DNS server, such as when DNS queries frequently timeout.

Impact

FQDN monitor status remains in 'fqdn-checking', even after the DNS server again becomes available. Monitors may eventually become "un-stuck", and monitors will (correctly) reset upon system restart.

Conditions

FQDN monitors are configured; and the DNS server used to resolve FQDN nodes is intermittently available, leading to occasional timeouts to bigd from DNS queries.

Workaround

Although there is no workaround, FQDN monitors are not recommended for use in environments where DNS servers are unreliable.

Fix Information

None

Behavior Change