valdis.kletnieks@vt.edu wrote on 9/26/2018 1:44 PM:
On Wed, 26 Sep 2018 10:52:07 +0300, Michael Bullut said:
Has anyone deployed the aforementioned in your individual networks? A quick test suggests it is quite fast compared with Google's D.N.S. resolvers: *Reply from 1.1.1.1 <http://1.1.1.1/>: bytes=32 time=3ms TTL=61* 3ms indicates you're hitting an instance that is fairly close by, network-wise.
Looking at your traceroute:
3 7 ms 13 ms 15 ms 10.98.0.233 4 7 ms 5 ms 4 ms one.one.one.one [1.1.1.1]
The instance is apparently on the same subnet as your CGN exit point. As such, unless CloudFlare is deploying a *lot* of anycast instances, most people are not going to have the joyous experience you have.
From my desktop, 1.1.1.1 is 7 network hops away, compared to 8.8.8.8's 10 hops, but the extra 3 hops inside AS15169 probably don't leave the building, and may not even leave the rack. Both are right around 6.9ms away - while *our* network presence there is 4 hops and also 6.9ms away and traceroute is showing jitter larger than the difference between our router and either DNS service...
I'm not a proponent of using 1.1.1.1, but CloudFlare does have a good CDN: Pinging 1.1.1.1 with 32 bytes of data: Reply from 1.1.1.1: bytes=32 time<1ms TTL=58 Reply from 1.1.1.1: bytes=32 time<1ms TTL=58 Reply from 1.1.1.1: bytes=32 time<1ms TTL=58 Reply from 1.1.1.1: bytes=32 time<1ms TTL=58 Tracing route to one.one.one.one [1.1.1.1] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms xxxx 2 <1 ms <1 ms <1 ms xxxx 3 <1 ms <1 ms <1 ms xxxx 4 1 ms 1 ms 1 ms 209.152.151.8 5 1 ms 1 ms 1 ms 38.140.136.177 6 1 ms <1 ms <1 ms 38.140.136.74 7 <1 ms <1 ms <1 ms one.one.one.one [1.1.1.1] Trace complete. dig @1.1.1.1 cloudflare.com | grep 'Query time' ;; Query time: 1 msec dig @1.1.1.1 nanog.org | grep 'Query time' ;; Query time: 28 msec