Sep 09 2019 03:26 AM
I gather it is possible to enable it in Chrome by adding some extra runes on the command line, that didn't appear to work on Edge-dev. I don't have Chrome installed, obviously.
Cloudflare has a handy page to test it https://1.1.1.1/help
I've had my DNS entry set to 1.1.1.1 for a while now, it seems quick and reliable, in addition to the 65,000 entries in my hosts file (resolving ad servers to 127.0.0.1), web pages load pretty darn quick.
Jul 28 2020 07:08 AM
Jul 30 2020 01:24 AM
@geek2point0 they pushed a new build of Edge, I'm now on Version 86.0.587.0 (Official build) dev (64-bit)
In the production build ( 84.0.522.48) its at the same url edge://flags/#dns-over-https .
Jul 30 2020 06:00 AM
Aug 11 2020 02:16 AM
@geek2point0 I can see that inside an organisation you wouldn't want some users doing DNS lookups that couldn't be seen by admins. Many orgs run DNS internally, as demonstrated by the rather embarrassing bug last week, (https://www.wired.com/story/sigred-windows-dns-flas-wormable/).
I don't know if this option is turned off by domain membership - perhaps a question for Microsoft? @Elliot Kirk