Our customers have two outbound lines, each with a GTM and two GTMs in a sync group.
When the other line is dropped, the client DNS still resolves to the old address.
This may be related to local DNS. Does F5GTM have any mechanism for customers to quickly resolve to a new address? We tested it for about 5 minutes, or the old address that was resolved, causing the app to be inaccessible.
Default TTL in wide ip is 30 seconds to force client to send a new request.
Browsers will use same server ip until tab closed or page refreshed.
If you want the browser to fallback to other ip, you can configure 2 answers per request in wide ip or pool!
Does the local DNS set a longer cache time and cause the parsing to be incorrect?