From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3)
Description of problem:
As the named.conf file the current bind configuration, it should not
get replaced when updating the package (thus causing some software to
fail because the config file is reset to a caching-only name server!)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install bind-chroot
2. change named.conf
3. update to bind-chroot-9.2.4-2
Actual Results: current (correct) config file will get renamed to
named.conf.rpmsave, standard named.config is now the default config
file -- your software breaks :-(
Expected Results: store new named.conf as named.conf.rpmnew, do not
touch old named.conf
This is not an issue with the bind-* package, but with the
No bind-* package supplies any named configuration files,
unless none exist on the system, when only rndc.conf, rndc.key,
and the bare minimum named.conf sufficient to allow named to
run are installed.
When you install the 'caching-nameserver' package, which consists
entirely of the named configuration files, you are asking for
a caching-nameserver named configuration to be installed.
If you want to customize your named configuration files, and run
something other / more than a caching-only nameserver, uninstall
the caching-nameserver package.
Unless caching-nameserver replaces any existing named configuration
files on installation / upgrade, there would be no way of guaranteeing
after installation that a caching-nameserver was in place afterwards,
and no way of upgrading these configuration files.
Hence this bug is being closed as 'NOT A BUG'.