[bind10-dev] addZone interface for the new loadzone and zone management framework

[Michal 'vorner' Vaner]

Hello

This is outside of the original discussion about addZone (so I'm not objecting
to the proposal ‒ there could be better solutions, but we need to move forward).

On Fri, Dec 07, 2012 at 10:39:06AM -0800, JINMEI Tatuya / 神明達哉 wrote:
> A bit more explanation: I guess there can actually be a situation
> where a zone exists but its contents (RRs) don't.  For example, if a
> secondary server (which is already referenced from the parent zone) is
> being setup but zone transfer from the primary server somehow hasn't
> succeeded (due to temporary failure of the primary, network problems,
> etc).  In this case, the secondary server should recognize it's
> managing the zone without the contents and should return SERVFAIL to
> queries for the zone rather than a response indicating it's not really
> authoritative for that zone (in our implementation, it would be
> REFUSED).
> 
> So I think it makes some sense to be able to manage the
> existence/non-existence of zones independently from loading RRs for
> the zones.

While I see the reason behind the separate existence of zone and the content, I
believe the data source should only contain valid zones. So in case of not-yet
transferred secondary zone, for example, I think we should have a configuration
specifying the zone exists and where it comes from, but no zone in the database
yet. Once the XfrIn connects, it should create the zone there and attempt to
load it. If it succeeds, it commits and zone becomes ready. If it fails during
the attempt, the zone is not committed and it still doesn't exist.

What I wouldn't like is handling special cases like „I have the zone finder, but
it has no RRs“ all over the place.

With regards

-- 
chown -R us $BASE

Michal 'vorner' Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20121210/7f948f6f/attachment.bin>