BIND 10 #1092: NSAS_INVALID_RESPONSE is internal error?

[BIND 10 Development]

#1092: NSAS_INVALID_RESPONSE is internal error?
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:  zhanglikun
                       Type:         |                Status:  reviewing
  defect                             |             Milestone:
                   Priority:  major  |  Sprint-20110830
                  Component:         |            Resolution:
  Unclassified                       |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DNS
            Defect Severity:  High   |  Estimated Difficulty:  3
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => zhanglikun


Comment:

 Hello

 Thanks for the investigation. If it is really as you say (which is
 possible, whoever wrote the description might have gotten confused by the
 failureInternal, so he said it is internal error), the message is safe.

 Maybe if the thing is common (as you say, most NSs don't have an AAAA
 record), it should maybe be even INFO, not WARN (for one, we don't want to
 make admins panic, and for another, they can do nothing about these WARNs
 and this will be very common message, so to avoid SPAMing).

 I think the „short“ message you propose with the parenthesis doesn't help
 much. Does it mean the one we got is with NOERROR and empty? Or that the
 one we wanted should be NOERROR and empty? Or should the NOERROR and empty
 be result of replacement and not this exact verbatim message? Maybe say
 something like „queried for $NAME/$TYPE, but got no useful data as answer
 (rcode: $RCODE, count of RRs: $RRCOUNT)“?

 Anyway, the long description should be updated as well (while the short
 one is not very helpful, the long one is plain wrong). Any suggestions?

 Thank you

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