BIND 10 #670: identify a secondary zone

[BIND 10 Development]

#670: identify a secondary zone
-------------------------------------+-------------------------------------
                 Reporter:  jreed    |                Owner:  jelte
                     Type:  defect   |               Status:  reviewing
                 Priority:  blocker  |            Milestone:
                Component:           |  Sprint-20110419
  secondary manager                  |           Resolution:
                 Keywords:           |            Sensitive:  0
Estimated Number of Hours:  0.0      |  Add Hours to Ticket:  0
                Billable?:  1        |          Total Hours:  0
                Internal?:  0        |
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => jelte


Comment:

 Hello

 Replying to [comment:7 jelte]:
 > Now that there is a secondaries list, I would expect to be able to use
 that to add zones; i.e. add a zone to said list, specify the master(s),
 and it should start transferring them (it now returns a seemingly
 unrelated error about a SOA, which is technically correct if you know what
 it's doing, but not really helpful). Note that this is not a comment on
 this ticket, but a suggestion for a 'new' feature :) (which probably
 involves more substansive changes to zonemgr as your comment already
 suggests). Other suggestions for improvement; initial testing makes it
 appear that the refresh interval is only updated on start, and not changed
 when the SOA value changes, and the logs at least suggest that it actually
 does a full AXFR, even if the zone has not been changed (have not checked
 whether this is actually the case). Also not really relevant for this
 ticket though.

 Hmm, right, good point. Or there should be at last a command „import zone“
 or something, because having to carry the zone in the first time on floppy
 diskettes shouldn't be necessary, when it can be transfered at later time
 over the network.

 > One problem that may be relevant to this ticket is that the zone name
 one sets in secondary_zones must be an FQDN, if the root dot is missing
 it'll error on not finding a SOA (it should imo either error on not being
 an fqdn, or it should add the root dot itself).

 It adds the dot internally if it's missing now.

 > Small python nit: dicts have their own copy() method so copy.copy() is
 not necessary on line 407

 ACK

 > Rest of the code looks ok (barring that work mentioned before, shall we
 open separate task(s) for that? I think we'll find much more work to do,
 but for now this can be merged.

 Yes, would you like to create the tickets?

 Are the fixes/changes OK now?

 Thanks

-- 
Ticket URL: <http://bind10.isc.org/ticket/670#comment:8>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development