Forum Discussion
GTM has some dependencies on the underlying BIND system that is fronted by the Zonerunner utility, which as Leonardo has stated is just a GUI wrapper for BIND. BIND has no dependencies on GTM.
If I have no wideIPs defined, and I have not chosen to use the local BIND instance for anything, then Zonerunner should be completely empty. But let's suppose I add a single wideIP called www.test.local to the GTM config, with a single pool and a single virtual server in that pool with an IP address/port of 10.0.0.101:80.
When that is done, a zone is created in BIND for test.local in the file /var/named/config/namedb/db.external.test.local. with these contents:
[root@ltm3:Active:Standalone] config # cat /var/named/config/namedb/db.external.test.local.
test.local. 500 IN SOA ltm3.test.local. hostmaster.ltm3.test.local. 1 10800 3600 604800 60
test.local. 0 IN NS ltm3.test.local.
ltm3.test.local. 0 IN A 127.0.0.1
www.test.local. 0 IN A 10.0.0.101
And zonerunner will display this zone file like this:
For the details on how the listener processes queries based on the different GTM features you have enabled, see knowledge article 14510.
It is my understanding that the expected behavior is zones/records are created as a result of the wideIP object creation. If this is not what you are experiencing on a particular version of TMOS, then I'd open a support case for clarification. If my understanding is incorrect, please post back here what you learn. Thanks,