Opened 9 years ago

Closed 8 years ago

Last modified 8 years ago

#306 closed defect (wontfix)

incorrect response to direct DS query

Reported by: jinmei Owned by: jinmei
Priority: medium Milestone:
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: 0.0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

Assume the BIND10 auth server has authority for a signed zone "example.org".

It returns a REFUSED error for a query for example.org/DS.

This seems to be wrong. At least it breaks the assumption of BIND 9 resolver.

BIND 9 auth server returns a no-error empty response in this case. We should probably do the same.

Subtickets

Change History (6)

comment:1 Changed 9 years ago by larissas

  • Milestone changed from y2 6 month milestone to feature backlog item
  • Owner set to UnAssigned
  • Priority changed from critical to major
  • Status changed from new to assigned

comment:2 Changed 9 years ago by stephen

  • Milestone feature backlog item deleted

Milestone feature backlog item deleted

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

  • Defect Severity set to N/A
  • Owner changed from UnAssigned to jinmei
  • Sub-Project set to DNS

This seems to still be the way the server works, although I have not tested it with the in-memory data source, so perhaps this is fixed with the refactored code. Jinmei, do you know?

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

  • Milestone set to New Tasks

Replying to shane:

This seems to still be the way the server works, although I have not tested it with the in-memory data source, so perhaps this is fixed with the refactored code. Jinmei, do you know?

This shouldn't be an issue in the new query logic. I'm closing this
ticket.

comment:5 Changed 8 years ago by jinmei

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

comment:6 Changed 8 years ago by shane

  • Milestone New Tasks deleted
Note: See TracTickets for help on using tickets.