Firefox enable DNS-over-HTTPS (DoH)

with DNS-over-HTTPS: In June the Mozilla Foundation announced that it was investigating the plugin at a limited level (for Nightly ) of the DNS-over-HTTPS (or DoH) feature in Firefox.

This function uses its DNS service to encrypt both requests and responses to any DNS queries, to increase privacy security for app users.

The Mozilla Foundation has so far been very happy with DoH's performance and said that even the slowest links have made tremendous performance improvements. So Mozilla extends the mood to allow more users to test the DNS-over-HTTPS feature.

"Our initial DoH tests looked at the time it takes to get a response from Cloudflare's DoH resolve," says Mozilla.

"The results were very positive, and the slower users show a huge improvement in performance. A recent test in the Beta channel confirmed that DoH is fast and does not cause problems for our users. "

So if you want to try the new feature, we'll see below how to enable it in your Firefox.

How to enable DNS-over-HTTPS (DoH) in Firefox

DoH is currently being tested, but if you want to use it right away, you can do it by setting it to about: config.

To enable DoH, follow these steps:

Type about: config in the Firefox address bar and press enter. Click the button indicating that you accept the risks.
In the search box, type network.trr to display all settings for Firefox's Trusted Recursive Resolver.
Double-click network.trr.mode, and type 2 in the box. Press OK as shown below. This will trigger DoH in Firefox.

firefox

Then you need to make sure that network.trr.uri is set to https://mozilla.cloudflare-dns.com/dns-query as it is the Cloudflare DoH DNS resolver used by Firefox for testing. If this URL is not set, double-click the setting and enter the URL.
Now you can close the page about: config.

To check if you are using DoH for DNS queries, visit the page Cloudflare Browsing Security Control and click the "Check my browser" button.

The website will carry out various tests to see if you are using , DNSSEC, TLS 1.3 or encrypted SNI.

If the DoH is properly enabled, it should indicate that Secure DNS and TLS 1.3 are enabled as shown below.

So your Firefox will use DoH to resolve its DNS queries .

___________________

iGuRu.gr The Best Technology Site in Greecefgns

every publication, directly to your inbox

Join the 2.100 registrants.

Written by giorgos

George still wonders what he's doing here ...

6 Comments

Leave a Reply
  1. Thanks for the information, and congratulations
    but..
    That way you don't even put one on watch and record you, and sell you?
    whether it is cloudflare or google or a more "private" dns provider.
    Anyway your ISP will download that page you requested eg. so ..
    can still monitor and record ..
    and any third party

    • ..I had received an answer then (probably from George) that ..I forget the encryption – but here:
      https://blog.cloudflare.com/oblivious-dns/ and the naming vendors themselves are now saying we're going to ODNS-ObliviousDNS because ISPs can time-correlate the DNS request with the page you just downloaded..
      Of course - even if the dns query is "encrypted" via https.
      I put the encryption in quotes because it is both standardized and not configurable at will.
      Besides, you have also written about the problems with https.

  2. Good evening my friends.
    First congratulations on both the topics and its presentation.
    On the occasion of this article, I would like your "lights". After following the steps of the map you give, in the check I did in the link that leads us to Cloudflare it shows me that my browser does not use the TLS 1.3 protocol or Encrypted SNI encryption

    The Firefox I have is version 63.0.3 (64bit) The windows of my computer are the "7 PRO" 64 bit. with all the latest updates… and the Cloudflare DNS network settings.

    What mistake or omission can I make?

Leave a reply

Your email address is not published. Required fields are mentioned with *

Your message will not be published if:
1. Contains insulting, defamatory, racist, offensive or inappropriate comments.
2. Causes harm to minors.
3. It interferes with the privacy and individual and social rights of other users.
4. Advertises products or services or websites.
5. Contains personal information (address, phone, etc.).