How is this supposed to work together with caching on public recursive resolvers? When the answer (for a query which contains EDNS client subnet information) is personalized, it cannot get cached, and so the reason to use a caching resolver goes away - the client has the same RTT time as if it would asked the authoritative server himself. -- 93.200.30.76 ( talk) 00:43, 3 September 2022 (UTC)
How is this supposed to work together with caching on public recursive resolvers? When the answer (for a query which contains EDNS client subnet information) is personalized, it cannot get cached, and so the reason to use a caching resolver goes away - the client has the same RTT time as if it would asked the authoritative server himself. -- 93.200.30.76 ( talk) 00:43, 3 September 2022 (UTC)