Many people have mentioned (via bugzilla) the policy change whereby BIND is
now off by default. I do not have a problem with the policy change. The
issue is when I apply the RPM as an update to a system already running
BIND, the RPM should note that BIND is enabled and not disable it. If a
person makes the choice to run BIND by enabling the service, then
subsequent RPMS should either silently honor that choice, or if this is not
possible, issue a warning stating that the service has been disabled.
If the RPM cannot be made smarter (but we all know that it can), then
minimally the documentation that suggests the installation of the RPM
should note that BIND will not be started on the next reboot.
We'll change it if we need to issue another security update.
Releasing a new RPM now would cause more confusion than it would help.