I found out today that I can change my dns to acces 1337.to again. My ISP was blocking it. However, it works on chrome, but not on firefox. Why doesn’t it work on firefox?

  • Qazwsxedcrfv000@lemmy.unknownsys.com
    link
    fedilink
    English
    arrow-up
    31
    ·
    edit-2
    1 year ago

    Chrome has DNS-over-HTTPS enabled by default. Firefox, however, enables that by default in certain regions only.

    Cloudflare has a comprehensive guide on how to enable it in various browsers.

    P.S. If you dun wanna use Cloudflare as the resolver, quad9 can be an (maybe better) option.

    • abbadon420@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      Followup question, prowlarr seems to have the same issue. Do you know if and how I can setup prowlarr to use couldflare dns?

    • whiskers@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      2
      ·
      1 year ago

      That seems as a weird decision by Firefox considering their relatively privacy focused image.

      • Deluxeparrot@feddit.uk
        link
        fedilink
        English
        arrow-up
        20
        arrow-down
        1
        ·
        1 year ago

        Not really as hiding dns alone doesn’t give you a big increase in privacy. Your isp can see what sites you visit immediately after anyway.

        It could be argued that sending all your dns requests to a 3rd party by default is actually a decrease in privacy.

      • luffylemmy85@feddit.nl
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        1.https does not mean more private. for regular browsing it does not matter 2. it is always good to have 2 browsers or use containers to seperate personal and regular stuff