Forum Discussion
sathish_2826
Nimbostratus
NimbostratusGTM Wideip and pool persistence
Hi there , please help me understand the gtm wideip and pool persistence, gtm wideip persistence — this tells a specific user how long you will stick with the same pool member for dns queries ...
Simon_Blakely
Employee
Employee> I will likely to get 10.10.10.10 for 1 hr,
The BigIP DNS will still return 10.10.10.10 to your query for 1 hour after the last time you checked.
> but for every 15 seconds a dns requests sends to wideip to see if the member is still active
Your system will cache the DNS result for 15 seconds, and then if you ask for that fqdn again, it will check.
Note: DNS Persistence may not always work the way you expect.
K15594: Overview of BIG-IP DNS persistence
K6082: BIG-IP DNS provides persistence records for a wide IP after a pool or data center is disabled
sathish_2826Nimbostratus
NimbostratusOne another clarification, after setting the wideip persistence TTL to 3600 s, and pool TTL to 15 seconds,
When i access my application in periodic intervals, it just keeps flipping between 10.10.10.10 and 10.10.10.11, these are my LTM vips in the pool.
Tested this multiple times and as you said, it is very inconsistent,
Do you have any other thoughts on this Simon?
- Simon_Blakely
How are you checking resolution?
I would recommend a dig command for the wideIP directly to your GTM listener is the best place to start.
If you use your local device DNS resolver, you may end up going through different LDNSs to the GTM and getting different persistence records.
Remember that the DNS persistence record is for the LDNS that queries the GTM, which probably won't be your own IP address.