BIND 10 #1390: update b10-auth to pass IXFR-request to xfrout

BIND 10 Development do-not-reply at isc.org
Mon Nov 21 17:17:17 UTC 2011


#1390: update b10-auth to pass IXFR-request to xfrout
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jelte
  jinmei                             |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:  major  |  Sprint-20111122
                  Component:         |            Resolution:
  b10-auth                           |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DNS
            Defect Severity:  N/A    |  Estimated Difficulty:  0
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => jelte


Comment:

 Hello

 Replying to [comment:5 jelte]:
 > >  * There are two „# TODO: Log?“. Maybe we should decide and maybe
 > really log.
 >
 > ack, three even :) added log messages. After a short bit of discussion
 > on jabber, I've set these to debug level (otherwise externals could
 > cause log spam), except for the one that should never even reach this
 > part of the code. I also changed the acl reject/drop from info to
 > debug, for the same reasoning.

 Hmm, looks like there'll be a collision with #1372, as it touches the area
 as well. But this branch is OK in itself.

 > Hmm, yes, I don't know if we were aiming for one Big Changelog
 > message, but let's go for:
 >
 > [func]  jelte
 > The b10-auth will no longer reply to IXFR requests with a NOTIMPL, but
 > pass the IXFR request on to b10-xfrout (if running). Currently,
 > pending #1371 and #1372, xfrout will not correctly respond to IXFR
 > requests, but it will answer as if it was an AXFR.

 I'm not sure if it will be true on the release, the #1371 and #1382 are
 almost ready to merge as well. So, maybe the note about response to IXFR
 might be unneeded.

 But the branch is ready to merge.

 Thank you

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


More information about the bind10-tickets mailing list