Outcome: You’ll enable DNS over HTTPS (DoH) in Firefox so your DNS lookups are encrypted and usually faster.

Who this is for: Firefox users on Windows, macOS, Linux, or Android who want more private browsing without installing extensions.

Time required: About 1 minute.

Quick Answer

Open Firefox → Settings → Privacy & Security → DNS over HTTPS, switch it to Enable, pick a provider like Cloudflare, then restart Firefox and test with a DNS leak check. You’ll keep normal browsing while hiding DNS queries from your ISP.

What this trick does (and what it doesn’t)

DNS over HTTPS encrypts DNS lookups (the “what site is this?” request) between Firefox and your DNS provider. That helps block ISP DNS snooping and can speed up domain lookups. It is not a full VPN, so your IP/location behavior stays the same.

Prerequisites

  • Firefox 62 or newer
  • Internet connection
  • Optional: a preferred DoH provider (Cloudflare, NextDNS, etc.)

Step-by-step: Enable DNS over HTTPS in Firefox

  1. Open Firefox Settings.
    Click the menu button (☰) in the top-right, then click Settings.

    Expected result: You land on the Firefox Settings page.

  2. Go to Privacy & Security.
    In the left sidebar, click Privacy & Security.

    Expected result: You see privacy controls and security settings.

  3. Find DNS over HTTPS and enable it.
    Scroll to the DNS over HTTPS section, choose Enable, then select a provider (for most users, Cloudflare works well).

    Expected result: DNS over HTTPS status is enabled and a provider is selected.

  4. Restart Firefox and test.
    Close and reopen Firefox. Then run a quick DNS leak check.

    Expected result: Leak test should show your chosen resolver instead of your ISP DNS in most setups.

Expected result checks

  • Web pages resolve normally after restart (no DNS errors).
  • DNS leak test reflects your selected DoH provider.
  • Browsing feels the same or slightly faster on first page loads.

Common mistakes

  • Forgetting to select a provider: DoH is enabled but provider is not set as expected.
  • Testing before restart: Old DNS cache can make test results confusing.
  • Mixing browser DNS with VPN assumptions: DoH protects DNS requests, not all traffic metadata.
  • Using captive portals (hotel/airport Wi-Fi): DoH can sometimes interfere until login is completed.

Quick troubleshooting

  • Pages won’t load after enabling DoH: Toggle DoH off, reconnect, then re-enable.
  • Captive portal won’t open: Temporarily disable DoH, complete login page, then turn it back on.
  • Still looks like ISP DNS: Clear cache/restart and retest; switch provider if needed.
  • Network policy blocks DoH: On work/school networks, you may need to leave DoH disabled due to policy controls.

Reference links

Related tech tricks

Next step

If this worked, do one more 60-second privacy upgrade: switch your browser’s default search engine to one with stronger privacy defaults, then compare page-load speed and DNS leak results again.