Opened 9 years ago

Closed 5 years ago

#337 closed defect (wontfix)

Expired zone should not be served

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

Description

Currently, when zonemgr expires one zone, auth/xfrout module doesn't know it, so, the expired zone is still served. There should be one way to mark the zone.

Subtickets

Change History (16)

comment:1 Changed 9 years ago by jreed

  • Defect Severity set to N/A
  • Milestone set to Sprint-20110517
  • Sub-Project set to DNS

comment:2 Changed 9 years ago by stephen

  • Estimated Difficulty changed from 0.0 to 3

comment:3 Changed 9 years ago by jreed

  • Type changed from task to defect

comment:4 Changed 9 years ago by jinmei

Should we really solve this ticket now?

Assuming we'll work on datasource refactoring quite soonish, it seems
to make more sense to solve this on top of the clarification. Plus,
although this is surely a real problem it doesn't seem to be so
critical considering the overall quality (in terms of "production
ready-ness") of BIND 10.

So, my proposal is to remove this ticket from the current sprint for now.

For the purpose heads-up, I'll move this to the review queue.

comment:5 follow-up: Changed 9 years ago by jinmei

  • Owner set to UnAssigned
  • Status changed from new to reviewing

comment:6 in reply to: ↑ 5 Changed 9 years ago by jinmei

Replying to jinmei:

There seems to be a consensus (at the bi-weekly call on June 7)
for moving this ticket to the backlog. Moving the ticket accordingly.

comment:7 Changed 9 years ago by jinmei

  • Milestone changed from Sprint-20110614 to Year 3 Task Backlog
  • Owner changed from UnAssigned to jinmei
  • Status changed from reviewing to accepted

comment:8 Changed 9 years ago by jinmei

  • Owner changed from jinmei to UnAssigned
  • Status changed from accepted to assigned

comment:9 follow-up: Changed 8 years ago by shane

  • Owner changed from UnAssigned to jinmei

Jinmei, we've refactored the data sources. Is there any action taken now when a zone becomes stale? If so, I guess we can resolve this ticket. Otherwise we need to implement it! :)

comment:10 in reply to: ↑ 9 Changed 8 years ago by jinmei

Replying to shane:

Jinmei, we've refactored the data sources. Is there any action taken now when a zone becomes stale? If so, I guess we can resolve this ticket. Otherwise we need to implement it! :)

In terms of the new data source API/implementation, we don't do
anything about expired zone. IMO it's more about another ever-lasting
topic of zone configuration/management redesign, rather than
manipulating zone data in a data source.

comment:11 Changed 8 years ago by jinmei

  • Owner changed from jinmei to shane

comment:12 Changed 8 years ago by shane

  • Milestone Year 3 Task Backlog deleted
  • Owner changed from shane to UnAssigned

comment:13 Changed 8 years ago by jelte

  • Milestone set to Next-Sprint-Proposed

comment:14 Changed 6 years ago by shane

What we really need is a way for an administrator to configure this behavior per zone, along with a default server behavior.

comment:15 Changed 6 years ago by stephen

  • Milestone set to DNS Outstanding Tasks

comment:16 Changed 5 years ago by tomek

  • Resolution set to wontfix
  • Status changed from assigned 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.