GSLB and ADNS Support Across Different Traffic Domains on NetScaler

GSLB and ADNS Support Across Different Traffic Domains on NetScaler

book

Article ID: CTX202277

calendar_today

Updated On:

Description

GSLB and ADNS in the present release of NetScaler are not aware of Traffic Domains. So GSLB configuration in the default Traffic Domain is available on the other Traffic Domains as well.

If GSLB configuration needs to be shared across all traffic domains then GSLB methods Static Proximity and Round Trip Time does not work.

Resolution

Two ADNS services with two Traffic Domains is not a supported configuration with GSLB methods - Static Proximity and Round Trip Time (RTT). When different Traffic Domains are in use, the same GSLB configuration cannot be effective in both the Traffic Domains. This is currently not possible since we do not support Traffic Domain for GSLB. Even though GSLB is configured in default Traffic Domain, since ADNS is not Traffic Domain aware GSLB domain will be available in all Traffic Domains. This might not be desirable for all scenarios. If this is a desirable scenario then the GSLB methods like Static Proximity and RTT will not work.

The workaround in this scenario is to use GSLB methods other than RTT and Static Proximity.

Refer to the following Citrix Documentation for the list of all the GSLB methods available - Changing the GSLB Method.


Problem Cause

GSLB works only in default Traffic Domain which is TD0 and it is not aware of any other Traffic Domains such as TD1.

GSLB and ADNS are not supported fully for Traffic Domain. GSLB is only allowed to be added to default Traffic Domain TD0.

To support Static Proximity andĀ RTT based GSLB the entire GSLB functionality will have to be made Traffic Domain aware which is not possible at present.

Issue/Introduction

GSLB setup on NetScaler does not work when GSLB control (MEP and probes) is in default Traffic Domain TD0 and the ADNS service is in another Traffic Domain TD1.