BIND 10 #685: resolver cached SERVFAIL becomes NOERROR

[BIND 10 Development]

#685: resolver cached SERVFAIL becomes NOERROR
--------------------------------+---------------------------------
           Reporter:  jreed     |                      Owner:
               Type:  defect    |                     Status:  new
           Priority:  major     |                  Milestone:
          Component:  resolver  |                   Keywords:
          Sensitive:  0         |  Estimated Number of Hours:  0
Add Hours to Ticket:  0         |                  Billable?:  1
        Total Hours:  0         |                  Internal?:  0
--------------------------------+---------------------------------
 I had a DNAME that resulted in a synthesized CNAME that is too long. Using
 b10-resolver as a forwarder: on the first query the upstream sent back a
 SERVFAIL. On second query, the b10-resolver said "Message found in cache,
 returning that" and returned a  status: NOERROR (ANSWER: 0).

 (I noticed this when researching #145.)

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