BIND 10 #1383: FORMERR log messages not logged

[BIND 10 Development]

#1383: FORMERR log messages not logged
--------------------------------+-----------------------------------------
            Reporter:  jreed    |                        Owner:
                Type:  defect   |                       Status:  new
            Priority:  major    |                    Milestone:  New Tasks
           Component:  logging  |                     Keywords:
           Sensitive:  0        |              Defect Severity:  Medium
         Sub-Project:  DNS      |  Feature Depending on Ticket:
Estimated Difficulty:  0        |          Add Hours to Ticket:  0
         Total Hours:  0        |                    Internal?:  0
--------------------------------+-----------------------------------------
 dvv noted on jabber a couple weeks ago about querying for
 teredo.ipv6.microsoft.com resulted in a FORMERR.
 I could repeat that with BIND 10 resolver but not BIND 9.

 Our source code has many logging places for FORMERR situations, but I
 never see any FORMERR logging in my logs (even with full debugging and
 doing this test).

 Jinmei said: In general, exception messages may or may not appear in logs.
 It depends on how the catcher side reacts to them.

 The fix is to make sure any FORMERR generated by BIND 10 is logged.

 This may lead to understand why this particular query resulted in FORMERR
 (which may need a new ticket to fix?).

 (Also: it returns AUTHORITY section for FORMERR response. Maybe need a new
 ticket for that?)

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