How to Enable or Disable DNS over HTTPS (DoH) in Microsoft Edge  

zebal said:

Therefore DNS servers specified in NIC?
my NIC has custom DNS servers not the ones provided by router via DHCP.

Correct. Use current service provider is to use your current DNS provider.

Thanks for confirming @Cliff S and @Brink

zebal said:

Thanks for confirming @Cliff S and @Brink

zebal said:

Thanks for confirming @Cliff S and @Brink

You're welcome

I was hoping I can pick your brain on this. Suddenly out of the blue, my Edge has "disabled" this function saying there is a policy for it, but when I check there is no policy for this, so why could it be doing this?



So I go and take a look at the policy to see what's what. As you can see, there is nothing there (other than the force disabling of Microsoft automatically logging into every god damn thing without permission, I don't need all my work accounts having their activity on their servers).



To the best of my knowledge, this has nothing to do with the DOH policy, so why is it disabling this feature? It almost feels like M$ passive aggressive screw you but being a professional, I would like to understand the actual mechanism and reason behind it and less an emotionally annoyed reaction.

I selected the "Show policies with no value" so I can isolate the one that controls DOH so we can see that it indeed is not touched, so should not be affected.



Any idea what's going on here? I can't imagine the 1 policy in effect (which semantics aside is absurd they consider that, managed by organization) is affecting this, right? Especially that after I set this policy, DOH was working just fine, so unless a more recent update changed the behavior of this policy to also block DOH, makes no sense to me. I considered explicitly setting DOH in the policy (a la force it) but I feel that should be so unnecessary and feels too hacky to get it working when it should not be affected.

Thoughts? Suggestions? Insights? Any is appreciated, thank you.

Hello @On10,

Double check the registry location in option two to see if the BuiltInDnsClientEnabled DWORD has been set or not.

Brink said:

Hello @On10,
Double check the registry location in option two to see if the BuiltInDnsClientEnabled DWORD has been set or not.

Thank you, I checked and unless I am reading this wrong, it is not:

On10 said:

Thank you, I checked and unless I am reading this wrong, it is not:

You're not wrong. That policy is not set.

I suppose you can make sure Windows 10 DNS is set below how you want for Edge to use.

Change IPv4 and IPv6 DNS Server Address in Windows

Brink said:

You're not wrong. That policy is not set.I suppose you can make sure Windows 10 DNS is set below how you want for Edge to use.Change IPv4 and IPv6 DNS Server Address in Windows

I already have that setup, my interfaces are configured accordingly, aka WIFI is on one configuration, ETH is on another, and so are the VPN.

But the ability to switch on the fly is necessary for testing and the feature is supposed to be available so I don't want to just "live with it" if you will on a global level or keep messing with my system's global DNS settings just to test something in Edge, you know what I mean? It is neither good nor feasible.

Do we know why it is behaving this way when it shouldn't?

On10 said:

I already have that setup, my interfaces are configured accordingly, aka WIFI is on one configuration, ETH is on another, and so are the VPN.

But the ability to switch on the fly is necessary for testing and the feature is supposed to be available so I don't want to just "live with it" if you will on a global level or keep messing with my system's global DNS settings just to test something in Edge, you know what I mean? It is neither good nor feasible.

Do we know why it is behaving this way when it shouldn't?

If you haven't already you could check to see if a edge://flags flag may have been set causing this.