BIND 10 #3058: BIND10-1.1.0 Resolver fails to answer some Queries

[BIND 10 Development]

#3058: BIND10-1.1.0 Resolver fails to answer some Queries
---------------------------------+-----------------------------------------
            Reporter:  thozza    |                        Owner:
                Type:  defect    |                       Status:  new
            Priority:  low       |                    Milestone:  New Tasks
           Component:  resolver  |                   Resolution:
            Keywords:            |                 CVSS Scoring:
           Sensitive:  0         |              Defect Severity:  High
         Sub-Project:  DNS       |  Feature Depending on Ticket:
Estimated Difficulty:  0         |          Add Hours to Ticket:  0
         Total Hours:  0         |                    Internal?:  0
---------------------------------+-----------------------------------------

Comment (by thozza):

 Replying to [comment:1 vorner]:
 > While the problem is probably real, the current resolver implementation
 is mostly an experiment for us. It's not production ready, so problems are
 to be expected. Maybe we should warn in the logs, or something, marking it
 as red at https://bind10.isc.org/wiki/ComponentStatus isn't enough.

 I'm aware of the current state of b10-resolver. However since we have
 BIND10 available as a package in
 Fedora 19 there are users starting to use it.

 I'm not expecting you to fix this issue any time soon, just wanted to
 report it so it will be fixed
 eventually.
 > I'm pretty sure it can handle IPv6 (as the library we use hides the
 difference between IPv4 and IPv6 for us), but we know it gets confused
 inside from time to time and just breaks for some unknown reason.

 My guess based on log is that the resolver fails while trying to query NS
 for desired domain over IPv6
 even though it already got an answer over IPv4.

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