CNAME Monitoring

Hi srivatsavat92,
We do this to provide access to cloud-specific workloads that need access to a service. We use both GTM and LTM for this solution.

Wide IPs-
cloudagnosticname.example.com, type CNAME
cspAname.example.com, type A
cspBname.example.com, type A

Pools -
cnpool_cloudagnosticname { type CNAME, members are Wide IPs cloudproviderAname.example.com & cloudproviderBname.example.com }
vspool_cspAname { type A, member is VS for service in cloudproviderA }
vspool_cspBname { type A, member is VS for service in cloudproviderB }

Wide IP cloudagnosticname.example.com --> CNAME pool cnpool_cloudagnosticname

CNAME pool cnpool_cloudagnosticname --> Wide IP cspAname.example.com & Wide IP cspBname.example.com

Health of the two members of cnpool_cloudagnisticname is determined by the health of the two Wide IPs.

Wide IP cspAname.example.com --> A pool vspool_cspAname
Wide IP cspBname.example.com --> A pool vspool_cspBname

Federated LTMs provide health information on the VSs back to the BIG-IP DNS cluster. As long as the VS is up, the cloud specific Wide IP is up and the member of the CNAME pool is up as well. If a VS goes down, the cloud specific Wide IP goes down, as does the member of the CNAME pool. The cloudagnosticname.example.com Wide IP only ever hands out 'healthy' CNAMEs.

You could do this without using LTMs to provide the health information, you would just need to configure server and virtual server objects that correspond to the hosts that the cloud specific Wide IPs represent and monitor them from your BIG-IP DNS cluster directly.