This looks good, but I assume that any DNS request I make is still routed through my ISP. Therefore, I assume there is no way to stop my ISP from keeping a log of every URL I visit. Is that correct?
[deleted]
1.1.1.1: Fast, privacy-first consumer DNS service
391–400 of 695 posts
Re: 1.1.1.1: Fast, privacy-first consumer DNS service
#392Earlier quoted context omitted.
No it wouldn't. They're both encrypted with the same method so they can't tell whether http is used or not.
Sorry, confused. Https requests are prolific, while encrypted DNS requests aren't. Why isn't the former less hard to detect?
How would you tell that an encrypted chunk of data is HTTPS instead of DNS? The best you'd be able to do is guess based on behavior that it's DNS.
Re: 1.1.1.1: Fast, privacy-first consumer DNS service
#393>"And we wanted to put our money where our mouth was, so we committed to retaining KPMG, the well-respected auditing firm, to audit our code and practices annually and publish a public report confirming we're doing what we said we would." It's worth pointing out that KPMG was Wells Fargo's independent auditor while the bank recently committed fraud on a massive scale by creating more than a million fake deposit accou…
I've worked with KPMG subsidiary for security audit. This is an E&Y kind of company, where you pay x4 to work with the least competent people because you need a familiar name stamped on some report.
Re: 1.1.1.1: Fast, privacy-first consumer DNS service
#394I still find myself wondering about things like the iphones DNS service though. You can’t change it while connected to a cell network and it always seemed strange to me that was considered okay.
You can change the iPhone DNS servers by installing a profile. Apps like "DNS Override" (not a recommendation) will do it for you.
Re: 1.1.1.1: Fast, privacy-first consumer DNS service
#395And look at these ping times: CloudFlare Google DNS Quad9 OpenDNS NewYork 2 msec 1 msec 2 msec 19 msec Toronto 2 msec 28 msec 17 msec 27 msec Atlanta 1 msec 2 msec 1 msec 19 msec Dallas 1 msec 9 msec 1 msec 7 msec San Francisco 3 msec 21 msec 15 msec 20 msec London 1 msec 12 msec 1 msec 14 msec Amsterdam 2 msec 6 msec 1 msec 6 msec Frankfurt 1 msec 9 msec 2 msec 9 msec Tokyo 2 msec 2 msec 81 msec 77 msec Singapore 2…
Note, from Google Compute Engine use 8.8.8.8 as it should always be faster. I'm guessing the 8.8.8.8 service exists in every Google Cloud region. Even better use the default GCE autogenered DNS IP that they configure in /etc/resolv.conf to get instance name resolving magic.
Re: 1.1.1.1: Fast, privacy-first consumer DNS service
#396$ ping 1.1.1.1 PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=47 time=214.866 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=47 time=173.416 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=45 time=256.007 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=45 time=196.638 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=45 time=294.694 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=45 time=314.883 ms 64 bytes from 1.1.1.1: ic…
From Norway (fiber), seems to be a bit faster than google:
$ ping -c 5 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: icmp_seq=0 ttl=60 time=1.606 ms
64 bytes from 1.1.1.1: icmp_seq=1 ttl=60 time=1.562 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=60 time=1.540 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=60 time=1.574 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=60 time=1.564 ms
--- 1.1.1.1 ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 1.540/1.569/1.606/0.022 ms
$ ping -c 5 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=57 time=9.068 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=8.923 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=8.974 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=8.916 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=8.931 ms
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 8.916/8.962/9.068/0.057 ms
Re: 1.1.1.1: Fast, privacy-first consumer DNS service
#397Does Windows/all my devices support DNS-over-HTTPS (or TLS) right now?
I.e. if I set everything to use 1.1.1.1, will all my devices know to use the secure protocols, or will it be regular old unsecure DNS?
Re: 1.1.1.1: Fast, privacy-first consumer DNS service
#398Here are instructions for testing DoH (DNS-over-HTTPS) in Firefox Nightly:
https://gist.github.com/mcmanus/766a9564a51325b6543644983539...
Re: 1.1.1.1: Fast, privacy-first consumer DNS service
#399For the Cloudflare folks hanging around:
Please, please, please add some basic "features" (like Google does) that will help when troubleshooting resolution!
For example, the following will show the unicast IP address of the server you're hitting when using 8.8.8.8:
$ dig @8.8.8.8 txt o-o.myaddr.l.google.com. +short
$ dig @8.8.8.8 txt locations.publicdns.goog. +short
Re: 1.1.1.1: Fast, privacy-first consumer DNS service
#400And look at these ping times: CloudFlare Google DNS Quad9 OpenDNS NewYork 2 msec 1 msec 2 msec 19 msec Toronto 2 msec 28 msec 17 msec 27 msec Atlanta 1 msec 2 msec 1 msec 19 msec Dallas 1 msec 9 msec 1 msec 7 msec San Francisco 3 msec 21 msec 15 msec 20 msec London 1 msec 12 msec 1 msec 14 msec Amsterdam 2 msec 6 msec 1 msec 6 msec Frankfurt 1 msec 9 msec 2 msec 9 msec Tokyo 2 msec 2 msec 81 msec 77 msec Singapore 2…
Where are you testing from? I'm going to guess: a datacenter. Residential customers won't see anything this fast. I'm in a small town in Kansas, connected by 1 Gbit ATT fiber. I'm getting ~26ms to 1.1.1.1 and ~19ms to my private DNS resolver that I host in a datacenter in Dallas. Google DNS comes in around 19ms. I suspect that Cloudflare and Google DNS both have POPs in Dallas, which accounts for the similar numbers…
Small village next to a provincial town in Europe on Cable: getting 11ms avg.