BIND 10 #1881: b10-auth behavior when XFR not expected to answer

[BIND 10 Development]

#1881: b10-auth behavior when XFR not expected to answer
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  enhancement   |                       Status:  new
            Priority:  medium        |                    Milestone:  New
           Component:  b10-auth      |  Tasks
           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
-------------------------------------+-------------------------------------
 This is from this
 https://lists.isc.org/pipermail/bind10-dev/2011-December/002961.html
 thread on bind10-dev mailing list:

 On Tue, 20 Dec 2011, JINMEI Tatuya / ???? wrote:

 > It's also strange to me that b10-auth still doesn't consume 100% CPU
 > time even if it should be too busy and actually drops queries.
 >
 > Maybe related to this point, I guess we should allow b10-auth simply
 > returns REFUSED or some other error to xfr requests immediately if
 > it's not expected to answer them.  The ability of disabling xfrout is
 > nice, but what it currently means that b10-auth tries to forward the
 > requests but fails to establish a connection to xfrout (resulting in
 > an exception) for every request.  That's an obvious waste, and maybe
 > that's the reason for the idle time.

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