What is DNS over HTTPS ? Well it’s basically an encrypted way of querying DNS. Normally DNS uses port 53 to communicate with the server and query the name we want. But all of that traffic is in plain-text and thus it is very easy to poison that communication. DNS over HTTPS is secure because it uses certificates to encrypt traffic (just like HTTPS websites).

Mozilla Firefox makes it very easy to enable this feature. Just open the settings and search for “DNS over HTTPS”:

In the connection settings enable DNS over HTTPS. You could also add a custom provider. Here is a good list: https://github.com/curl/curl/wiki/DNS-over-HTTPS#publicly-available-servers

Microsoft Edge does not have a user-friendly way of activating the feature (yet).

In the edge://flags/ search for “DNS” and you will find the corresponding setting:

Unfortunately Microsoft Edge does not allow custom providers. Hopefully they will one day.

Microsoft yesterday announced in their blog post that the Beta Build of their Edge Browser is generally available.

If you don’t know yet, Microsoft is replacing “old” Edge which had the EdgeHTML rendering engine with Chromium, a rendering engine Chrome also uses.

To this day, two channels were available for use: Canary and Dev. Canary updates daily and Dev weekly. The Beta channel should be a stable release containing the properly tested features and updates every 6 weeks.

Enterprise Customers can also download the Policy Files with the Administrative Templates (.admx). Some interesting settings are roaming profiles and Internet Explorer Mode. Roaming profiles make the deployment in RDS (formerly Terminal Services) environments very appealing.

Microsoft Edge can be downloaded here – you have the option to download any of the 3 different builds.