Forum Discussion
NimbostratusGTM DNS Response not reflecting GTM WideIP/Pool Status
GTM pool Preferred and ALternate LB Method is set as Round Robin, Fallback Method is set as None.
Application is not yet live, so LTM virtual server is down, obviously the GTM pool and wideip as well down.
Unexpectedly, GTM is responding for the domain requests with the respective GTM pool member/virtual server IPs.
What will be reason for this ? Is it the expected behavior?
Below is the similar configuration deployed;
gtm wideip abc.xyz.com {
persistence enabled
pools {
abc.xyz.com_pool {
order 0
}
}
ttl-persistence 28800
}
gtm pool abc.xyz.com_pool {
fallback-mode none
members {
/Common/DC1_LTM_Server:abc_xyz_com_443 {
order 0
}
/Common/DC2_LTM_Server:abc_xyz_com_443 {
order 1
}
}
ttl 120
}
Both the GTM members DC1_LTM_Server:abc_xyz_com_443 and DC2_LTM_Server:abc_xyz_com_443 are down as the application is not live yet.
AneshCirrostratus
Fall Back method should be set Drop, else the DNS query will be answered by BIND
Stanislas_Piro2Cumulonimbus
@Nesh,
there is no Drop method.
must not forward request to BIND and is like a DROP.None@Narendren S
If there is one LB method with option
and previous methods doesn't match (pool members down, topology method doesn't match, ...), it will use local Bind to answer DNS request.Return do DNSIf you have more than 1 answer, this is an answer from BIND and not GTM.