BIND 10 #2897: BIND should log zone serials along with zone name for xfer-in, xfer-out and notify

BIND 10 Development do-not-reply at isc.org
Wed Apr 3 11:04:03 UTC 2013


#2897: BIND should log zone serials along with zone name for xfer-in, xfer-out and
notify
-------------------------------------+-------------------------------------
                   Reporter:  shane  |                 Owner:
                       Type:         |                Status:  new
  enhancement                        |             Milestone:  New Tasks
                   Priority:         |              Keywords:
  medium                             |             Sensitive:  0
                  Component:         |           Sub-Project:  DNS
  Unclassified                       |  Estimated Difficulty:  0
               CVSS Scoring:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 Joe Abley suggested this for BIND 9, and it makes sense for BIND 10 too:

 {{{
 Hi,

 Feature request: please make BIND9 include the zone serial number for:

 - log messages concerning NOTIFY messages received
 - log messages concerning NOTIFY messages sent
 - log messages concerning AXFR responses sent (xfer-out)
 - log messages concerning AXFR responses received (xfer-in)

 Thanks,


 Joe
 }}}

 While we don't get the zone serial in a NOTIFY as far as I know, we could
 log the serial that the slave has when it gets the NOTIFY (although we
 need to be careful that the log message is clear about ''which'' serial we
 are logging).

 We have nice information with zone transfers, it seems weird that we
 didn't think to include such basic information. :)

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


More information about the bind10-tickets mailing list