Opened 9 years ago

Closed 9 years ago

#488 closed enhancement (complete)

Handle referral

Reported by: shane Owned by: jelte
Priority: medium Milestone: R-Team-Sprint-20110316
Component: resolver Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity:
Sub-Project: Feature Depending on Ticket:
Estimated Difficulty: 3.0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


Handle referral

This is handling referrals "properly".

Given the MessagePtr?, with an NS RRSET, the NSAS will retrieve an address to send the next fetch, and then send it and register callback.


Change History (6)

comment:1 Changed 9 years ago by stephen

This is dependent to #501, as the resolver needs to pass any glue in the referral response to the NSAS.

comment:2 Changed 9 years ago by jelte

  • Owner set to jelte
  • Status changed from new to assigned

with #487, #495 and #501 done, I think the only thing to do here is to check if the referral really is a subzone. I'll add it to runningquery

comment:3 Changed 9 years ago by jelte

  • Owner changed from jelte to UnAssigned
  • Status changed from assigned to reviewing

it's just a minimal changeset: 447c40bcee5edbd71ee1b3812fa71727b2fdc7a6 (though it is branched of trac501)

One thing; we recreate a Name from the string cur_zone_ here again. It is a string because in most uses of cur_zone the apis want a string. I think we should consider changes the api's that handle names to take a Name obejct instead of a string. (and the replace cur_zone by a Name)

comment:4 Changed 9 years ago by stephen

  • Owner changed from UnAssigned to stephen

comment:5 Changed 9 years ago by stephen

  • Owner changed from stephen to jelte

Looks OK - go ahead and merge.

I've added the comments about Name objects to the refactoring notes page.

comment:6 Changed 9 years ago by jelte

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