I don't know, searched here & elsewhere so I'm asking. W7P64. Is using Simple DNSCrypt really beneficial or more of a pita? Can the Cloudflare & the Quad9 DNS servers be trusted? Will using this setup mess with YouTube, Yahoo Sports NHL game of the day, YAHOO! VIEW, GMail & other sites that deliver services based on my location? Thanks.
I don't think that it should have any effect on it. AFAIK only domain name resolution request is performed by those servers. Connection to those services is the same as before.
I use DNSCrypt with Unbound in OpenBSD and used in Gnu/Linux and everything have been fine. Location is recognized by your IP address and/or browser's headers sent to server. BTW You can change automatically recognized location by Youtube settings, even without signing in. https://screenshots.firefox.com/N4T4Vz5MNMWFxrG5/www.youtube.com This will generate URL with location setting, which you can bookamark.
Installed it. Running DNS leak test at dnsleaktest.com the Standard test is taking forever. How can I tell it's working?
I think with this I'm sorted. https://www.wilderssecurity.com/thr...mple-dnscrypt-first-post.388479/#post-2748572
Saw this today: 1.1.1.1: How to use Cloudflare's DNS service to speed up and secure your internet http://www.zdnet.com/article/how-to...0266579295406237784147191&ftag=TRE-03-10aaa6b Using Steve Gibson's DNS Benchmark tool the Cloudflare DNS server was a little faster than Google Public DNS. The two fastest servers IPs identify as NTT.NET; don't know anything about them.
Does anyone know anything about Quad9? Was using Norton DNS until it ended in November. Want to try Quad9, but looked up their corporate address on their website and it is a mail drop called "You Send Me." They have a very professional website and get good reviews. I am just hesitant when they have no real address/building.
I googled quad9 and everything I found was positive, but you probably saw the same stuff. I've been using 1.1.1.1 ( Cloudflare aka Quad1 ) on Firefox and getting good performance. I may set Quad9 ( 9.9.9.9 ) on my Ethernet adapter and see how it performs. Cloudflare and Quad9 appear to have similar features, eg queries over DoH and DoT. I'm not aware of a reason to prefer one over the other at the moment
FYI there are apps for Android for easily switching to 1.1.1.1 or 9.9.9.9. I've tried both and so far 9.9.9.9 is faster and more consistent; I sometimes get site unreachable errors when using 1.1.1.1. I'm going to experiment on my PC as well.
Cisco's OpenDNS is better at blocking malicious domains than Quad9, at least that was the case in 2017. hxxps://medium . com/@nykolas.z/dns-security-filters-compared-quad9-x-opendns-x-comodo-secure-x-norton-connectsafe-x-yandex-safe-a00ace3bf21f Cloudflare does not block malicious domain, but when it comes to privace is more trustworthy, as they have more privacy-friendly privacy policy and are audited by external company.
Neustar has pretty fast servers around the world, I use UltraDNS Business Secure on desktop and Ipredator.se via dnscrypt in the browser. Cleanbrowsing is also pretty good in Europe, but sometimes blocks too much.
This looks like a good spot... I've been using DoH in Firefox 64.0.x and 60esr for some time in Windows 7 and 10. In the latest FF releases, you can toggle DoH realtime to play with it via: Options > General > Network Settings Check Enable DNS over HTTPS That sets the safe & simple mode 2 and mozilla.cloudfare-dns prefs But getting fancy requires manual tweaks in about:config. Last month I went from mode 2 to 3 to bootstrap the address. network.trr.mode = 3 network.trr.uri = https://mozilla.cloudflare-dns.com/dns-query network.trr.bootstrapAddress = 1.1.1.1 (For mode 2, the bootstrapAddress pref is blank.) For sites outside of the "mainstream," there's an occasional, rare actually, "Hmm. We’re having trouble finding that site." page but a click on Try again will bring up the page. I tried Quad9's https://dns.quad9.net/dns-query in mode 2 with success, but 9.9.9.9 mode 3 returned too many of that "trouble finding" indicating a dependence on System DNS. Open about:networking, select DNS, TRR will report true. As will any competent TCP/IP utility, shown here for mode 3: In mode 2, the IP address will be for mozilla.cloudflare-dns.com/dns-query, whatever that might be at any given point in time or place. FWIW at this stage of the game, in 64.0.x you can set network.security.esni.enabled to true. Useful: https://www.ghacks.net/2018/04/02/configure-dns-over-https-in-firefox/ https://daniel.haxx.se/blog/2018/06/03/inside-firefoxs-doh-engine/ https://www.cloudflare.com/ssl/encrypted-sni/ https://whoismydns.com/ https://www.eff.org/deeplinks/2018/09/esni-privacy-protecting-upgrade-https
Simple DNSCrypt, for the Windows platform, uses the local proxy for system DNS. DNSCrypt-Proxy and DoH-proxy for Linux work in the same way, but I can't say 100% for sure since I stopped using Linux way back with Ubuntu v6 and some version of Knoppix and now I'm burning in Hell where I've arranged with The Big Guy for you to work in my division when you get here. Firefox's DoH is internal to itself, ignoring system DNS in trr mode 3, using system DNS as fallback in mode 2. So if your system is set up to use Quad9 or Google or whatever, in mode 2, Firefox will use that if Cloudflare fails. IMHO, mode 2 is obsolete. Mode 3 with Mozilla's uri and bootstrap 1.1.1.1 rocks. All other network facing apps will continue to use the system DNS as they don't care what Firefox is doing for DNS lookups. HTTPS Everywhere is an extension which "consists of a large number of rules for switching sites from HTTP to HTTPS" by "using clever technology to rewrite requests." Source: eff.org The clever tech is Perl.
Sounds like you have a wireless or otherwise weak connection. Firefox has quite a strict timeout for responses before it gives up. In about:config change: Increase it to 10000 or 20000. This should resolve your issue.
@ elapsed - Thanks for the tip. I show 1500 and Stenberg's site cites a default 3000. I did not catch that when I was setting up FF 64 last month. I just verified 1500 as its default by building a fresh profile. It's 3000 in 60esr which is what I was working with (but only mozilla.cloudfare-dns). Hmmmmm... I'm going to give Quad9 another try with higher settings. I prefer them though I'd be giving up Cloudflare's experimental ESNI; not giving up much at this point in time. BTW: Cox Cable 100 Mbps, DOCSIS 3.0, Gigabit LAN, quality CAT6. UPDATE: 3000 helped; 10000 did the trick.