Forum Discussion
NimbostratusDNS Persistence in GTM
Hi
We are planning to setup an Active / Active DC for our Website. All inbound traffic to our website is from AKAMAI edge servers. our requirement is to do the load balance of these inbound traffic across 2 DC (50-50% load sharing). Also we want to have a DNS persistence.
The problem what I see in this solution is, the AKAMAI has N number of Edge servers. A single user session would be load balanced within AKAMAI cloud and will take a different Edge server to reach our web servers. In this case, even if I enable the DNS persistence in GTM I don't think so it will work as the source is going to be changed every time and that will break the user session.
As anyone deployed the similar kind of solution to tackle this kind of DNS persistence issue? If so, would you please advice me how to achieve this.
Thanks
1 Reply
Kevin_Davies_40Nacreous
Each source will naturally persist when it looks up the destination URL. As long as the connection stays active it the resulting IP address on the Edge server will not change, it will only look it up once. The 50/50 occurs when the GTM first hands out the IP address to the Edge server. Each alternate request will get the other DC address. There is no dependancy on source addressing unless you use topology based load balancing.
