BIND 10 #1086: Ensure message consistency when outputting address+port or name+type+class

BIND 10 Development do-not-reply at isc.org
Thu Jun 30 17:33:35 UTC 2011


#1086: Ensure message consistency when outputting address+port or name+type+class
--------------------------------+-----------------------------------------
            Reporter:  stephen  |                        Owner:
                Type:  defect   |                       Status:  new
            Priority:  trivial  |                    Milestone:  New Tasks
           Component:  logging  |                     Keywords:
           Sensitive:  0        |              Defect Severity:  N/A
         Sub-Project:  DNS      |  Feature Depending on Ticket:
Estimated Difficulty:  0        |          Add Hours to Ticket:  0
         Total Hours:  0        |                    Internal?:  0
--------------------------------+-----------------------------------------
 Some logging messages output an endpoint (address + port) in the form
 "address#port" and others "address(port)".  "address#port" is BIND9 usage,
 so messages should be changed to use that.

 Similarly, although BIND9 is not always consistent, specifying a name,
 type and class is usually done using "name/type/class" (or "name/type" if
 class is not present).  BIND 10 messages should be reviewed for adherence
 to that standard.

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


More information about the bind10-tickets mailing list