Cloudflare's new DNS

sajunky · Apr 5, 2018

Year 2018 will set a milestone in securing DNS. It looks like DNS over TLS is going to be implemented in the first place, see: https://tools.ietf.org/html/rfc8310

I expect that hardware routers are not ready yet. What software is available now for PC if I want to test it with Cloudflare (by example)?

[EDIT] I see there is a proxy client for Windows an other OS's available for download from the Cloudflare website: https://developers.cloudflare.com/1.1.1.1/dns-over-https/cloudflared-proxy/

Genisys · Apr 5, 2018

ActivateD said:
I wonder what Cisco will do with their devices that use 1.1.1.1 for guest hotspots.

It shouldn't be a big problem realistically, it isn't their responsibility to make sure network Admins change IP addresses or set up equipment properly.

Rickster · Apr 5, 2018

This new DNS was making my internet kuk, it was buffering youtube at 144p.

Bryn · Apr 5, 2018

Rickster said:
This new DNS was making my internet kuk, it was buffering youtube at 144p.

Did you reboot your router? Is your ISP Telkom?

Working perfectly for me.

infscrtyrisk · Apr 6, 2018

Rickster said:
This new DNS was making my internet kuk, it was buffering youtube at 144p.

um, forgive me, I am slow

You are going to have to explain this one to me, how exactly does DNS cause youtube buffering?

Thor · Apr 6, 2018

Web Africa

Code:

[email protected]:~$ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=55 time=118 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=55 time=143 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=55 time=97.2 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=55 time=151 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=55 time=138 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=55 time=213 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=55 time=162 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=55 time=159 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=55 time=119 ms
64 bytes from 1.1.1.1: icmp_seq=10 ttl=55 time=115 ms
64 bytes from 1.1.1.1: icmp_seq=11 ttl=55 time=119 ms
64 bytes from 1.1.1.1: icmp_seq=12 ttl=55 time=114 ms
64 bytes from 1.1.1.1: icmp_seq=13 ttl=55 time=104 ms
^C
--- 1.1.1.1 ping statistics ---
14 packets transmitted, 13 received, 7% packet loss, time 13018ms
rtt min/avg/max/mdev = 97.250/135.159/213.151/30.016 ms
[email protected]:~$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=35.1 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=54 time=34.8 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=54 time=34.3 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=54 time=35.0 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=54 time=34.9 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=54 time=35.0 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=54 time=34.8 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=54 time=34.7 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=54 time=34.8 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=54 time=34.9 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=54 time=34.9 ms
64 bytes from 8.8.8.8: icmp_seq=12 ttl=54 time=34.8 ms
64 bytes from 8.8.8.8: icmp_seq=13 ttl=54 time=34.8 ms
^C
--- 8.8.8.8 ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 12017ms
rtt min/avg/max/mdev = 34.381/34.897/35.126/0.293 ms
[email protected]:~$

Sinbad · Apr 6, 2018

infscrtyrisk said:
um, forgive me, I am slow You are going to have to explain this one to me, how exactly does DNS cause youtube buffering?

If it resolves the cdn to an ip far away from you.....

Pho3nix · Apr 6, 2018

Thor said:

Web Africa

Code:

[email protected]:~$ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=55 time=118 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=55 time=143 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=55 time=97.2 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=55 time=151 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=55 time=138 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=55 time=213 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=55 time=162 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=55 time=159 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=55 time=119 ms
64 bytes from 1.1.1.1: icmp_seq=10 ttl=55 time=115 ms
64 bytes from 1.1.1.1: icmp_seq=11 ttl=55 time=119 ms
64 bytes from 1.1.1.1: icmp_seq=12 ttl=55 time=114 ms
64 bytes from 1.1.1.1: icmp_seq=13 ttl=55 time=104 ms
^C
--- 1.1.1.1 ping statistics ---
14 packets transmitted, 13 received, 7% packet loss, time 13018ms
rtt min/avg/max/mdev = 97.250/135.159/213.151/30.016 ms
[email protected]:~$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=35.1 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=54 time=34.8 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=54 time=34.3 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=54 time=35.0 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=54 time=34.9 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=54 time=35.0 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=54 time=34.8 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=54 time=34.7 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=54 time=34.8 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=54 time=34.9 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=54 time=34.9 ms
64 bytes from 8.8.8.8: icmp_seq=12 ttl=54 time=34.8 ms
64 bytes from 8.8.8.8: icmp_seq=13 ttl=54 time=34.8 ms
^C
--- 8.8.8.8 ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 12017ms
rtt min/avg/max/mdev = 34.381/34.897/35.126/0.293 ms
[email protected]:~$

Glad to see you back

Bryn · Apr 6, 2018

Thor said:

Web Africa

Code:

