Re: [PLUG] [xpost] Cloudflare announces DNS Resolver 1.1.1.1 (on 4/1)
Without doing much/any testing, from experience I use two different DNS one from google and other from OpenDNS. (But I change it if I suspect any latitude depending upon political turmoil in country or otherwise.) This combination helps for me because ISP DNS can play tricks and some providers insist their DNS inclusion for service performance. There maybe forums which are off-limit to ISP DNS but are better shielded differently by OpenDNS and likes. ISP's DNS may get subjected to Govt. whims which isn't necessarily so with others above. Again wherever possible I follow govt. recommendations on deleting certain apps on (y)our mobile. But I have found some of it stupid is because govt. itself modified the list later and excluded a couple from it. On Monday 09 April 2018 11:59 AM, Amey Abhyankar wrote: On 2 April 2018 at 10:18, Arun Khanwrote: On Sun, Apr 1, 2018 at 9:01 PM, Gaurav Pant wrote: Hi, On Mon, Apr 2, 2018 at 12:45 AM, Arun Khan wrote: Cloudflare announces public DNS servers 1.1.1.1 and 1.0.0.1 on 4/1 (April 1). NO -- it’s not an April Fool’s joke. Scroll down to the end of the blog. Looks like one :) tried to ping 1.1.1.1 no reply. Ping response is not necessarily a good test. After all, many servers are configured to drop ICMP echo request to avoid DDoS. I did end user testing over the weekend. Equipments & softwares used as follows = Ubuntu 16.04 , Mozilla & Chrome browsers, HP i5 powered latest gen laptop, 2mbps broadband connection over RJ11, TP Link wifi router with 1.1.1.1 manually fixed DNS, performed rounds of tcpdumps to ensure all traffic is using 1.1.1.1 DNS server, confirmed speed over sppedtest before proceeding My observations as follows = - Indian web-sites take lot of time to load for example zee5.com. - Few services gave location unknown error - Browsing of YouTube video's was ok but not that great [Not streaming but loading list of videos while scrolling] - Facebook,twitter,linkedin browsing was slow - Overall web browsing slowed down & in later stage died loading basic search engine pages like bing,duckduckgo. - AWS dashboards & console took significant time to load - Not frequently used/accessed web sites like slack.com died loading several times in multiple browsers Conclusion = After switching to ISP's DNS, everything got resumed as expected. Regards, Amey. Try: host www.google.com 1.1.1.1 and you will get a response (see below). Using domain server: Name: 1.1.1.1 Address: 1.1.1.1#53 Aliases: www.google.com has address 172.217.194.99 www.google.com has address 172.217.194.103 www.google.com has address 172.217.194.104 www.google.com has address 172.217.194.105 www.google.com has address 172.217.194.106 www.google.com has address 172.217.194.147 www.google.com has IPv6 address 2404:6800:4003:c00::6a -- Arun. ___ plug-mail mailing list plug-mail@plug.org.in http://list.plug.org.in/listinfo/plug-mail ___ plug-mail mailing list plug-mail@plug.org.in http://list.plug.org.in/listinfo/plug-mail -- -- Consultant Spirituel Guruvision Inc. ___ plug-mail mailing list plug-mail@plug.org.in http://list.plug.org.in/listinfo/plug-mail
Re: [PLUG] [xpost] Cloudflare announces DNS Resolver 1.1.1.1 (on 4/1)
> Conclusion = > After switching to ISP's DNS, everything got resumed as expected. > While I have not done such extensive "study", I have reached the same conclusion over the years. I use GoogleDNS as a backup, but generally switching "back" to ISP's DNS improves things a lot. I would be interested to know why (and if there is anything we can do) -Mandar ___ plug-mail mailing list plug-mail@plug.org.in http://list.plug.org.in/listinfo/plug-mail
Re: [PLUG] [xpost] Cloudflare announces DNS Resolver 1.1.1.1 (on 4/1)
On 2 April 2018 at 10:18, Arun Khanwrote: > On Sun, Apr 1, 2018 at 9:01 PM, Gaurav Pant wrote: >> Hi, >> >> On Mon, Apr 2, 2018 at 12:45 AM, Arun Khan wrote: >>> >>> Cloudflare announces public DNS servers 1.1.1.1 and 1.0.0.1 on 4/1 (April >>> 1). >>> >>> NO -- it’s not an April Fool’s joke. Scroll down to the end of the blog. >> >> >> Looks like one :) tried to ping 1.1.1.1 no reply. >> > > Ping response is not necessarily a good test. After all, many servers > are configured to drop ICMP echo request to avoid DDoS. I did end user testing over the weekend. Equipments & softwares used as follows = Ubuntu 16.04 , Mozilla & Chrome browsers, HP i5 powered latest gen laptop, 2mbps broadband connection over RJ11, TP Link wifi router with 1.1.1.1 manually fixed DNS, performed rounds of tcpdumps to ensure all traffic is using 1.1.1.1 DNS server, confirmed speed over sppedtest before proceeding My observations as follows = - Indian web-sites take lot of time to load for example zee5.com. - Few services gave location unknown error - Browsing of YouTube video's was ok but not that great [Not streaming but loading list of videos while scrolling] - Facebook,twitter,linkedin browsing was slow - Overall web browsing slowed down & in later stage died loading basic search engine pages like bing,duckduckgo. - AWS dashboards & console took significant time to load - Not frequently used/accessed web sites like slack.com died loading several times in multiple browsers Conclusion = After switching to ISP's DNS, everything got resumed as expected. Regards, Amey. > > Try: > > host www.google.com 1.1.1.1 > > and you will get a response (see below). > > Using domain server: > Name: 1.1.1.1 > Address: 1.1.1.1#53 > Aliases: > > www.google.com has address 172.217.194.99 > www.google.com has address 172.217.194.103 > www.google.com has address 172.217.194.104 > www.google.com has address 172.217.194.105 > www.google.com has address 172.217.194.106 > www.google.com has address 172.217.194.147 > www.google.com has IPv6 address 2404:6800:4003:c00::6a > > -- Arun. > ___ > plug-mail mailing list > plug-mail@plug.org.in > http://list.plug.org.in/listinfo/plug-mail ___ plug-mail mailing list plug-mail@plug.org.in http://list.plug.org.in/listinfo/plug-mail
Re: [PLUG] [xpost] Cloudflare announces DNS Resolver 1.1.1.1 (on 4/1)
On Tue, Apr 3, 2018 at 11:39 PM, Dhanesh B. Sabanewrote: > At bottom:- > > On Tuesday 03 April 2018 03:55 PM, शंतनू wrote: >> Looks like 139.59.23.241 (NIC's opennic) which has 34.113 ms response >> time is better than 8.8.8.8 (google) which has 70.512 ms response time >> is better than 1.1.1.1 (cloudflare) which has 73.364 ms response time. >> > > There's a post on Medium [1] which compares the performance of DNS > Resolvers and CloudFlare comes up to be the winner in almost all the > test cases. > > [1] > https://medium.com/@nykolas.z/dns-resolvers-performance-compared-cloudflare-x-google-x-quad9-x-opendns-149e803734e5 > Tried https://github.com/cleanbrowsing/dnsperftest. $ bash ./dnstest.sh test1 test2 test3 test4 test5 test6 test7 test8 test9 test10 Average 209.222.18.222283 ms 1000 ms 267 ms 357 ms 264 ms 264 ms 1000 ms 266 ms 272 ms 267 ms424.00 209.222.18.218278 ms 268 ms 317 ms 1000 ms 269 ms 1000 ms 277 ms 259 ms 259 ms 1000 ms 492.70 cloudflare73 ms 75 ms 76 ms 73 ms 72 ms 1000 ms 77 ms 72 ms 75 ms 78 ms 167.10 google79 ms 63 ms 62 ms 74 ms 78 ms 427 ms 60 ms 74 ms 80 ms 84 ms 108.10 quad9 74 ms 65 ms 66 ms 67 ms 70 ms 65 ms 66 ms 66 ms 67 ms 65 ms 67.10 opendns 177 ms 67 ms 63 ms 62 ms 117 ms 258 ms 80 ms 127 ms 171 ms 62 ms 118.40 norton64 ms 59 ms 60 ms 59 ms 61 ms 64 ms 61 ms 60 ms 63 ms 66 ms 61.70 cleanbrowsing 71 ms 69 ms 124 ms 81 ms 67 ms 66 ms 68 ms 72 ms 68 ms 67 ms 75.30 yandex151 ms 195 ms 152 ms 169 ms 1000 ms 260 ms 170 ms 155 ms 155 ms 191 ms259.80 adguard 1000 ms 171 ms 156 ms 155 ms 158 ms 169 ms 170 ms 165 ms 158 ms 161 ms246.30 neustar 223 ms 218 ms 240 ms 287 ms 287 ms 216 ms 220 ms 322 ms 1000 ms 315 ms332.80 comodo145 ms 140 ms 138 ms 140 ms 145 ms 140 ms 145 ms 136 ms 140 ms 140 ms140.90 opennic 63 ms 62 ms 61 ms 62 ms 74 ms 75 ms 64 ms 66 ms 65 ms 61 ms 65.30 localhost 1 ms1 ms1 ms1 ms44 ms 1 ms34 ms 1 ms1 ms38 ms 12.30 opennic is 139.59.23.241 localhost is dnsmasq server running locally. BYOD...Bring Your Own DNS ;) -- शंतनू > -- > Dhanesh B. Sabane > https://dhanesh95.gitlab.io > > > ___ > plug-mail mailing list > plug-mail@plug.org.in > http://list.plug.org.in/listinfo/plug-mail > ___ plug-mail mailing list plug-mail@plug.org.in http://list.plug.org.in/listinfo/plug-mail
Re: [PLUG] [xpost] Cloudflare announces DNS Resolver 1.1.1.1 (on 4/1)
At bottom:- On Tuesday 03 April 2018 03:55 PM, शंतनू wrote: > Looks like 139.59.23.241 (NIC's opennic) which has 34.113 ms response > time is better than 8.8.8.8 (google) which has 70.512 ms response time > is better than 1.1.1.1 (cloudflare) which has 73.364 ms response time. > There's a post on Medium [1] which compares the performance of DNS Resolvers and CloudFlare comes up to be the winner in almost all the test cases. [1] https://medium.com/@nykolas.z/dns-resolvers-performance-compared-cloudflare-x-google-x-quad9-x-opendns-149e803734e5 -- Dhanesh B. Sabane https://dhanesh95.gitlab.io signature.asc Description: OpenPGP digital signature ___ plug-mail mailing list plug-mail@plug.org.in http://list.plug.org.in/listinfo/plug-mail
Re: [PLUG] [xpost] Cloudflare announces DNS Resolver 1.1.1.1 (on 4/1)
Looks like 139.59.23.241 (NIC's opennic) which has 34.113 ms response time is better than 8.8.8.8 (google) which has 70.512 ms response time is better than 1.1.1.1 (cloudflare) which has 73.364 ms response time. $ ping -c 5 139.59.23.241 PING 139.59.23.241 (139.59.23.241): 56 data bytes 64 bytes from 139.59.23.241: icmp_seq=0 ttl=54 time=33.574 ms 64 bytes from 139.59.23.241: icmp_seq=1 ttl=54 time=35.030 ms 64 bytes from 139.59.23.241: icmp_seq=2 ttl=54 time=33.392 ms 64 bytes from 139.59.23.241: icmp_seq=3 ttl=54 time=32.447 ms 64 bytes from 139.59.23.241: icmp_seq=4 ttl=54 time=36.122 ms --- 139.59.23.241 ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 32.447/34.113/36.122/1.301 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=46 time=68.970 ms 64 bytes from 8.8.8.8: icmp_seq=1 ttl=46 time=70.793 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=46 time=75.928 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=46 time=68.875 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=46 time=67.993 ms --- 8.8.8.8 ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 67.993/70.512/75.928/2.857 ms $ 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=54 time=75.831 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=54 time=74.279 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=54 time=73.743 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=54 time=71.254 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=54 time=71.711 ms --- 1.1.1.1 ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 71.254/73.364/75.831/1.688 ms On Mon, Apr 2, 2018 at 10:18 AM, Arun Khanwrote: > On Sun, Apr 1, 2018 at 9:01 PM, Gaurav Pant wrote: >> Hi, >> >> On Mon, Apr 2, 2018 at 12:45 AM, Arun Khan wrote: >>> >>> Cloudflare announces public DNS servers 1.1.1.1 and 1.0.0.1 on 4/1 (April >>> 1). >>> >>> NO -- it’s not an April Fool’s joke. Scroll down to the end of the blog. >> >> >> Looks like one :) tried to ping 1.1.1.1 no reply. >> > > Ping response is not necessarily a good test. After all, many servers > are configured to drop ICMP echo request to avoid DDoS. > > Try: > > host www.google.com 1.1.1.1 > > and you will get a response (see below). > > Using domain server: > Name: 1.1.1.1 > Address: 1.1.1.1#53 > Aliases: > > www.google.com has address 172.217.194.99 > www.google.com has address 172.217.194.103 > www.google.com has address 172.217.194.104 > www.google.com has address 172.217.194.105 > www.google.com has address 172.217.194.106 > www.google.com has address 172.217.194.147 > www.google.com has IPv6 address 2404:6800:4003:c00::6a > > -- Arun. > ___ > plug-mail mailing list > plug-mail@plug.org.in > http://list.plug.org.in/listinfo/plug-mail ___ plug-mail mailing list plug-mail@plug.org.in http://list.plug.org.in/listinfo/plug-mail
Re: [PLUG] [xpost] Cloudflare announces DNS Resolver 1.1.1.1 (on 4/1)
On Sun, Apr 1, 2018 at 9:01 PM, Gaurav Pantwrote: > Hi, > > On Mon, Apr 2, 2018 at 12:45 AM, Arun Khan wrote: >> >> Cloudflare announces public DNS servers 1.1.1.1 and 1.0.0.1 on 4/1 (April >> 1). >> >> NO -- it’s not an April Fool’s joke. Scroll down to the end of the blog. > > > Looks like one :) tried to ping 1.1.1.1 no reply. > Ping response is not necessarily a good test. After all, many servers are configured to drop ICMP echo request to avoid DDoS. Try: host www.google.com 1.1.1.1 and you will get a response (see below). Using domain server: Name: 1.1.1.1 Address: 1.1.1.1#53 Aliases: www.google.com has address 172.217.194.99 www.google.com has address 172.217.194.103 www.google.com has address 172.217.194.104 www.google.com has address 172.217.194.105 www.google.com has address 172.217.194.106 www.google.com has address 172.217.194.147 www.google.com has IPv6 address 2404:6800:4003:c00::6a -- Arun. ___ plug-mail mailing list plug-mail@plug.org.in http://list.plug.org.in/listinfo/plug-mail
Re: [PLUG] [xpost] Cloudflare announces DNS Resolver 1.1.1.1 (on 4/1)
Hi, On Mon, Apr 2, 2018 at 12:45 AM, Arun Khanwrote: > Cloudflare announces public DNS servers 1.1.1.1 and 1.0.0.1 on 4/1 (April > 1). > > NO -- it’s not an April Fool’s joke. Scroll down to the end of the blog. > Looks like one :) tried to ping 1.1.1.1 no reply. > https://blog.cloudflare.com/dns-resolver-1-1-1-1/amp/ > > Don’t believe it? Pinch yourself and test it out! > > -- Arun Khan > ___ > plug-mail mailing list > plug-mail@plug.org.in > http://list.plug.org.in/listinfo/plug-mail > Gaurav Pant -- --- http://OpenSourceCook.in If you can cook, you can code. ___ plug-mail mailing list plug-mail@plug.org.in http://list.plug.org.in/listinfo/plug-mail
[PLUG] [xpost] Cloudflare announces DNS Resolver 1.1.1.1 (on 4/1)
Cloudflare announces public DNS servers 1.1.1.1 and 1.0.0.1 on 4/1 (April 1). NO -- it’s not an April Fool’s joke. Scroll down to the end of the blog. https://blog.cloudflare.com/dns-resolver-1-1-1-1/amp/ Don’t believe it? Pinch yourself and test it out! -- Arun Khan ___ plug-mail mailing list plug-mail@plug.org.in http://list.plug.org.in/listinfo/plug-mail