GTM Split DNS - Topology Records or Zone Views?
I'll be setting up a new Datacenter and running GTM between LTMs at each DC. When the need arises, I need internal clients to resolve internal VSs for a WIP, and external clients should get an external VS (either a NAT or a real public VS in a DMZ). My setup will be fairly simple, most applications are a single VS/Port, and either need to be active/active or active/standby across the two DCs.
What is everyone doing for GTM Split DNS? I have seen the F5 document regarding setting up topology records on the WIP to select a pool based on source IP, and I've also seen references to using Zone Views. Which is preferred for ease of setup/use as well as flexibility?
With Topology records, it seems to me that you lose a bit of flexibility because you have to dedicate your WIP load balancing to just doing Split DNS, and have to do all your load balancing at the pool level? Maybe not much of an issue, especially in a fairly simple setup. Possibly some duplication of work depending on the setup, having to create an Internal and External Pool and VS for every app?
Views seem to decouple Split DNS from the WIP/Pool/VS process, but it seems like it is going to be more trouble to manually manage the records in ZoneRunner? Specifically when you add a new WIP, it automatically adds a record in ZoneRunner, but it seems to add it to the default or highest ordered zone? So if that's the internal zone, it adds even external records to it or vise-versa? Then you have to go in and manually edit the records to fix it, and are those manual changes ever overridden in the future? Or is there a way to direct the records appropriately, or disable automatic record creation to force you to add it manually?
Thanks.