Forum Discussion
Dev channel update to 80.0.345.0 is live
Enabling edge://flags/#dns-over-https doesn't seem to do anything, 1.1.1.1/help shows that DoH is not enabled.
DoH in Firefox works fine, and 1.1.1.1/help shows that DoH is enabled when visiting it from Firefox.
Canary 80.0.351.0 but probably same story with current Dev build.
keyblade wrote:
Is DNS-over-HTTPS not supported properly yet?
Enabling edge://flags/#dns-over-https doesn't seem to do anything, 1.1.1.1/help shows that DoH is not enabled.
DoH in Firefox works fine, and 1.1.1.1/help shows that DoH is enabled when visiting it from Firefox.
Canary 80.0.351.0 but probably same story with current Dev build.Hi,
try setting your DNS in your Windows IPv4 settings
I set it only in my router and the cloudflare DNS test didn't detect it, but after setting it in the Windows 10 IPv4 setting, it worked.
Edge insider Version 80.0.351.0 (Official build) canary (64-bit)
Also to be more secure, use it system wide, Simple DNSCrypt:
Do NOT manually set your DNS IPs if you're in an Active Directory environment. You'll have a bad day.
CurtisBrabham wrote:Do NOT manually set your DNS IPs if you're in an Active Directory environment. You'll have a bad day.
Of course 🙂
that was for personal computers, local AD joined computers (non-admins) wouldn't even be able to change their DNS without the required permissions.
though AAD (Azure AD) devices won't be having any problems if they change their DNS ^^
Hmm, yeah, forcing DNS in adapter settings works although I had to do /flushdns in addition to that. Well, still I would've really preferred if DoH in Edge was set up similar to Firefox without relying on the DNS set in the network adapter settings so hopefully MS will make it work similar to FF.
The way it works in Firefox is you have a separate option for DoH in the network settings page where you can use custom DNS address or use Clourflare (comes as a default), no DNS setup required in the adapter settings.
I think Chrome either doesn't require DNS set in adapter setting or you can circumvent it by using launch parameters in addition to enable DoH flag.Yeah i would like something like that too. Firefox uses its own network settings, you can set proxy settings inside Firefox that will only apply to it and not the rest of the system, SOCKS5, HTTP, HTTPS/SSL etc, even DNS over SOCKS5
I remember creating a topic about it 2 months ago
https://techcommunity.microsoft.com/t5/Discussions/Add-SOCKS5-Authentication-support-to-Edge-insider-browser/m-p/908994
but didn't receive so much attention from developers unfortunatelyno Google chrome needed to set DNS in network adapter in order for cloudflare website to detect the DoH, it was exactly like Edge insider, I'm using Edge and Chrome both Canary channels.
- I use quad9 dns in the Ipv4 settings, but with the flag enabled, Edge changes them to cloudflare ones and doh is enabled
FedeDiLo wrote:
I use quad9 dns in the Ipv4 settings, but with the flag enabled, Edge changes them to cloudflare ones and doh is enabledThat's weird, in the flag description there is no mention of Cloudflare
Secure DNS lookups
Enables DNS over HTTPS. When this feature is enabled, your browser may try to use a secure HTTPS connection to look up the addresses of websites and other web resources. – Mac, Windows
#dns-over-httpsthere are lots of DNS servers offering their services over HTTPS, I wonder why Edge uses Cloudflare by default!
- It's working for me on Dev 80.0.334.4
