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?

  • Qazwsxedcrfv000A
    link
    fedilink
    English
    36
    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.

    • @[email protected]OP
      link
      fedilink
      English
      31 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?

      • Qazwsxedcrfv000A
        link
        fedilink
        English
        21 year ago

        prowlarr does not appear to support customizing DNS. You need to alter your DNS on the OS level. Which OS are you using?

        • @[email protected]OP
          link
          fedilink
          English
          21 year ago

          I think it just neede some time to sink in, or just another restart, but today everything just qorks. Thanks for your help anyways, I appriciate it.

        • @[email protected]OP
          link
          fedilink
          English
          11 year ago

          Linux Ubuntu. What I’ve done so far is change the nameserver in resolv.conf to 1.1.1.1 and installed resolveconf to make it permanent. Basically these steps

          • Qazwsxedcrfv000A
            link
            fedilink
            English
            11 year ago

            And the issue still persists even after taking those steps?

            Does the dig command confirm 1.1.1.1 is in use?

            • @[email protected]OP
              link
              fedilink
              English
              11 year ago

              Yes. Unfortunately prowlarr seems to have stopped working all together. Some issue with sqlite and there not being a “user” table. It is not my day!

    • @[email protected]
      link
      fedilink
      English
      31 year ago

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

      • Deluxeparrot
        link
        fedilink
        English
        201 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.

        • Qazwsxedcrfv000A
          link
          fedilink
          English
          41 year ago

          Yeah hiding DNS queries is just one part of the equation. It has to be coupled with other techs/techniques to really achieve privacy.

      • @[email protected]
        cake
        link
        fedilink
        English
        11 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