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:  UnAssigned
  jinmei                             |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20120320
  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      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:10 haikuo]:
 > it is not support NSEC3 unit test for database data resource now,so the
 unit test for RESULT_NSEC3_SIGNED setting in case of NXDOMAIN and NXRRSEon
 will go on after it support NSEC3 feature in database data resource.

 I don't think this is correct as I commented in #1785.  And I don't
 think this is an acceptable excuse to skip tests.  My suggestion is to
 use the existence of NSEC3PARAM to identify whether the zone is NSEC3
 signed or not, or, if this task is really not testable until the
 data source supports NSEC3 itself, we should hold off for tick ticket
 until it's done, then write tests, then get this reviewed.

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