How to affect Static persist LB method for GSLB pools

TiborP So typically with large providers of a caching NS they will typically the users query to them is directed using anycast or some variation of that so that the users request is directed to the closest device to them. This is a guess but most likely what's happening is the source IP of the cache NS is not the same as the IP that the user is querying which results in the user being sent to multiple locations because the cache NS is querying from multiple source IPs. I have something similar behavior when a firewall utilizes FQDNs to allow users out of or into an environment but the client has a different DNS server they query which results in the traffic being blocked. In your case the GTM is seing the source of the DNS request as different IPs which results in persistence not functioning correctly for the end user. You might consider running a tcpdump on the GTM or turning on some logging so you can validate the users DNS query and where it's coming from because they most likely are changing on each DNS query.