said by TSI Marc:
yeah but that doesn't lead to better performance.. you want records that are accurate to stay cached so their response is fast.. having to go query the auth dns server where the records are hosted is the part that takes the longest...
Understood. It wasn't to suggest it would improve performance. It would improve accuracy though. It's a trade off.
If it's 100-500ms (500 would be terrible) every 10-60 minutes that get hit with the latency, I don't think it would even be noticeable, if you look at the average response time.
Also, the end-users computer would respect the TTL in its DNS cache, so it would only be new requests.
You could override this TTL cap for the top 1% of the queries, fairly easily, which would give you better performance for most sites, and better accuracy for the 'long tail'.
Just throwing some (unrequested) ideas out there.