I'm still left with little understanding of why this is important? What is the use of these lookups for the browser? A previously undisclosed security feature? And what is being alleged from the name service side? A unintentional DOS-type attack on the root server system itself? CAS. On Tue, 25 Aug 2020, 3:39 pm Dev Anand Teelucksingh, <devtee@gmail.com> wrote:
The Chromium browser—open source, upstream parent to both Google Chrome and the new Microsoft Edge—is getting some serious negative attention for a well-intentioned feature that checks to see if a user's ISP is "hijacking" non-existent domain results.
The Intranet Redirect Detector <https://bugs.chromium.org/p/chromium/issues/detail?id=1090985>, which makes spurious queries for random "domains" statistically unlikely to exist, is responsible for roughly half of the total traffic the world's root DNS servers receive. Verisign engineer Matt Thomas wrote a lengthy APNIC blog post <https://blog.apnic.net/2020/08/21/chromiums-impact-on-root-dns-traffic/> outlining the problem and defining its scope.
Read rest of Ars Technica article :
https://arstechnica.com/gadgets/2020/08/a-chrome-feature-is-creating-enormou...
The APNIC blog post : https://blog.apnic.net/2020/08/21/chromiums-impact-on-root-dns-traffic/
Not aware if this is mentioned before in ICANN circles
Dev Anand
_______________________________________________ ttf mailing list ttf@atlarge-lists.icann.org https://mm.icann.org/mailman/listinfo/ttf
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.