BIND 10 #2911: don't fallback from ixfr to axfr due to data source error

[BIND 10 Development]

#2911: don't fallback from ixfr to axfr due to data source error
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |  UnAssigned
            Priority:  medium        |                       Status:
           Component:  xfrin         |  assigned
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20130514
         Sub-Project:  DNS           |                   Resolution:
Estimated Difficulty:  4             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Note there's a discussion on this topic at bind10-dev:
 https://lists.isc.org/pipermail/bind10-dev/2013-April/004590.html

 We'll probably have to change the resolution as discussed there
 (I think the task size is still generally the same so it won't have to
 be re-estimated).

 Another note: I noticed there are comments and documentation saying
 "we don't yet support axfr-to-ixfr fallback".  This is false.  I
 suggest updating these within this ticket, too.  Further, I can
 probably now switch to the "use IXFR by default" mode.

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