Rate this Article:
You must be signed in to rate again
Article Feedback Print View
Alternate Languages: N/A

When Using Proximity-based Global Server Load Balancing, Can There be Significant Discrepancies Caused by Using the Local Domain Name System to Determine Where a Client is Rather than the Client Itself?

Document ID: CTX109859   /   Created On: Jul 7, 2006   /   Updated On: Jul 7, 2006
Average Rating: not yet rated

Q: When using proximity-based Global Server Load Balancing (GSLB), can there be significant discrepancies caused by using the Local Domain Name System (LDNS) to determine where a client is rather than the client itself?

A: Yes. However, the difficulty is that when clients make Domain Name System (DNS) requests, they typically do so to their LDNS server. Most LDNS servers are configured to do recursive lookups, which means the NetScaler system never sees the actual client IP address, only the LDNS address.

While there are known exceptions (AOL being the typically cited case since all users call on the same set of LDNS servers in Reston, Virginia, regardless of their location), the LDNS method works well for most users.

Note: The AOL citation is actually invalid. Because AOL's HTTP proxy farm makes all HTTP requests come out of Reston, Virginia, having the LDNS servers in Reston produces the fastest response times for AOL users.


Search
Knowledge Center
XenApp
XenApp Plugins (Clients)
XenServer
XenDesktop
NetScaler Application Delivery
Access Gateway
EdgeSight
Provisioning Server
WANScaler
Password Manager
Browse and search our Beta library. Planning, installation, maintenance, and readme info merged into one collection.