[bind10-dev] Zone loading requirements, take 1

[Shane Kerr]

Evan,

On Monday, 2012-03-05 19:12:16 +0000, 
Evan Hunt <each at isc.org> wrote:
> > $ b10-zoneloader example.com.zone
> > 
> > And BIND 10 should be able to figure out that I am loading
> > example.com if it is unambiguous from context. (This is an
> > annoyance of mine from zone signing today.)
> > 
> > This might be scope creep, but I think it is not too hard and would
> > be nice.
> 
> I agree, that is nice.  (I remember wanting to add that feature to
> the original b10-loadzone, but I can't remember if I did or not.)

Right now the current b10-loadzone looks for an SOA RR with a name and
assumes that is the name of the zone being loaded. I think that's
pretty much the correct behavior.

> But, even so, *if* the zone origin is provided in advance--from
> command line or zone configuration--then we must be able to accept an
> ambiguous zonefile such as the one I mentioned earlier.  (And
> similarly, must be able to accept a zonefile with the SOA in an
> arbitrary location, even if it will rarely encounter that particular
> weirdness.)

Well sure, I don't consider it ambiguous if the origin is otherwise
specified. :)

Based on Peter's and your input I've change 3.4.2 to remove the
requirement that SOA be the first record in a zone file. 

Cheers,

--
Shane