8.2.2 -> 8.2.3 Zone File Problems

[Forrest Aldrich]

I too was bitten by this, with 100s of zones affected.

Seems the parsing should "know" to recognize your example.  Mine was 
different, where I had:

         @ IN SOA ns.domain.com. some.domain.com.
                 (2000010101
                         ...)

But still similar.

I'm told that 8.2.x had a bug that allowed invalid SOA's (as we've showed 
here) to be accepted.

*shrug* I would think that the example should still be valid, because it's 
following a format, similar to something in the named.conf where you can 
have the braces on any part of the line:

         config-directive        {       data;   };

or

         config-directive {
                                 data;
         }

Shouldn't really "matter" all that much.



_F


At 03:12 PM 1/29/2001 -0500, James Snow wrote:

>In response to the latest BIND8 vulnerability I upgraded my nameservers
>from 8.2.2 (p5, I think) to 8.2.3 and my zone files were all rejected.
>
>The cause of this was the positioning of the leading parenthesis after
>the SOA line. For example:
>
>         @ IN SOA ns.domain.com. snow.domain.com.
>         (    2001012901
>                 ... )
>
>This was rejected. I had to move the leading parenthesis up one line to
>get them working again:
>
>         @ IN SOA ns.domain.com. snow.domain.com. (
>                 2001012901
>                 ... )
>
>I don't have a preference for either one but I am curious to know if
>there is a reason for this. (Other than just an oddity in parsing the
>zone file.)
>
>I have relatively few zone files to deal with so this was trivial to fix
>by hand. If you have more than a few you'll probably want to script a
>fix for this before you update.
>
>
>-Snow