[34274] in North American Network Operators' Group
Re: [NANOG] Re: Reasons why BIND isn't being upgraded
daemon@ATHENA.MIT.EDU (Pete Ehlke)
Thu Feb 1 22:34:01 2001
Date: Thu, 1 Feb 2001 19:30:41 -0800
From: Pete Ehlke <pde@ehlke.net>
To: Pim van Riezen <pi@vuurwerk.nl>
Cc: nanog@merit.edu
Message-ID: <20010201193040.A17115@ehlke.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <Pine.SGI.4.30.0102020343160.115762-100000@jones.lab.madscience.nl>; from pi@vuurwerk.nl on Fri, Feb 02, 2001 at 03:54:10AM +0100
Errors-To: owner-nanog-outgoing@merit.edu
Pim van Riezen (pi@vuurwerk.nl) said, on [010201 18:58]:
>
> Parsing human input isn't hard, you know. Robustness doesn't come from
> being anal. If there's a bogus entry, reject the entry not the entire
> zone. The rejection as such doesn't even classify as bogosity, it's the
>
I fail to understand this. You seem to suggest that a name server should
reject the SOA record, but accept and attempt to serve the zone.
Precisely how would that work?
> I also seriously counter your claim that having this bracket on the next
> line is in any way bogus. It's visually superior to the now enforced
> option of having it on the same line. There is nothing in the parser not
> to understand it. Spreading data across lines is commonly accepted in a
> lot of configuration languages and bind has been among this in all
> versions I previously ran. Why is that now suddenly bogus?
>
Because rfc1035 has always defined it as bogus. The parenthesis is, as
you are now no doubt aware, a line continuation character:
5.1. Format
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, and text literals can contain
CRLF within the text. Any combination of tabs and spaces act as a
delimiter between the separate items that make up an entry. The end of
any line in the master file can end with a comment. The comment starts
with a ";" (semicolon).
-P.
