Chrome could just behave like a resolver. Or operating systems could start behaving like resolvers on ::1. DNS was designed with trusted resolvers in mind (was

Chrome could just behave like a resolver. Or operating systems could start behaving like resolvers on ::1. DNS was designed with trusted resolvers in mind (was it?), but we've shifted towards using resolvers of our ISPs and random companies. I can see the appeal of caching across a WAN, but then again, we don't use HTTP proxies anymore, which provide a similar caching feature. Integrity protection should be placed higher in our priority list than caching effectiveness. Maybe the impact on root servers created with selfhosted resolvers would decrease as chromium wouldn't have to query random TLDs -- root could just be cached for days. Actually, thinking about caching root, why don't resolvers already cache root? Chrome wouldn't have such an impact if NSEC from root was remembered by resolvers. DNSSEC solves this problem even nowadays.