It appears that 1.1.1.1 might already be suffering the pressure of early adopters already, showing significantly slower response times than their secondary IP of 1.0.0.1, so you may want to set 1.0.0.1 as your primary and 1.1.1.1 as your secondary. Some things I noticed on this run, and subsequent runs. DNS Performance Analytics and Comparison screenshot from Apr 01 2018. Then I set my router's DNS cache feature to zero, and ran DNS Benchmark again, and have posted one preliminary screenshot below. First, I just ran it, adding CloudFlare's 1.1.1.1 primary and 1.0.0.1 secondary IP addresses, along with Quad9's 9.9.9.9 primary and 149.112.112.112 secondary DNSs. So once again, DNS Benchmark came in handy for my own testing at my own 06109 location, so I decided to retest. The thing is, DNS is very location specific, so your results will vary from what DNSPerf indicates. Nevertheless, this new service is real, and it's here, and the speeds claims appear to be pretty remarkable, especially when you look at the DNSPerf site that Tom mentions. Well, I can say I saw this one coming, with today being a rather peculiar day for an announcement. So it seemed clear that 4/1 (April 1st) was the date we needed to launch it. The only question that remained was when to launch the new service? This is the first consumer product Cloudflare has ever launched, so we wanted to reach a wider audience.

Announcing 1.1.1.1: the fastest, privacy-first consumer DNS service.

Posted by Paul Braren on (updated on Apr 4 2018) in

Norton connectsafe vs opendns