BIND 10 #1102: Make message about out-of-bailiwick data less verbose

[BIND 10 Development]

#1102: Make message about out-of-bailiwick data less verbose
-------------------------------------+-------------------------------------
                   Reporter:  shane  |                 Owner:  jreed
                       Type:         |                Status:  reviewing
  enhancement                        |             Milestone:
                   Priority:  low    |  Sprint-20120403
                  Component:         |            Resolution:
  b10-auth                           |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DNS
            Defect Severity:  Low    |  Estimated Difficulty:  1
Feature Depending on Ticket:  none   |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jreed):

 Committed it in commit 6784b5dbb0e599f370fb5965acf7038ab214b107

 Added a little to the log description based on conversation in jabber.

 No changelog entry added as discussed on jabber. Nobody reported it other
 than our developers. And not useful to have a changelog entry for every
 logging severity change.

 I was thinking that the NS lookups for additional data should be logged
 differently... this log message happens due to outside queries for
 something not in the datasource AND also for lookups of addresses for NS
 records in the datasource (for additional section info). I was told in
 jabber: "i suspect that at the time it is logged, it does not know why it
 is looking for that data." and that the new datasource should improve
 this.

 The original problem for the ticket is solved, but I am not closing this
 ticket unless others agree that the current single log ID for two
 different concepts is okay.

 Another issue is that I am logging at log level 40. I didn't see other
 choice used for datasrc. Note that 30 and below is useful for admins, like
 this log id.  But we plan to have a different task reviewing log entries,
 severities, debug levels, etc. So we can handle it then. (I made a ticket
 for this: #1822.)

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