- in an explicit deployment, a website, or site components load, but consistently take over a minute to do so.
- Website consistently takes a minute to load through ProxySG in an explicit deployment
- DNS record has multiple IP addresses listed
In an explicit deployment, the ProxySG will handle DNS, and some DNS entries have multiple IP addresses listed. What can happen is that if one of the IP's listed on the A record is unreachable, the ProxySG may reach out to it first. If this happens, the ProxySG will wait the traditional tcp handshake timeout time (75 seconds) before trying any addition IP on the A record, thus having the latency but still loading.
This issue can be solved in two ways:
For a temporary fix, policy can be applied to assign the working IP from DNS to the ProxySG, as found here.