4 ms·

All the more reason to stay with Firefox.

garren 6y ago
And/or NextDNS.io - Uncloaking cloaked domains is primary what brought me to the service. Added benefits include service across all browsers, all devices, local/mobile etc.
- ray991 6y ago
  But that is just swapping one privacy issue with another, as NextDNS is also free to sell user’s private metadata to data brokers. https://news.ycombinator.com/item?id=23318830 https://news.ycombinator.com/item?id=23318830
dhimes 6y ago
One problem I seem to be having with FF (on Win 10 anyway) is it's not checking my hosts file for a domain lookup before using dns. Overriding the hosts file makes some things easier so I tend to do it. But now, my first time trying from Win, and it's not getting my page. Chrome works, ssh from WSL works, but FF uses dns first, apparently. It's the first development usage I've found that Chrome works better than FF.
- airstrike 6y ago
  Well, that just means Firefox is winning this war by, what, 79–1 rather than 80-0
  - dhimes 6y ago
    Agree.
- mrj 6y ago
  Yeah I had that problem too after they shipped encrypted dns. You can turn that off and it'll work normally.
  - dhimes 6y ago
    OK thank you!
- deadbunny 6y ago
  Are you using (or have been subjected to) Firefox enabling DNS over http? IIRC it's auto enabled for users in the US.
- jlgaddis 6y ago
  If you want to use DNS-over-HTTPS, you can add domain names to "network.trr.excluded-domains" in "about:config" (if, for example, you always use the .dev TLD for custom hostnames in your hosts file, you can simply exclude that domain name). If not, well, just disable DNS-over-HTTPS entirely. See https://wiki.mozilla.org/Trusted_Recursive_Resolver https://wiki.mozilla.org/Trusted_Recursive_Resolver for even more DoH-related settings you can tweak.
  - dhimes 6y ago
    Thank you- that's very helpful!
ta17711771 6y ago
Or Chromium variants, if security is important to you.
- ta17711771 6y ago
  See: per site isolation, Firefox X11 exploit, etc

And/or NextDNS.io - Uncloaking cloaked domains is primary what brought me to the service. Added benefits include service across all browsers, all devices, local/mobile etc.

ray991 6y ago
But that is just swapping one privacy issue with another, as NextDNS is also free to sell user’s private metadata to data brokers. https://news.ycombinator.com/item?id=23318830 https://news.ycombinator.com/item?id=23318830

dhimes 6y ago

One problem I seem to be having with FF (on Win 10 anyway) is it's not checking my hosts file for a domain lookup before using dns. Overriding the hosts file makes some things easier so I tend to do it. But now, my first time trying from Win, and it's not getting my page. Chrome works, ssh from WSL works, but FF uses dns first, apparently. It's the first development usage I've found that Chrome works better than FF.

airstrike 6y ago
Well, that just means Firefox is winning this war by, what, 79–1 rather than 80-0
- dhimes 6y ago
  Agree.
mrj 6y ago
Yeah I had that problem too after they shipped encrypted dns. You can turn that off and it'll work normally.
- dhimes 6y ago
  OK thank you!
deadbunny 6y ago
Are you using (or have been subjected to) Firefox enabling DNS over http? IIRC it's auto enabled for users in the US.
jlgaddis 6y ago
If you want to use DNS-over-HTTPS, you can add domain names to "network.trr.excluded-domains" in "about:config" (if, for example, you always use the .dev TLD for custom hostnames in your hosts file, you can simply exclude that domain name). If not, well, just disable DNS-over-HTTPS entirely. See https://wiki.mozilla.org/Trusted_Recursive_Resolver https://wiki.mozilla.org/Trusted_Recursive_Resolver for even more DoH-related settings you can tweak.
- dhimes 6y ago
  Thank you- that's very helpful!

ta17711771 6y ago

Or Chromium variants, if security is important to you.

ta17711771 6y ago
See: per site isolation, Firefox X11 exploit, etc