BIND 10 #1579: Update database ZoneFinder::find() for negative cases of NSEC3-signed zones

[BIND 10 Development]

#1579: Update database ZoneFinder::find() for negative cases of NSEC3-signed zones
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jinmei
  jinmei                             |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20120403
  medium                             |            Resolution:
                  Component:  data   |             Sensitive:  0
  source                             |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  5
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by haikuo):

 * owner:  haikuo => jinmei


Comment:

 I updated my codes to git, and do the following things:
 1 If zone is signed with NSEC3, and I will return RESULT_NSEC3_SIGNED, and
 it does not find NSEC any more. and it is good for query performance.
 2 If zone has NSEC rrset and NSEC3PARAM rrset at the same time, it will
 throw DataSourceError.
 3 for the unittest, it spend a lot of time. I developed a case of the
 coexistence of NSEC and NSEC3 and some cases to lookout rrset on NSEC3 by
 find function. But I have a problems now, that is those case could work
 separately, but would not work togather because of the incompatibility of
 NSEC and NSEC3, so I "#if 0 *****#endif" to disable some cases. can you
 give me a suggestion to deal with that?

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