> On Jul 26, 2026, at 21:50, Michael Breuer <[email protected]> wrote: > > Hi. > > I like the idea of cache synchronisation. But I have a preference for > encrypted transport-only, out of privacy concerns. Leaking the cache to the > networks doesn’t look good to me. >
I have an outstanding request for unbound to do cache replication but only for DNSSEC entries that validate. This allows you to sync from untrusted sources à la pool.ntp.org and we can create a huge volunteer pool. Cache sharing on poisonable data seems wrong and too risky. Transport security is no substitute for data origin security. Paul >> On 20. Jul 2026, at 14:10, Stephane Bortzmeyer >> <[email protected]> wrote: >> >> This is an individual draft but dnsop may be interested. Comments welcome. >> >> "Networks of cooperating and mutually trusting DNS resolvers could >> benefit from cache sharing, where one resolver would distribute the >> result of a resolution to other resolvers. This document >> standardizes a protocol to do so." >> >> https://datatracker.ietf.org/doc/draft-bortzmeyer-dnsop-poisonlicious/ >> >> _______________________________________________ >> DNSOP mailing list -- [email protected] >> To unsubscribe send an email to [email protected] > > _______________________________________________ > DNSOP mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
