Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP GTM
Known Affected Versions:
10.0.0, 10.1.0, 10.2.0, 10.2.1, 10.2.2, 10.2.3, 10.2.4, 11.0.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.5.1 HF1, 11.6.1 HF1, 11.5.1 HF2, 11.6.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.6.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1
Fixed In:
11.6.0
Opened: Nov 18, 2013 Severity: 3-Major Related Article:
K15072
The GTM global setting "cache-ldns-servers" can erroneously be set to "no" when a Wide IP is configured with "persistence enabled."
Persistence will not work correctly if "cache-ldns-servers" is turned off.
The GTM global setting "cache-ldns-servers" can erroneously be set to "no" when a Wide IP is configured with "persistence enabled."
Set the GTM global setting "cache-ldns-servers" to "yes" if any Wide IPs have persistence enabled. This is only necessary if the cache is turned off after persistence is enabled as enabling persistence automatically turns the cache on.
The BIG-IP GTM Cache Local DNS Servers global variable (cache-ldns-servers) is no longer erroneously disabled when persistence is enabled for a wide IP.