BIND 10 #321: b10-auth doesn't handle mixture of DNAME and NS

[BIND 10 Development]

#321: b10-auth doesn't handle mixture of DNAME and NS
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jinmei
  jinmei                             |                Status:  assigned
                       Type:         |             Milestone:  New Tasks
  defect                             |            Resolution:
                   Priority:  major  |             Sensitive:  0
                  Component:  data   |           Sub-Project:  DNS
  source                             |  Estimated Difficulty:  0.25
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:2 shane]:
 > Even without non-captive data sources, we could be acting as a secondary
 for a server with such a broken configuration, so we need to handle it in
 the most logical way possible.
 >
 > Anyway, there ''has'' been a revisit of the whole logic and a
 refactoring of the code. Does this issue still exist? (I admit I am lazy
 and did not load such a zone to check, sorry!)

 Not checked the behavior with a running system either, but according
 to the code:

 - in-memory data source rejects loading such a zone in the first place
 - database-based data source prefers NS over DNAME.

 Considering the case of non-captive database backend, handling this
 case somehow is probably okay, and which behavior wouldn't matter much
 as it's half broken anyway.  So we should probably be consistent with
 BIND 9 and explicitly document it somewhere.  That may go to a
 separate task?

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