8.2.2 -> 8.2.3 Zone File Problems
James Snow
snow at teardrop.org
Mon Jan 29 20:28:40 UTC 2001
I've been referred to RFC1035 which states:
The format of these files is a sequence of entries. Entries are
predominantly line-oriented, though parentheses can be used to
continue a list of items across a line boundary,
My thanks to the referring party.
-Snow
On Mon, Jan 29, 2001 at 03:12:32PM -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
More information about the bind-users
mailing list