Description of problem:

In an attempt to get a dnssec-conf package that did not cause bug#505754 I went ahead and upgraded to the dnssec-conf that's present in rawhide (I'm currently running Fedora 11).

While this *DID* fix the issue found in bug#505754, it however caused massive formatting and structural changes to the named.conf file in question.  It removed whitespace that was there on purpose, changed comment structuring, added extraneous blocks, etc.

My original named.conf file was 486 lines long, had a readable formatting and was easily understood

The new Named file is 501 lines long and has the formatting completely changed and made nigh unreadable.

The patch difference between the two results in a uniform (-u) diff of 629 lines long.

Examples 1 changes:
-------------------------------------------------------------------------------
-               127.0.0.1;                      # localhost
-               149.20.20.144;                  # ns2.kernel.org (odin1) - new - san jose
+               127.0.0.1;
+               
+                       # localhost
+               149.20.20.144;
+               
+                       # ns2.kernel.org (odin1) - new - san jose
...

Example 2 changes:
-------------------------------------------------------------------------------
 };
-
 // reduce log verbosity on issues outside our control
 logging {
-       category lame-servers { null; };        # Not interested in lame remote servers
-       category resolver { null; };            # Not interested in broken remote servers
-       category lame-servers { null; };        # Not interested in brokenness
+       category lame-servers {
+               null;
+       };
+       
+               # Not interested in lame remote servers
+       category resolver {

-------------------------------------------------------------------------------

It was bad enough that dnssec-conf couldn't properly patch named.conf but the new version is blatantly unacceptable for these huge changes and what with bind now *REQUIRING* it

# rpm -q --requires bind | grep dnssec-conf
dnssec-conf  
#

it's a little difficult to just remove this and ignore dnssec for the time being, or manually add the dnssec information on our own and not use dnssec-conf

Version-Release number of selected component (if applicable):

1.22-1.fc13

How reproducible:

Always

Steps to Reproduce:
1. have named.conf
2. start named or run dnssec-configure
3. named.conf has been massively altered.
  
Actual results:

hugely reformatted named.conf file.

Expected results:

minimal changes to add *only* the required information for dnssec-conf.  The version from F11 / F12 came closer, it just screwed up on where it added the entries if you have a reasonably complex dns structure.