Citrix ADC support configuring GSLB in an ADC cluster, and there's some known issues in this specific configuration.

1.  After GSLB force sync, Slave site GSLB node group configuration lost .
   • In a GSLB configuration Force Sync, the GSLB site where force sync start is called a Master site, the remote site receiving gslb configs is called a Slave site. The GSLB related Cluster Node Group configuration on Slave site will lost after force sync, which may cause GSLB service DOWN on slave site.
2.  "add server ..." commands can be seen as GSLB running config in specific scenarios.
   • When users adding a remote site GSLB services, users may find "add server " command listed as GSLB running config, which is not expected and may cause issue in future GSLB config syncs.

• Users must manually add GSLB node group configuration again after GSLB force sync. For details of configuration in need, please refer to: 

• As this issue only happens on specific GUI configuration. Please use "New Server" Option when adding remote GSLB Services from GUI:

• Listed issues are all in Citrix ADC engineering team's scope and may be fixed in future release.

Problem Cause

1. Slave site GSLB node group configuration lost after GSLB force sync.

• GSLB Force Sync will clear all GSLB Slave site configuration then apply the master GSLB configuration. Which will cause nodegroup binding configuration lost. This is currently a product limitation on Citrix ADC due to GSLB's nodegroup requirement in Cluster, known as NSHELP-26235. 

2. "add server ..." commands can be seen as GSLB running config.

• "add server" command will be included in GSLB running configuration only when users firstly add remote GSLB services's IP in Traffic Management > Load Balancing > Servers, then add GSLB service on GUI with "Existing Servers" option. Adding GSLB Services from CLI won't trigger this issue. This GUI issue is known as NSHELP-28990.