BIND 10 #1570: DS query handling in auth::Query

BIND 10 Development do-not-reply at isc.org
Wed Feb 8 18:05:57 UTC 2012


#1570: DS query handling in auth::Query
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jinmei
  jinmei                             |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20120221
  critical                           |            Resolution:
                  Component:         |             Sensitive:  0
  b10-auth                           |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  6
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:13 stephen]:

 > >> It would be helpful to explain how the case of a query for a
 grandchild zone with the server having authority for the child zone
 differs from the case of a query for the child zone with the server having
 authority for the parent.
 > >I don't understand this comment...
 > It was prompted by the comment above the test dsAtGrandParentAndChild,
 which says:
 > {{{
 > // DS query for a "grandchild" zone, and the server has authority of the
 > // child zone, too.  In this case the query should be handled in the
 child
 > // side and should result in no data with SOA.
 > }}}
 > The comment implies that the test is checking that a DS query to the
 child zone in a parent-child relationship is handled by the parent, a test
 that is done elsewhere.  I think the comment should be rephrased to say
 that the test is checking that the query is handled by the parent of the
 zone to which the query is directed, and not by any ancestors of the
 parent.

 I'm still not sure if I fully understand the concern, but I see the
 above cited comment can be confusing (or inaccurate).  I revised it
 hoping it's now more understandable.  How about that?

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


More information about the bind10-tickets mailing list