[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
CloudFlare D.N.S. Resolvers... (220.127.116.11 & 18.104.22.168)
- Subject: CloudFlare D.N.S. Resolvers... (22.214.171.124 & 126.96.36.199)
- From: valdis.kletnieks at vt.edu (valdis.kletnieks at vt.edu)
- Date: Wed, 26 Sep 2018 14:44:20 -0400
- In-reply-to: <[email protected]om>
- References: <[email protected]om>
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 188.8.131.52 <http://184.108.40.206/>: 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 [220.127.116.11]
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, 18.104.22.168 is 7 network hops away, compared to 22.214.171.124'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...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 486 bytes
Desc: not available