World of EUC

Users need to be able to reach the datacenter-specific DNS names. Consider configuring active/passive for those DNS names in case Gateway is down in one datacenter but the farm is still up.

thanks carl so the new datacenter specific names <http://gatewaynl.corp.com|gatewaynl.corp.com> and <http://gatewayuk.corp.com|gatewayuk.corp.com> have to be in public DNS and added as a SAN on the existing ssl cert with the existing gslb name <http://gateway.corp.com|gateway.corp.com> if i am not planning on using gslb for the new datacenter specific names? ill look into the active/passive gslb config for the new datacenter specific names as you make a good point if not using gslb A/P for the new names

<@UM531NUFJ> if i am to use gslb in A/P config for these datacenter specific names i presume would need four gslb vservers per datacenter x2 primary x2 backup for uk and for nl as i got adns in both datacenters.  The relevant gslb domain would then be bound to the primary gslb vserver for the specific datacenter eg <http://uk.gslb.corp.com|uk.gslb.corp.com> bound to the primary gslb vserver that contains uk gslb service and <http://nl.gslb.corp.com|nl.gslb.corp.com> bound to the primary gslb vserver that contains nl gslb service this correct ? i have the zone <http://gslb.corp.com|gslb.corp.com> delegated rather than individual records

Yes to all questions. :slightly_smiling_face:

I got round to implementing this i went with the GSLB  Active/Passive route for the datacentre specific names. OGR works really well really impressed with it