The objective is to use the Global Server Load Balancing (GSLB) feature of the NetScaler for multiple backend servers, however, the actual traffic will not be served by the NetScaler and rather should be sent directly to the backend server.

 

---

Instructions

1. Create the GSLB Site(s). If you have just a single site, create a single GSLB Site.

2. Create the GSLB services that would point to the server. In this case since the traffic needs to be sent to the server directly, the GSLB service would not point to any virtual server on the NetScaler.

Note: When we create the GSLB service pointing to the server directly, the state as well as the effective state of the GSLB Service would show down.

We need to bind a monitor to the GSLB service in order to do the health check.
The Effective state in any case will show down because the effective state is derived from the virtual server and not from the server.

3. Add the GSLB virtual server and bind the GSLB Services to it. We would then define the domain for the GSLB.

4. Add an ADNS Service on the NetScaler, if not added already.

Now, when the user would try to access the GSLB FQDN, the NetScaler would simply do the Name resolution. However, since the IP that would be returned to the user would be pointing to the server directly, the user request would be subsequently forwarded to the server and not to the NetScaler.