Opened 8 years ago

Closed 6 years ago

#1881 closed enhancement (wontfix)

b10-auth behavior when XFR not expected to answer

Reported by: jreed Owned by:
Priority: medium Milestone: DNS Outstanding Tasks
Component: b10-auth Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 6 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


This is from this 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.


Change History (4)

comment:1 Changed 8 years ago by jinmei

I'm afraid this requires some design and subtasking.

comment:2 Changed 8 years ago by shane

  • Milestone New Tasks deleted

comment:3 Changed 6 years ago by stephen

  • Milestone set to DNS Outstanding Tasks

comment:4 Changed 6 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed

DNS and BIND10 framework is outside of scope for Kea project.
The corresponding code has been removed from Kea git repository.
If you want to follow up on DNS or former BIND10 issues, see project.

Closing ticket.

Note: See TracTickets for help on using tickets.