NimbostratusIt is becoming a contentious issue of f5 support personnel not supporting BIND, though configured and installed by f5 consultants? What is the best way to permanently disable BIND so that no-one can use BIND feature and only stick with GTM DNS has to offer?
Thanks,
Nimbostratus
NoctilucentYou can disable BIND in the DNS profile applied to your listener. Just set 'Use BIND Server on BIG-IP' to disabled.
ZoneRunner will still show up in your GUI though. Suppose you could stop the zrd and named services, though that may cause other problems.
Packaging BIND with your product and then refusing to support it is frustrating though. Happened to us as well.
NimbostratusSo that means zrd is supported but bind (named) is not?
NoctilucentZoneRunner is essentially the graphical interface for BIND. In my experience, the level of BIND support that we've gotten has been dependent upon the support engineer and their knowledge of it.
I heard a couple of years ago that BIND might be removed from GTM, but that was only rumor. I've not heard any official roadmap for it.
NimbostratusCory, you are right - the support and to what extent you are brushed aside depends on support engineer. I think we are reaching a conclusion here i.e. Disabled named service, disable bind in the dns profile. Thereafter whatever is left is all f5 derived code and it should be supported, which include the bind derivative zonerunner. This has been very helpful.
Nimbostratus