GSLB static proximity handing out sites not close to the requesting client
Article ID: CTX218985
Updated On:
Description
We are seeing clients in APAC region getting handed GSLB service IPs for US data centers, leading them to conclude GSLB static proximity isn't working correctly. The same is occurring for clients in the US getting directed to APAC data centers.
Resolution
The GSLB static proximity issues were resolved by performing the below corrective actions. Note, MIR cannot be enabled simultaneously with EDNS0.
- Disabling MIR (multi-IP response) on the GSLB virtual server.
- Enabling EDNS on the GSLB virtual server. This allows the GSLB decision to leverage the client IP subnet information (EDNS header in the DNS request from the LDNS server) which allows an accurate proximity decision.
Problem Cause
Customer was using centralized DNS providers such as Google DNS which can result in LDNS servers which aren't geographically close to the client. GSLB static proximity makes a decision based on the LDNS IP so for example, a client in APAC could be given a LDNS server close to the US which results in GSLB handing out a US data center versus an APAC one.Issue/Introduction
Customer seeing clients in APAC region getting handed GSLB service IPs for US data centers, leading them to conclude GSLB static proximity isn't working correctly. The same is occurring for clients in the US getting directed to APAC data centers.
Additional Information
Refer the below URL for more information on EDNS0 -
http://docs.citrix.com/en-us/netscaler/11-1/gslb/configure-EDNS0-client-subnet.html
http://docs.citrix.com/en-us/netscaler/11-1/gslb/configure-EDNS0-client-subnet.html
Was this article helpful?
Yes
No
Powered by
