upstream/unbound
1
0
Fork 0
mirror of https://github.com/NLnetLabs/unbound.git synced 2026-01-03 05:19:34 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

rrset id for cache flush

Browse source 
git-svn-id: file:///svn/unbound/trunk@1703 be551aaa-1e26-0410-a405-d3ace91eadb9
This commit is contained in:
Wouter Wijngaards 2009-07-07 10:16:34 +00:00
parent 5e90d568eb
commit 5decb468c2
1 changed files with 6 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
doc/TODO
View file

@ -179,8 +179,12 @@ Triggered by a trust anchor or by a signed DS record for a zone.
Another option is to check if the IP address for the bad data is in
the delegation point for the zone. If it is not - try again instantly.
This is a loop if the NS has zero TTL on its address.
Another option is to flush the zone from cache, too expensive to implement.
How to solve this?
Flush cache is when the zone is backed off to more than one second.
Flush is denoted by an age number, we use the rrset-special-id number,
this is a thread-specific number. At validation failure, if the data
RRset is older than this number, it is flushed and the query is restarted.
A thread stores its own id number when a backoff larger than a second
occurs and its id number has not been stored yet.
* unbound is configured to talk to upstream caches. These caches have
inconsistent bad data. If one is bad, it is marked bad for that zone.
If all are bad, there may not be any way for unbound to remove the