Manually refreshing DNS entries

The public DNS entries are updated automatically during Data Lake and Cloudera Data Hub cluster operations, such as starting the cluster and repairing the cluster. In case the DNS entries are not refreshed automatically, there will be error events in the cluster details page and also in CDP CLI. As the DNS failures are not considered as critical failures, the cluster health can change back to healthy state for the start operation, but the cluster creation and repair fails. The DNS entries must be updated to avoid errors when accessing the Cloudera services externally.

The internal and external domain names (FQDNs) are the same. These names are resolved by FreeIPA in the environment. However, in case there is no specific DNS configuration for client applications outside the Cloudera environment, the default method to access an instance is by resolving the FQDN through public DNS servers.

In case the public DNS entries are not updated, the client application cannot connect to the Data Lake or Cloudera Data Hub services, because the application cannot resolve the hostnames.