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?
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
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
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
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.
Thanks!
That seems as a weird decision by Firefox considering their relatively privacy focused image.
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.
Yeah hiding DNS queries is just one part of the equation. It has to be coupled with other techs/techniques to really achieve privacy.
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
Maybe a little off-topic, but I found this useful to explain difference between DoT and DoH: https://www.cloudflare.com/learning/dns/dns-over-tls/
Turns out I am using DoT instead of DoH. Both are encrypted, but DoT is distinguishable from HTTPS traffic.
Followup question, prowlarr seems to have the same issue. Do you know if and how I can setup prowlarr to use couldflare dns?
Prowlarr works fine but you need yomething inbetween to solve the CF captcha.
https://github.com/FlareSolverr/FlareSolverr
Edit: Using both in a docker container
prowlarr does not appear to support customizing DNS. You need to alter your DNS on the OS level. Which OS are you using?
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
And the issue still persists even after taking those steps?
Does the
digcommand confirm 1.1.1.1 is in use?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!
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.
You are welcome and glad that it works eventually.