Could you add a DNS server in Canada?

[zzq...@gmail.com]

Because OpenDNS has added its data centre in Toronto recently (May 21), and I pinged it

IPv4:

Pinging 208.67.222.222 with 32 bytes of data:

Reply from 208.67.222.222: bytes=32 time=11ms TTL=59

Reply from 208.67.222.222: bytes=32 time=12ms TTL=59

Reply from 208.67.222.222: bytes=32 time=11ms TTL=59

Reply from 208.67.222.222: bytes=32 time=12ms TTL=59

Ping statistics for 208.67.222.222:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 11ms, Maximum = 12ms, Average = 11ms

IPv6:

Pinging 2620:0:ccc::2 with 32 bytes of data:

Reply from 2620:0:ccc::2: time=13ms

Reply from 2620:0:ccc::2: time=14ms

Reply from 2620:0:ccc::2: time=14ms

Reply from 2620:0:ccc::2: time=13ms

Ping statistics for 2620:0:ccc::2:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 13ms, Maximum = 14ms, Average = 13ms

It's very fast now. But the only problem is: OpenDNS will redirect you to a search engine when it cannot find a website. But Google DNS won't. If you add a server in Toronto, I'll start using it then. 

[Shen Wan]

What is the latency you get when you ping 8.8.8.8/8.8.4.4? And how about the latency to resolve a domain, OpenDNS vs Google Public DNS?

[zzq...@gmail.com]

IPv4:

Pinging 8.8.8.8 with 32 bytes of data:

Reply from 8.8.8.8: bytes=32 time=39ms TTL=44

Reply from 8.8.8.8: bytes=32 time=41ms TTL=44

Reply from 8.8.8.8: bytes=32 time=42ms TTL=44

Reply from 8.8.8.8: bytes=32 time=38ms TTL=44

Ping statistics for 8.8.8.8:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 38ms, Maximum = 42ms, Average = 40ms

IPv6: 

Pinging 2001:4860:4860::8888 with 32 bytes of data:

Reply from 2001:4860:4860::8888: time=45ms

Reply from 2001:4860:4860::8888: time=41ms

Reply from 2001:4860:4860::8888: time=43ms

Reply from 2001:4860:4860::8888: time=42ms

Ping statistics for 2001:4860:4860::8888:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 41ms, Maximum = 45ms, Average = 42ms

[Shen Wan]

Your latency to 8.8.8.8 is normal. Actually the ping latency from my home to 8.8.8.8 is very similar to yours. We'd like our network latency to all our users to be as low as possible. Unfortunately, it is impossible to deploy servers close to everyone in the world.

Please see https://developers.google.com/speed/public-dns/faq#tools and test to find the fasted DNS resolver for your location. If the test shows that Google Public DNS is significantly slower than OpenDNS, please share your result with us.

[zzq...@gmail.com]

I know why Google DNS is slower, because some websites are resolved to servers far from me (I live near Toronto). For example: www.facebook.com is resolved to 31.13.73.* (55ms), using carrier DNS is 31.13.74.* (25ms), OpenDNS is 31.13.71.* (25ms). www.sohu.com is resolved 202.55.12.17 (245ms) in Hong Kong, using carrier DNS and OpenDNS will be 66.102.246.139 (121ms) in western US. 

[Shen Wan]

This is because some of www.sohu.com's nameservers (61.135.150.76 and 61.135.179.169) are dropping queries from Google Public DNS. Therefore we have to query their nameservers at Asia (221.179.180.22) and get www.sohu.com resolved to an IP address in Hong Kong. Please contact Sohu to solve this issue.

For Facebook, please see: https://developers.google.com/speed/public-dns/faq#cdn for an explanation.

[zzq...@gmail.com]

OK, I give up using Google DNS and use OpenDNS instead

1. OpenDNS has a data centre in Toronto.

2. As of June 6th, all of OpenDNS’s users will get NXDOMAIN and SERVFAIL messages to get truly RFC compliant DNS, no more ads, no more DNS hijacking

3. OpenDNS will lead me to a nearest server

4. China has blocked Google, so more and more sites in China can't be resolved by Google DNS

[Shen Wan]

Thanks for letting us know your concerns about using Google Public DNS! We strive to server our users the best DNS service.

1. We may deploy resolvers in Canada in the future.

2. Glad to see OpenDNS becoming ad-free. Although they are still not fully RFC compliant.

3. For nameservers supporting ECS, we will return best results. Unfortunately Facebook is not using ECS yet. See: https://developers.google.com/speed/public-dns/faq#cdn

4. Only a few websites are limiting Google Public DNS's queries. We hope this is temporary.