BIND 10 #659: resolver priming
BIND 10 Development
do-not-reply at isc.org
Fri Mar 4 10:33:59 UTC 2011
#659: resolver priming
-------------------------------------+-------------------------------------
Reporter: jelte | Owner:
Type: defect | Status: new
Priority: major | Milestone: R-Team-
Component: resolver | Task-Backlog
Sensitive: 0 | Keywords:
Add Hours to Ticket: 0 | Estimated Number of Hours: 0
Total Hours: 0 | Billable?: 1
| Internal?: 0
-------------------------------------+-------------------------------------
Ticket #495 introduces the use of the NSAS, but it doesn't correctly prime
the resolver yet. We really need this (at least a simple version of it),
it should probably be a method of RecursiveQuery (which is in essence the
'resolver' object right now), called once initialized, and later at a
regular interval (either when the priming result appears to expire or once
a day).
This might also need a way to simply send out one query and get back the
result, without the full recursive process. Depending on what we do in
#658, this may already be possible.
--
Ticket URL: <http://bind10.isc.org/ticket/659>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list