[bind10-dev] Zone loading requirements, take 1

[Evan Hunt]

> In the context of zone loading, "origin" means "the thing that we tack
> onto relative domain names". The origin might not be known before
> loading.

That's true, but by "zone origin" I meant specifically the zone name, not
the currentz value of $ORIGIN.

> $ 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.)

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.)

                                        eh