Description of problem:
system-config-bind modifies zones by rewriting their zone files. Bind,
however, manages dynamic zone files by itself. Bind refuses to load if a zone
file was changed while it was down, and writing zone files managed by bind
while it is up will likely cause immediate corruption.
Version-Release number of selected component (if applicable):
(haven't tested since I'd like to keep my server working, but numerous
attempts to edit zone files for dynamic zones have taught me to use nsupdate)
Steps to Reproduce:
1. Edit a dynamic zone (in /var/named/data)
2. Restart bind
3. bind won't load the changed zone.
Using dynamic updates for *all* zones seems a much better solution anyway:
multiple admins can change entries in the same dynamic zone without
corruption. Editing text files may be fun for people, but machines aren't so
good at it.
Yes, s-c-bind should handle dynamic zones more gracefully - at least by doing
an 'rndc freeze -> ( modify zone file ) -> rndc unfreeze' , if not actually
providing an interface to nsupdate. In the long term, a GUI interface to
nsupdate allowing management of remote zones would be a desirable and is
planned. I'll implement the freeze/unfreeze for dynamic zones with the
next release. Meanwhile, a simple workaround is to select 'Server -> Stop',
then edit the dynamic zones, and do 'Server -> Start'. In my experience,
most BIND users do not use dynamic zones at all, so forcing all zones
managed by s-c-bind to be dynamic is not an option.
Now fixed with system-config-bind-4.0.0-41.fc5, to be released to FC-5
system-config-bind-4.0.0-41.fc5 has been pushed for fc5, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report.
I tested it and it's working, but I still think an nsupdate style solution
would be much better.