Opened 9 years ago

Closed 6 years ago

#543 closed task (wontfix)

Chaining of CNAMEs in in-memory data-source.

Reported by: vorner Owned by:
Priority: medium Milestone: Remaining BIND10 tickets
Component: data source Version: bind10-old
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

Currently only the CNAME itself is returned to client if the in-memory datasource is used. The CNAME should be followed and the answer at the end returned as well if it is available in the same zone (or, in the datasource).

Note that this could solve itself when we merge datasource APIs together.

Subtickets

Change History (6)

comment:1 Changed 9 years ago by stephen

  • Milestone A-Team-Task-Backlog deleted

Milestone A-Team-Task-Backlog deleted

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

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

Just checked with the new in-memory code, and this is still a problem.

comment:3 Changed 8 years ago by shane

  • Milestone New Tasks deleted

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

Replying to shane:

Just checked with the new in-memory code, and this is still a problem.

Actually it's a kind of "design decision". We had a discussion about
this specific topic before although there didn't seem to be a clear
consensus:
https://lists.isc.org/pipermail/bind10-dev/2011-January/001868.html

comment:5 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:6 Changed 6 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version set to old-bind10

This issue is related to bind10 code that is no longer part of Kea.

If you are interested in BIND10/Bundy framework or its DNS components,
please check http://bundy-dns.de.

Closing ticket.

Note: See TracTickets for help on using tickets.