Questions from our Customer Training Course:
Health Checks in a multitenancy environment – how it interfaces with AX when recovering environment is not active? How to reduce the latency for failover?
How to mitigate services for Dynamic DNS in a GSLB environment? Are there any benefits for DDNS in a GSLB environment?
Thanks for posting the students inquiry on vADC. There are two GSLB questions requested and I will response to them individually. Health Checks in a multitenancy environment – how it interfaces with AX when recovering environment is not active? How to reduce the latency for failover?
Response: GSLB recovers based on the GSLB status messages that are transmitted across GSLB site/s and controller. To reduce and expedite the latency for failover to an UP state you can configure the “GSLB Update Interval” values to a more aggressive number. The default value of the GSLB Update Interval is at 30 minutes but if plan to change the following value you must account the following to avoid false positive status; network latency and number of sites you are checking for status messages.
How to mitigate services for Dynamic DNS in a GSLB environment? Are there any benefits for DDNS in a GSLB environment?
Response: It is not possible to mitigate DDNS services in a GSLB environment as GSLB can support both IP and FQDN addresses. Per my response above, there is no significant advantage other than the common benefits of A10 GSLB implementation such as:
1. Support multiple service providers with one single domain
2. No GSLB licensing required
3. Load balance between service providers include failover, weight and bandwidth cost.
4. Integrate DDNS into enterprise DNS environment
5. Easy to upgrade to DNSSEC if service provider doesn’t support it yet
Hello Genard Garcia,
Your statement about default “GSLB Update Interval” value of 30 min is slightly contraversal to documentation’s one:
“GSLB Protocol Update Interval
Specifies the number of seconds between GSLB status messages.
1-300 seconds
Default: 30 seconds”