Return
-
Title
FglAMs not reconnecting after moving FMS to new host (CNAME) - Is the DNS information cached? -
Description
We moved our FMS to a new host. All of the FglAM are configured to use CNAME (CNAME is a host alias for DNS). The FglAMs were not restarted, but it was expected that the FglAMs would seamlessly connect to the new FMS. Do they require a restart?
-
Cause
Issue is identified as FAM-3067
-
Resolution
In the version of FglAM (5.5.4), it will cache all DNS name resolutions for the duration of the VM's runtime.
As a result, they will need to restart the FglAM instances in order to pick-up the new DNS entries.In an upcoming release of FglAM, we have revised this configuration to now only cache the resolved names for 30 seconds.