Opened 9 years ago

Closed 6 years ago

#660 closed enhancement (wontfix)

options and/or commands to control cache behaviour

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

Description

Ticket #491 introduced the use of a cache, but at this moment we have no method of controlling it;

some initial nice options would be:

  • set maximum cache size
  • set maxmimum lru size
  • flush cache
  • flush cache for specific names
  • flush cache for specific zones and everything below it (though i'm not sure this is possible with the current cache implementation)

Subtickets

Change History (3)

comment:1 Changed 9 years ago by stephen

  • Milestone R-Team-Task-Backlog deleted

Milestone R-Team-Task-Backlog deleted

comment:2 Changed 6 years ago by stephen

  • Defect Severity set to N/A
  • Milestone set to DNS Outstanding Tasks
  • Sub-Project set to DNS

comment:3 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
http://bundy-dns.de project.

Closing ticket.

Note: See TracTickets for help on using tickets.