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

Jason_40733's avatar
Jason_40733
Icon for Cirrocumulus rankCirrocumulus
Apr 08, 2011

GTM Topology Architecture with DNS resolvers

We are implementing GTM and have some general topology rules setup for routing our traffic. Something we have come across, is a potential need for us to route different groups of DNS clients that ar...
config
design
Jason_40733's avatar
Jason_40733
Icon for Cirrocumulus rankCirrocumulus
Apr 11, 2011
That is a good document. It's something we've gone over. Our needs are a bit more in depth than that goes into. It appears that given the behavior of DNS, to accomplish what we wish to do we'll need to point anything that needs a more specific rule directly to the GTM. Which will eliminate part of our deployment simplicity gains by implementing GTM, but its not a huge difference.

 

 

So.... for a general topology set

 

subnet1 -> LDNS1 -> GTM

 

subnet2 -> LDNS1 -> GTM

 

subnet3 -> LDNS2 -> GTM

 

 

Will become this when more specific topology records are needed. It's either that or add more LDNS servers.

 

subnet1 -> LDNS1 -> GTM

 

subnet2 -> GTM

 

subnet3 -> LDNS2 -> GTM

 

 

With subnet2 being the subnet/IP address with specific topology needs.