BIND 10 #1657: zonemgr should not ask for IXFR on new zone
BIND 10 Development
do-not-reply at isc.org
Thu Feb 9 17:59:28 UTC 2012
#1657: zonemgr should not ask for IXFR on new zone
-------------------------------------+-------------------------------------
Reporter: jreed | Owner:
Type: | Status: new
defect | Milestone: Year 3 Task
Priority: major | Backlog
Component: | Resolution:
Unclassified | Sensitive: 0
Keywords: | Sub-Project: DNS
Defect Severity: N/A | Estimated Difficulty: 0
Feature Depending on Ticket: | Total Hours: 0
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jinmei):
Replying to [comment:2 shane]:
> I'm not even sure how this even tries to work. An IXFR is supposed to
give the starting serial number, and there is no SOA for a new zone.
If I understand it correctly, zonemgr is XFR-type agnostic. It simply
asks for a new version via whichever type of xfr.
In any case there's less doubt zonemgr will need heavy overhaul.
--
Ticket URL: <http://bind10.isc.org/ticket/1657#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list