BIND 10 #2951: NXDOMAIN case at root server results in SERVFAIL w/ sqlite3 datasrc

[BIND 10 Development]

#2951: NXDOMAIN case at root server results in SERVFAIL w/ sqlite3 datasrc
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |  UnAssigned
            Priority:  medium        |                       Status:
           Component:  data source   |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20131015
         Sub-Project:  DNS           |                   Resolution:
Estimated Difficulty:  0             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by muks):

 * owner:   => UnAssigned
 * status:  new => reviewing
 * milestone:   => Sprint-20131015


Comment:

 This is now ready for review.

 We create a `Name` object for `*` and `concatenate()` the super-domain to
 it. The `Name` construction for `*` is slightly less optimal, but this is
 the safest approach. Similar to `LabelSequence`, it is possible to have a
 static `Name::WILDCARD()` function that returns a reference to a global
 wildcard `Name` object, but this seems to be the only place in code that
 constructs the absolute '*.' name.

 Proposed `ChangeLog` entry:
 {{{
 +XYZ.   [bug]           muks
 +       b10-auth now correctly processes NXDOMAIN results in the root zone
 +       when using a SQLite3 data source.
 +       (Trac #2951, git ...)
 }}}

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