Re: [DNSOP] Last Call: <draft-ietf-dnsop-resolver-priming-09.txt> (Initializing a DNS Resolver with Priming Queries) to Best Current Practice

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 3 Nov 2016, at 21:16, william manning wrote:

What method is in place to ensure that the cache is, #1, checked before emitting priming queries, #2, that if there is already data (complete or
partial) in the cache, how is the client supposed to determine if the
cached data is preferred over unverified, remote data? Or does the client operate with the presumption that local data is always wrong and the best
data is always external?

Inquiring Minds want to know.

There is no such method in place. This document describes how to prime resolvers and when you should, but does not prohibit any other use of the same DNS queries when priming is not needed.

--Paul Hoffman




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]