4 ms·
Fairly certain this feature is more then ten years old.
by floil 6y ago
Fairly certain this feature is more then ten years old.
- gbil 6y agohttps://cloud.google.com/docs/chrome-enterprise/policies/?policy=DNSInterceptionChecksEnabled https://cloud.google.com/docs/chrome-enterprise/policies/?po... Google Chrome (Linux, Mac, Windows) since version 80 Google Chrome OS (Google Chrome OS) since version 80 Chrome 80: February 4, 2020 and as a clarification When you connect via VPN to the corporate network the DNS queries are not distributes as when you are in the office. You have a X amount of entry points for the VPN which are served by Y DNS servers which is less than the total amount of DNS servers available in the corporate network. Plus the amount of remote users increased vastly, plus the VPN technology used plus the DNS servers used. Not that simple I'm afraid
- joshuamorton 6y agoThe article mentions relevant code changes in 2014. It seems like the enterprise policy may be recent, but the feature is much older.
- gbil 6y agoSure and I explained why it hit us when it hit us Also keep in mind that Edge is chromium based now and has the same issue. And is becoming the standard by MS and thus the impact is increased now because of this
- joshuamorton 6y agoSure, lockdown and increased VPN use makes sense as to why this got painful in march. However I expect GP was quibbling with this part of your statement: >Furthermore if I remember correctly this "feature" in chrome was enabled in a version which was distributed to our clients maybe a month before the lockdowns so there was little time to see the effect while clients were still in the office Which claims that the feature was rolled out recently.
- gbil 6y agoFair enough, but I wrote if I remember correctly which obsiously I didn't and confused when we got hit by it with the actual implementation
- drivebycomment 6y agoThe article has a nice graph that shows when the feature was introduced - 2010.