BIND 10 #545: incorrect wildcard handling in sqlite3 data source

[BIND 10 Development]

#545: incorrect wildcard handling in sqlite3 data source
-------------------------------------+-------------------------------------
           Reporter:  jinmei         |                      Owner:
               Type:  defect         |  UnAssigned
           Priority:  major          |                     Status:  new
          Component:  data source    |                  Milestone:  feature
          Sensitive:  0              |  backlog item
Add Hours to Ticket:  0              |                   Keywords:
        Total Hours:  0              |  Estimated Number of Hours:  0
                                     |                  Billable?:  1
                                     |                  Internal?:  0
-------------------------------------+-------------------------------------
 Assume in example.com we have these records:

 {{{
 *.wild.example.com.     IN      A       192.0.2.255
 foo.wild.example.com.   IN      A       192.0.2.250
 }}}
 (and no other names under foo.wild.example.com.)

 In this case, queries for bar.foo.wild.example.com should result in
 NXDOMAIN
 due to the existence of foo.wild.example.com as described in Section 4.3.3
 of RFC1034.

 The query logic currently implemented in lib/datasource (mainly for
 sqlite3) doesn't handle this case correctly, and return a match with
 the wildcard.

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