There has been one other report of this log message recently and in the end it turned out that the associated service was going from alive to dying state, then back to alive again. This indicates intermittent keepalive failures for the service, but not enough to take it down. For a service in dying state, the dns record will go down as you are seeing.
The resolution was to determine why the service sometimes did not respond to keepalives. A possible workaround is to alter the keepalive parameters for the appropriate service, to keep it in alive state. I would suggest using a sniffer to check the service response to keepallives.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
Introduction Prepositioning is a powerful tools on the WAAS platform but
it is not always easy to figure out why your jobs are failing when
trying to retrieve the files.Here is a method that should help you to
figure out the reason why they are not succes...