2020
DOI: 10.17487/rfc8767
|View full text |Cite
|
Sign up to set email alerts
|

Serving Stale Data to Improve DNS Resiliency

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
3
0

Year Published

2023
2023
2023
2023

Publication Types

Select...
2
1
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(3 citation statements)
references
References 1 publication
0
3
0
Order By: Relevance
“…Farsight collects this dataset via recursive DNS resolvers of ISPs. Collaborating ISPs can install a sensor, which sends all cache misses [95,111]-see Table 4 in Appendix A-of their clients to Farsight.…”
Section: Datasetmentioning
confidence: 99%
See 1 more Smart Citation
“…Farsight collects this dataset via recursive DNS resolvers of ISPs. Collaborating ISPs can install a sensor, which sends all cache misses [95,111]-see Table 4 in Appendix A-of their clients to Farsight.…”
Section: Datasetmentioning
confidence: 99%
“…We are skipping the concepts of QNAME minimization[26], NS hardening, and GLUE records[100] for simplification here.10 We are skipping the concept of using stale caches for resiliency here[95].…”
mentioning
confidence: 99%
“…An additional strategy is serving stale cache records [26]. Stale cache records are records in the resolver's cache of which the TTL has expired.…”
Section: Back-off Strategiesmentioning
confidence: 99%