Why can I acces 1337 through chrome, but not through firefox?
Why can I acces 1337 through chrome, but not through firefox?
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?
You're viewing a single thread.
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.
36 0 ReplyThanks!
3 0 ReplyThat seems as a weird decision by Firefox considering their relatively privacy focused image.
5 2 ReplyNot 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.
21 1 ReplyYeah hiding DNS queries is just one part of the equation. It has to be coupled with other techs/techniques to really achieve privacy.
4 0 Reply
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
1 0 Reply
Followup question, prowlarr seems to have the same issue. Do you know if and how I can setup prowlarr to use couldflare dns?
3 0 Replyprowlarr does not appear to support customizing DNS. You need to alter your DNS on the OS level. Which OS are you using?
2 0 ReplyI 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.
2 0 ReplyYou are welcome and glad that it works eventually.
1 0 Reply
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
1 0 ReplyAnd the issue still persists even after taking those steps?
Does the
dig
command confirm 1.1.1.1 is in use?1 0 ReplyYes. 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!
1 0 Reply
Prowlarr works fine but you need yomething inbetween to solve the CF captcha.
https://github.com/FlareSolverr/FlareSolverrEdit: Using both in a docker container
1 0 Reply
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.
2 0 Reply