kizer Posted April 2, 2018 Share Posted April 2, 2018 https://www.theverge.com/2018/4/1/17185732/cloudflare-dns-service-1-1-1-1 Will it? Wont it? Who knows, but it is an alternative now I guess. You can check it out directly here. https://1.1.1.1 https://1.0.0.1/ ***************************** Edited for some more Clarity************************** Quote Link to comment
1812 Posted April 2, 2018 Share Posted April 2, 2018 (edited) when i ping couldflare dns vs google, its does show a few milliseconds faster response (~17ms vs 20ms) but what will i do with all those spare milliseconds that i've saved? edit for the real response-- i actually switched over and am getting significantly faster page load times. Edited April 2, 2018 by 1812 Quote Link to comment
kizer Posted April 2, 2018 Author Share Posted April 2, 2018 Not only are they talking about decent speeds, but as well they are talking about how they scrub their info every day so nothing is logged/tracked.. Or something like that. Quote Link to comment
NewDisplayName Posted April 3, 2018 Share Posted April 3, 2018 (edited) Hm, i cant even ping 1.1.1.1??? But backup works 1.0.0.1 Ping wird ausgeführt für 1.0.0.1 mit 32 Bytes Daten: Antwort von 1.0.0.1: Bytes=32 Zeit=29ms TTL=53 Antwort von 1.0.0.1: Bytes=32 Zeit=29ms TTL=53 Antwort von 1.0.0.1: Bytes=32 Zeit=28ms TTL=53 Antwort von 1.0.0.1: Bytes=32 Zeit=99ms TTL=53 (which is pretty bad, i guess, that spike) Edited April 3, 2018 by nuhll Quote Link to comment
1812 Posted April 3, 2018 Share Posted April 3, 2018 this is what I get right now: PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=57 time=15.443 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=57 time=11.656 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=57 time=10.335 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=57 time=11.292 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=57 time=19.991 ms --- 1.1.1.1 ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 10.335/13.743/19.991/3.575 ms Ping has started… PING 1.0.0.1 (1.0.0.1): 56 data bytes 64 bytes from 1.0.0.1: icmp_seq=0 ttl=57 time=19.941 ms 64 bytes from 1.0.0.1: icmp_seq=1 ttl=57 time=11.005 ms 64 bytes from 1.0.0.1: icmp_seq=2 ttl=57 time=10.411 ms 64 bytes from 1.0.0.1: icmp_seq=3 ttl=57 time=17.225 ms 64 bytes from 1.0.0.1: icmp_seq=4 ttl=57 time=17.853 ms --- 1.0.0.1 ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 10.411/15.287/19.941/3.850 ms 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=12.502 ms 64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=15.370 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=15.928 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=11.646 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=10.418 ms --- 8.8.8.8 ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 10.418/13.173/15.928/2.135 ms looks like google cranked up the response from my testing yesterday... Quote Link to comment
c3 Posted April 3, 2018 Share Posted April 3, 2018 I wear a tinfoil hat (and thus use pihole) ping is not a test of dns performance. Checkout DNS Benchmark Quote Link to comment
unevent Posted April 3, 2018 Share Posted April 3, 2018 ...or not use a DNS forwarder at all, run your own resolver. Quote Link to comment
c3 Posted April 3, 2018 Share Posted April 3, 2018 27 minutes ago, unevent said: ...or not use a DNS forwarder at all, run your own resolver. Actually I do, but that test was against pihole not bind. Quote Link to comment
NewDisplayName Posted April 3, 2018 Share Posted April 3, 2018 (edited) Ofc you cant only determine the speed by ping, but i guess google wont do internally anything different then cloudflare, so i guess, the ping is able to show some performance. But i test with dns benchmark! edit:The DNS resolver your system is using is responding faster than any of the 100% reliable publicly available alternative DNS nameservers this benchmark utility just tested. Therefore, there would be no performance benefit from switching to any of those publicly available nameservers. yea, like i thought (local DNS is 8.8.8.8 or 8.8.4.4) i added 1.1.1.1 and 1.0.0.1 to the test. Edited April 3, 2018 by nuhll Quote Link to comment
Hoopster Posted April 3, 2018 Share Posted April 3, 2018 (edited) I get 3ms pings to 1.1.1.1 and 1.0.0.1, 34ms pings to 8.8.8.8 and 47ms pings to 8.8.4.4. Repeated tests are consistently within 1ms of those times. I have to admit 3/4ms is very fast. Cloudflare would certainly be faster for me than Google DNS. Here are the results of DNS Benchmark (the top entry is my Pihole currently pointing to Google): Edited April 3, 2018 by Hoopster Quote Link to comment
dalben Posted April 4, 2018 Share Posted April 4, 2018 Tried here in SG and Cloudfare are running 3rd. 8. 8. 4. 4 | Min | Avg | Max |Std.Dev|Reliab%| ----------------+-------+-------+-------+-------+-------+ - Cached Name | 0.001 | 0.002 | 0.002 | 0.000 | 100.0 | - Uncached Name | 0.004 | 0.050 | 0.256 | 0.078 | 100.0 | - DotCom Lookup | 0.007 | 0.036 | 0.174 | 0.060 | 100.0 | ---<-------->---+-------+-------+-------+-------+-------+ google-public-dns-b.google.com GOOGLE - Google LLC, US 8. 8. 8. 8 | Min | Avg | Max |Std.Dev|Reliab%| ----------------+-------+-------+-------+-------+-------+ - Cached Name | 0.002 | 0.002 | 0.004 | 0.000 | 100.0 | - Uncached Name | 0.005 | 0.055 | 0.291 | 0.083 | 100.0 | - DotCom Lookup | 0.007 | 0.030 | 0.174 | 0.054 | 100.0 | ---<-------->---+-------+-------+-------+-------+-------+ google-public-dns-a.google.com GOOGLE - Google LLC, US 208. 67.220.220 | Min | Avg | Max |Std.Dev|Reliab%| ----------------+-------+-------+-------+-------+-------+ - Cached Name | 0.001 | 0.002 | 0.002 | 0.000 | 100.0 | - Uncached Name | 0.003 | 0.126 | 0.408 | 0.115 | 100.0 | - DotCom Lookup | 0.040 | 0.205 | 0.472 | 0.128 | 100.0 | ---<O-OOO-OO>---+-------+-------+-------+-------+-------+ resolver2.opendns.com OPENDNS - OpenDNS, LLC, US 208. 67.222.123 | Min | Avg | Max |Std.Dev|Reliab%| ----------------+-------+-------+-------+-------+-------+ - Cached Name | 0.002 | 0.002 | 0.003 | 0.000 | 100.0 | - Uncached Name | 0.003 | 0.127 | 0.460 | 0.134 | 100.0 | - DotCom Lookup | 0.009 | 0.232 | 0.479 | 0.135 | 100.0 | ---<O-OOO-OO>---+-------+-------+-------+-------+-------+ resolver1-fs.opendns.com OPENDNS - OpenDNS, LLC, US 208. 67.222.222 | Min | Avg | Max |Std.Dev|Reliab%| ----------------+-------+-------+-------+-------+-------+ - Cached Name | 0.002 | 0.002 | 0.004 | 0.000 | 100.0 | - Uncached Name | 0.002 | 0.136 | 0.539 | 0.149 | 100.0 | - DotCom Lookup | 0.046 | 0.199 | 0.409 | 0.100 | 100.0 | ---<O-OOO-OO>---+-------+-------+-------+-------+-------+ resolver1.opendns.com OPENDNS - OpenDNS, LLC, US 208. 67.220.123 | Min | Avg | Max |Std.Dev|Reliab%| ----------------+-------+-------+-------+-------+-------+ - Cached Name | 0.002 | 0.002 | 0.004 | 0.000 | 100.0 | - Uncached Name | 0.003 | 0.139 | 0.447 | 0.122 | 100.0 | - DotCom Lookup | 0.039 | 0.231 | 0.467 | 0.106 | 100.0 | ---<O-OOO-OO>---+-------+-------+-------+-------+-------+ resolver2-fs.opendns.com OPENDNS - OpenDNS, LLC, US 1. 0. 0. 1 | Min | Avg | Max |Std.Dev|Reliab%| ----------------+-------+-------+-------+-------+-------+ - Cached Name | 0.002 | 0.003 | 0.005 | 0.000 | 100.0 | - Uncached Name | 0.003 | 0.098 | 0.235 | 0.096 | 100.0 | - DotCom Lookup | 0.009 | 0.100 | 0.210 | 0.092 | 100.0 | ---<-------->---+-------+-------+-------+-------+-------+ 1dot1dot1dot1.cloudflare-dns.com CLOUDFLARENET - Cloudflare, Inc., US 1. 1. 1. 1 | Min | Avg | Max |Std.Dev|Reliab%| ----------------+-------+-------+-------+-------+-------+ - Cached Name | 0.002 | 0.003 | 0.004 | 0.001 | 100.0 | - Uncached Name | 0.003 | 0.100 | 0.288 | 0.094 | 100.0 | - DotCom Lookup | 0.168 | 0.185 | 0.232 | 0.013 | 100.0 | ---<-------->---+-------+-------+-------+-------+-------+ 1dot1dot1dot1.cloudflare-dns.com MEGAPATH2-US - MegaPath Networks Inc., US 208. 67.222.220 | Min | Avg | Max |Std.Dev|Reliab%| ----------------+-------+-------+-------+-------+-------+ - Cached Name | 0.002 | 0.003 | 0.004 | 0.001 | 100.0 | - Uncached Name | 0.003 | 0.138 | 0.520 | 0.150 | 100.0 | - DotCom Lookup | 0.004 | 0.204 | 0.470 | 0.113 | 100.0 | ---<O-OOO-OO>---+-------+-------+-------+-------+-------+ resolver3.opendns.com OPENDNS - OpenDNS, LLC, US Quote Link to comment
pwm Posted April 4, 2018 Share Posted April 4, 2018 Interesting that they have two machines with different IP but same hostname: 1. 0. 0. 1 | 1dot1dot1dot1.cloudflare-dns.com 1. 1. 1. 1 | 1dot1dot1dot1.cloudflare-dns.com 1 Quote Link to comment
jbartlett Posted April 13, 2018 Share Posted April 13, 2018 My results with Frontier FiOS out of the Seattle area. My pings for Cloudflare & Google were 3-4 ms, with Cloudflare getting about 1ms better on average. I'm updating my DNS settings to 1.0.0.1 & 8.8.4.4 Quote Link to comment
NewDisplayName Posted July 26, 2018 Share Posted July 26, 2018 just btw, even the ping times are a little lower with this new service, i get from time to time ping loss to 1.1.1.1, but not to 8.8.8.8 results in "this webpage cant be reached" messages fromt ime to time, i switched back to 8.8.8.8 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.