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:         |                 Owner:
  jinmei                             |                Status:  new
                       Type:         |             Milestone:  Next-Sprint-
  defect                             |  Proposed
                   Priority:         |              Keywords:
  medium                             |             Sensitive:  0
                  Component:  data   |           Sub-Project:  DNS
  source                             |  Estimated Difficulty:  0
               CVSS Scoring:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 It can be easily reproduced: load any valid root zone into sqlite3 DB
 file using b10-loadzone and serve that zone from b10-auth without
 in-memory cache.

 Then a query for a non existent domain would result in:
 {{{
    2013-05-09 17:23:00.110 ERROR [b10-auth.auth/18196] AUTH_PROCESS_FAIL
 message processing failure: duplicate period in *..
 }}}

 this is because `DatabaseClient::Finder::findWildcardMatch()` naively
 prepends '*.' to create a possible wildcard name:
 {{{#!cpp
         const string wildcard("*." + superdomain.toText());
 }}}
 It works for almost all cases but not for the apex of the root zone.
 Fix should be easy.

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