Forum Discussion
They do have some dependency, as when you create a wide IP, the system will add a zone and resource records automatically in BIND.
The other way around is not true, as zones or resource groups created in BIND, editing BIND files manually or via ZoneRunner, will not create any configuration related to wide IPs.
As I explained, ZoneRunner is just a front end for BIND, so BIND is the one that processes traffic.
If you change the word ZoneRunner to BIND in your text, yes, it is the traditional DNS server.
BIND will use the same listener IP as GTM (wide IP).
The listener in this context is just like an IP in a server, the server needs an IP to receive traffic, and that is what the listener is for, to receive DNS traffic, either to GTM (wide IP) or BIND.