Forum Discussion
FFive
Altocumulus
AltocumulusHelp me understand GTM Load Balancing Algorithm and how Topology Records and Topology Regions play i
We have two Topology Regions: Internal space (10.0.0.0/8) and External space (public facing IPs). The GTM is configured with two listeners, one internal-facing the other external-facing The GTM i...
FFiveAltocumulus
AltocumulusHi, Thank you so much for replying!
I am not sure I follow you. We have two IP Subnets or Topology Regions, the external which are the public facing IPs, and the internal which are in our 10.0.0.0/8.
One thing that could resolve the issue with the particular Wide IP is to remove the delegation pointing to the GTM from the Windows DNS server
Ok, so silly question - are you using GTM to host records for your web servers/services.
Or, DNS for your Clients/Servers?
My answer was for web servers, so once you have your wide-ip setup to the DNS name.
You setup a topology, so when the wide-ip gets a request from a certain IP it knows what to do with it.
So if from say a certain range or geo-ip region it can deside which IP's to respond with.
So the topology is for the incoming comms.
Where as the pool, is a list of servers/IP's which the GTM has avaiable to it to choose from when a request comes in.
Really the question is, when a request comes from one of those ranges what do you want to happen?
- FFive
Hi, Thank you again to continue engaging on this topic.
I am using the GTM to host DNS records for web servers/services/apps.
You helped me identify the issue. I have the wrong WIDE IP pool load balancing method as Round Robin instead of Topology. I feel embarrassed that I didn't notice this first. A lesson to look at the easiest possible resolution first instead of the more complicated ones.