Forum Discussion
Hello, if eas.domain.com is you current application name, then domain.com is your domain.
-
you don't create a A record for eas.gtm.domain.com, as this is the name you want GTMS to dynamically resolve.
-
the sol could translate in you use case to :
In the domain.com zone configuration you add
gtm IN NS gtm1.domain.com. IN NS gtm2.domain.com. <- this is declaring a subzone called gtm with authoritative ns gtm1 and gtm2 belonging to zone domain.com
gtm1.domain.com. IN A 192.168.101.254 <- you add two A records in zone domain.com to declare both GTM
gtm2.domain.com. IN A 192.168.102.254
With GTM global load balancing you don't load balance request to GTM, that you don't really care as they we will be synchronized on configuration side and can easily support load. By declaring that they are authoritative for subzone gtm.domain.com you make sure they receive DNS request for your new alias eas.gtm.domain.com. When they receive the DNS request they will apply the lb algorithm accordingly to their config to resolve the request with either two IPs that you defined, one per Datacenter.