[email protected]:~$ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=55 time=118 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=55 time=143 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=55 time=97.2 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=55 time=151 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=55 time=138 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=55 time=213 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=55 time=162 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=55 time=159 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=55 time=119 ms
64 bytes from 1.1.1.1: icmp_seq=10 ttl=55 time=115 ms
64 bytes from 1.1.1.1: icmp_seq=11 ttl=55 time=119 ms
64 bytes from 1.1.1.1: icmp_seq=12 ttl=55 time=114 ms
64 bytes from 1.1.1.1: icmp_seq=13 ttl=55 time=104 ms
^C
--- 1.1.1.1 ping statistics ---
14 packets transmitted, 13 received, 7% packet loss, time 13018ms
rtt min/avg/max/mdev = 97.250/135.159/213.151/30.016 ms
[email protected]:~$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=35.1 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=54 time=34.8 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=54 time=34.3 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=54 time=35.0 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=54 time=34.9 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=54 time=35.0 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=54 time=34.8 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=54 time=34.7 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=54 time=34.8 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=54 time=34.9 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=54 time=34.9 ms
64 bytes from 8.8.8.8: icmp_seq=12 ttl=54 time=34.8 ms
64 bytes from 8.8.8.8: icmp_seq=13 ttl=54 time=34.8 ms
^C
--- 8.8.8.8 ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 12017ms
rtt min/avg/max/mdev = 34.381/34.897/35.126/0.293 ms
[email protected]:~$

Something I've wondered is whether there's any value to pinging DNS addresses, seeing as ping and nslookup are useless for diagnosing DNS issues.

Thor · Apr 6, 2018

Bryn said:
Something I've wondered is whether there's any value to pinging DNS addresses, seeing as ping and nslookup are useless for diagnosing DNS issues.

True.

infscrtyrisk · Apr 7, 2018

Sinbad said:
If it resolves the cdn to an ip far away from you.....

I see. But I disagree -- it's not the DNS that is the root cause of the buffering...

Sinbad · Apr 7, 2018

infscrtyrisk said:
I see. But I disagree -- it's not the DNS that is the root cause of the buffering...

Well... It could be that it's sending you to a cdn node in Japan or something and there's just not a lot of bandwidth between here and there...

HeftyCrab · Apr 7, 2018

Rickster said:
This new DNS was making my internet kuk, it was buffering youtube at 144p.

Try OpenDns.

According to Cloudflare its the second fastest.

Also, im pretty sure if Cloudflare was faster you wouldn't notice the speed difference.

sajunky · Apr 7, 2018

Bryn said:
Something I've wondered is whether there's any value to pinging DNS addresses, seeing as ping and nslookup are useless for diagnosing DNS issues.

It is useful as it show routing problems on your IS provider backbone, something we have to resolve with our ISP.

I agree. Not related to the testing DNS, but it is something we have to start from. Having the same on Telkom cellular.

Gnome · Apr 9, 2018

1.1.1.1 does not break whitelisted Geolocating IPs. As I understand it both YouTube and Netflix are whitelisted.

Web-Africa likely hosts their own YouTube caches. eg. https://news.ycombinator.com/item?id=16733814

Sinbad · Apr 9, 2018

Gnome said:
1.1.1.1 does not break whitelisted Geolocating IPs. As I understand it both YouTube and Netflix are whitelisted.

Web-Africa likely hosts their own YouTube caches. eg. https://news.ycombinator.com/item?id=16733814

1.1.1.1 resolves Google.co.za to an overseas address for me

Gnome · Apr 9, 2018

Sinbad said:
1.1.1.1 resolves Google.co.za to an overseas address for me

That makes sense. Google.co.za != YouTube

Google will give you targeted ads based on location, so it makes sense to block them

The_Mowgs · Apr 26, 2018

I hope someone can help me with this. How do I set this DNS on a mikrotik router with routeros 6.40.5?

Bryn · Apr 26, 2018

The_Mowgs said:
I hope someone can help me with this. How do I set this DNS on a mikrotik router with routeros 6.40.5?

I'm not familiar with Mikrotik, but changing your DNS should be dead simple. Just find the spot where you enter your ISP account details and somewhere around there you should see an option for DNS.

Pr0zac · Apr 27, 2018

The_Mowgs said:
I hope someone can help me with this. How do I set this DNS on a mikrotik router with routeros 6.40.5?

I'm only on RouterOS v6.33.1 on my hAP Lite, but it was under IP > DNS for me.

Your ISP usually has their local DNS servers populated there. Just click the drop down arrows and apply the DNS addresses where required. I personally, while still just testing, put CloudFlare's set as 1st and 2nd, Google's set as 3rd and 4th. and I left my local ISP's set as 5th and 6th just in case. Will obviously remove the unnecessary ones accordingly now, since I've been using it for several weeks and all seems well.

Join the MyBroadband community

Get started

Cloudflare's new DNS

Honorary Master

Honorary Master

EVGA Fanatic

Doubleplusgood

Expert Member

Honorary Master

Honorary Master

The Legend

Doubleplusgood

Honorary Master

Expert Member

Honorary Master

Expert Member

Honorary Master

Executive Member

Honorary Master

Executive Member

Honorary Master

Doubleplusgood

Active Member