I suppose that's probably thanks to caching, dedicated apps for many websites, and most users sticking to a relatively small selection of websites.
I suppose that's probably thanks to caching, dedicated apps for many websites, and most users sticking to a relatively small selection of websites.
It’s, I believe, those servers that hit the root DNS servers when they don’t have the data.
Plus, the answers returned by the root servers more often than not include resource records with very high TTL values (e.g., NS RRs with a TTL of two days). These then get cached for that long by the recursive resolvers that are used (directly) by end users.
The root servers aren't responding to requests for the A RR for google.com from Joe Schmoe or the MX RR for gmail.com from Outlook running on his desktop -- both of which (without checking) likely have TTLs measured in a two- or (at the most) three-digit number of seconds.