For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

edgar_jacome_16's avatar
edgar_jacome_16
Icon for Nimbostratus rankNimbostratus
Jul 25, 2014

load balance Sub Domain, GTM, and Exchange 2013

Hey Folks,

 

I'm a noob when it comes to NS management, and was hoping y'all could help clear the air on a few assumptions. I'd like to load balance our external published eas.domain.com to two GTM's that are in different DC's. The NS server managing eas.domain.com is run by another team including their own NS.

 

Per the article below it appears I can still accomplish load balancing (active\active) if I convert eas.domain.com to a CName which resolves to the subdomain eas.gtm.domain.com that my GTM servers would be authoritative over. Ok that's the extent of what I understand is required. What I'm not clear about is what's actually involved\created on my NS teams side to make this happen.

 

Questions:

 

  1. Is an A record created for the subdomain eas.gmt.domain.com and if so what IP is that resolving too (one of the two GTM servers?).
  2. Article mentions create an A record for the two GTM's, which I'm assuming will be gtm1.eas.domain.com and gtm2.eas.domain.com or gtm1.gtm.eas.domain.com and gtm2.gtm.eas.domina.com?

Trying to wrap my head around how is the client (aka mobile device) aware\presented with both GTM's for load balancing? I appreciate if some one can outline with a few details for my better understanding of this process.

 

http://support.f5.com/kb/en-us/solutions/public/0000/200/sol277.html

 

Edgar

 

availability
BIG-IP Access Policy Manager (APM)
BIG-IP DNS
deployment
design
security

1 Reply

  • Arnaud_Lemaire's avatar
    Arnaud_Lemaire
    Icon for Employee rankEmployee
    Jul 28, 2014

    Hello, if eas.domain.com is you current application name, then domain.com is your domain.

     

    1. you don't create a A record for eas.gtm.domain.com, as this is the name you want GTMS to dynamically resolve.

       

    2. 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.