BIND 10 #2174: NSAS_WRONG_ANSWER

[BIND 10 Development]

#2174: NSAS_WRONG_ANSWER
----------------------------------------+----------------------------------
                   Reporter:  jreed     |                 Owner:
                       Type:  defect    |                Status:  new
                   Priority:  medium    |             Milestone:  New Tasks
                  Component:  resolver  |            Resolution:
                   Keywords:            |             Sensitive:  0
            Defect Severity:  N/A       |           Sub-Project:  DNS
Feature Depending on Ticket:            |  Estimated Difficulty:  0
        Add Hours to Ticket:  0         |           Total Hours:  0
                  Internal?:  0         |
----------------------------------------+----------------------------------

Comment (by vorner):

 Well, the problem is, the query referred here was from one part of the
 resolver to the NSAS. And the NSAS is not supposed to return CNAME, it's
 supposed to handle it and then return the AAAA (or say it isn't there).
 It's not CNAME from outside, it's CNAME from a place we control.

 About 4) ‒ it's because nobody knows at the time where the data originally
 came from. It might have been one of many servers or the cache.

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