BIND 10 #670: identify a secondary zone
BIND 10 Development
do-not-reply at isc.org
Mon Apr 4 20:28:28 UTC 2011
#670: identify a secondary zone
-------------------------------------+-------------------------------------
Reporter: jreed | Owner: vorner
Type: defect | Status: reviewing
Priority: blocker | Milestone:
Component: | Sprint-20110405
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 jelte):
* owner: jelte => vorner
Comment:
While this does seem to fix the stated problem, I don't think it works as
one would expect;
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.
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).
Small python nit: dicts have their own copy() method so copy.copy() is not
necessary on line 407
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.
--
Ticket URL: <http://bind10.isc.org/ticket/670#comment:7>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list