Ticket #86 (closed defect: wontfix)
query logic can include the duplicate RR in the answer and additional sections
| Reported by: | jinmei | Owned by: | jinmei |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | b10-auth | Keywords: | |
| Cc: | CVSS Scoring: | ||
| Sensitive: | no | Defect Severity: | Medium |
| Sub-Project: | DNS | Feature Depending on Ticket: | |
| Estimated Difficulty: | 0 | Add Hours to Ticket: | |
| Total Hours: | Internal?: | no |
Description
Consider the jinmei.org zone containing the following recoreds:
jinmei.org. 86400 NS ns.jinmei.org.
ns.jinmei.org. 86400 IN A 203.178.141.196
nscname.jinmei.org. 3600 IN CNAME ns.jinmei.org.
If you ask for nscname.jinmei.org/A, the query logic of the libauth returns a response message containing the A record both in the answer and additional sections.
I don't know if this is explicitly prohibited by a protocol spec (probably not), but the behavior looks awkward anyway. BIND 9 removes the redundant A RR from the additional section.
Change History
comment:2 in reply to: ↑ 1 Changed 3 years ago by jinmei
- Owner changed from each to jinmei
- Status changed from new to accepted
The way BIND9 handles this is by checking for duplicate data before inserting anything into the message sections. I had hoped to improve efficiency a bit by avoiding that step, but I think there's probably no way around it. However, let's leave it be for Y1.
Leaving this to post year1 is okay for me.
comment:3 Changed 3 years ago by jinmei
- Owner changed from jinmei to UnAssigned
- Status changed from accepted to assigned
A year2 fodder. changing the state to UnAssigned?.
comment:4 Changed 3 years ago by shane
- Milestone changed from 03. 1st Incremental Release to feature backlog item
comment:5 Changed 3 years ago by shane
- Priority changed from major to minor
- Component changed from Unclassified to b10-auth
comment:6 Changed 2 years ago by stephen
- Milestone feature backlog item deleted
Milestone feature backlog item deleted
comment:7 follow-up: ↓ 8 Changed 15 months ago by shane
- Owner changed from UnAssigned to jinmei
- Sub-Project set to DNS
- Internal? unset
- Defect Severity set to Medium
So... um... is this still a problem?
comment:8 in reply to: ↑ 7 Changed 15 months ago by jinmei
- Milestone set to New Tasks
Replying to shane:
So... um... is this still a problem?
There's a related topic in a more recent context, but I think we can
close this one.
Yes, good catch... I thought I had corrected for that by not fetching additional data that matched QNAME/QTYPE, but that obviously doesn't work in the CNAME case.
The way BIND9 handles this is by checking for duplicate data before inserting anything into the message sections. I had hoped to improve efficiency a bit by avoiding that step, but I think there's probably no way around it. However, let's leave it be for Y1.