In a proxied GSLB deployment, which address is used as the source for outgoing traffic when the connection is proxied?

In a proxied GSLB deployment, which address is used as the source for outgoing traffic when the connection is proxied?

• A. LDNS IP Address
• B. Client source IP
• C. Virtual IP
• D. Subnet IP (SNIP)

Answer: (D)

In proxied GSLB, the gateway acts as the intermediary for traffic between clients and the real servers, so it initiates the outbound connections itself. The address it uses as the source for those connections is the Subnet IP (SNIP) assigned to the subnet the servers reside in. This SNIP is the IP the gateway uses to reach the back-end servers, and it’s the source that the servers see, ensuring return traffic comes back to the gateway. The Virtual IP is the front-end address that clients connect to, not the source of the proxied requests to servers. The LDNS IP address relates to DNS resolution, not to the actual proxied traffic. The client’s source IP is only visible to the client; once the gateway proxies the request, the origin servers respond to the SNIP, not to the client’s IP.

In proxied GSLB, the gateway acts as the intermediary for traffic between clients and the real servers, so it initiates the outbound connections itself. The address it uses as the source for those connections is the Subnet IP (SNIP) assigned to the subnet the servers reside in. This SNIP is the IP the gateway uses to reach the back-end servers, and it’s the source that the servers see, ensuring return traffic comes back to the gateway.

The Virtual IP is the front-end address that clients connect to, not the source of the proxied requests to servers. The LDNS IP address relates to DNS resolution, not to the actual proxied traffic. The client’s source IP is only visible to the client; once the gateway proxies the request, the origin servers respond to the SNIP, not to the client’s IP.