Opened 8 years ago

Closed 8 years ago

#1552 closed defect (duplicate)

in-memory datasource handle DO flag

Reported by: jreed Owned by:
Priority: medium Milestone: Year 3 Task Backlog
Component: data source Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 4 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

If DNSSEC OK is set in the query, then have the in-memory datasource provide the DNSSEC records to be sent.

Subtickets

Change History (6)

comment:1 Changed 8 years ago by jinmei

  • Milestone changed from New Tasks to Next-Sprint-Proposed

should be done after #1614

comment:2 Changed 8 years ago by jelte

  • Estimated Difficulty changed from 0 to 4

comment:3 Changed 8 years ago by jreed

  • Milestone changed from Year 3 Task Backlog to Next-Sprint-Proposed

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

Probably fixed in #1695.

comment:5 in reply to: ↑ 4 Changed 8 years ago by jinmei

Replying to shane:

Probably fixed in #1695.

I think it meant the find() method of the in-memory data source should
return RRSIGs when asked. Actually, it has been the case almost from
the beginning. In-memory rather had a problem in its loading function
for signed zones (e.g. #1614), but we fixed these issues.

In any case, it now handles the DO bit correctly. I'm closing this ticket.

comment:6 Changed 8 years ago by jinmei

  • Resolution set to duplicate
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.