Google DNS in Italy

[Fabio Ancona]

Hi.

I'm in Italy and my ISP is Telecom Italia (also know as TIM).

I'm connected on Internet with a fast 100 Mb/sec line.

Months ago I was able to ping 8.8.8.8 and 8.8.4.4 in about 12 milliseconds and the DNS query was fast.

Now, from the same Internet line, I reach 8.8.8.8 and 8.8.4.4 in about 45 milliseconds and so the query are less fast.

See traceroute from Italy:

root@raspberry:~# traceroute 8.8.8.8

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets

 1  192.168.1.1 (192.168.1.1)  0.872 ms  0.962 ms  1.114 ms

 2  * * *

 3  172.17.161.93 (172.17.161.93)  7.328 ms 172.17.161.221 (172.17.161.221)  7.746 ms 172.17.162.33 (172.17.162.33)  7.663 ms

 4  172.17.160.149 (172.17.160.149)  11.880 ms 172.17.160.93 (172.17.160.93)  11.575 ms  11.486 ms

 5  172.17.4.28 (172.17.4.28)  24.709 ms 172.17.4.30 (172.17.4.30)  21.919 ms  21.836 ms

 6  etrunk15.milano1.mil.seabone.net (93.186.128.217)  24.222 ms etrunk11.milano50.mil.seabone.net (93.186.128.229)  21.102 ms etrunk15.milano1.mil.seabone.net (93.186.128.217)  17.829 ms

 7  72.14.204.72 (72.14.204.72)  17.507 ms 72.14.195.206 (72.14.195.206)  19.262 ms 72.14.203.52 (72.14.203.52)  20.169 ms

 8  216.239.54.119 (216.239.54.119)  20.268 ms 216.239.47.128 (216.239.47.128)  43.515 ms 209.85.241.94 (209.85.241.94)  20.863 ms

 9  108.170.233.11 (108.170.233.11)  61.183 ms 209.85.243.33 (209.85.243.33)  50.912 ms 216.239.58.10 (216.239.58.10)  39.775 ms

10  66.249.95.150 (66.249.95.150)  47.989 ms 64.233.174.143 (64.233.174.143)  52.796 ms  46.454 ms

11  108.170.234.47 (108.170.234.47)  50.160 ms 209.85.243.65 (209.85.243.65)  54.240 ms 209.85.248.71 (209.85.248.71)  42.255 ms

12  * * *

13  google-public-dns-a.google.com (8.8.8.8)  42.764 ms  42.018 ms  45.582 ms

root@raspberry:~#

May be there was Google Public DNS in Italy and since some months there is not more?

Is there a possibility to recover Google Public DNS in Italy to reduce latency time and so to have DNS query more fast?

Or is it a routing problem of Telecom Italia (my ISP)?

Thanks!

[Alex Dupuy]

Google's services and locations are described and mapped at https://peering.google.com/#/infrastructure.

While Google Public DNS is not provided at all of the locations mapped, there is cache capability located at most of the Edge PoPs.

Normal maintenance, unusual outages, routing issues, and large internet traffic shifts may cause the specific set of locations providing Google Public DNS caching to change without notice. In many cases, increased latency from such changes is not that significant for the total query load (although always-in-cache popular domains are likely to be more affected).

Usually the anycast routing for 8.8.8.8, 8.8.4.4, and the IPv6 addresses will take you to the nearest location with Google Public DNS functions, but it can be that certain networks "hardwire" particular peers in their routing tables, causing traffic to flow to an offline location, from whence it has to travel over Google's internal networks to reach the Public DNS service. This can be slower than if your queries went directly to another location, depending on many factors. So it is possible that your problems are related to a combination of an Google Public DNS edge location status change and routing issues with your ISP.

I can't offer anything more than that, except to recommend that you be thankful you aren't located in Australia, where the impact of changes like these is much more extreme.

[Fabio Ancona]

Hi Alex and thanks for your answer.

Google Edge PoP is available also in Italy (in Milano).

The strange is that Google DNS Servers are available also on the Edge PoPs, but why my traceroute does not reach Milano (Milan) where there is a Google Edge PoP?

Just for your info, others traceroute to others Google services (goolge.com, youtube.com, photos.google.com, etc..) are correctly routed to Milano.

See that examples:

  

root@raspberry:~# traceroute www.youtube.com

traceroute to www.youtube.com (216.58.205.206), 30 hops max, 60 byte packets

 1  192.168.147.1 (192.168.147.1)  0.848 ms  0.933 ms  1.706 ms

 2  * * *

 3  172.17.161.97 (172.17.161.97)  8.538 ms 172.17.161.221 (172.17.161.221)  8.659 ms 172.17.161.97 (172.17.161.97)  9.296 ms

 4  172.17.160.149 (172.17.160.149)  12.485 ms 172.17.160.105 (172.17.160.105)  10.214 ms 172.17.160.85 (172.17.160.85)  11.934 ms

 5  172.17.4.30 (172.17.4.30)  23.648 ms  23.589 ms  23.530 ms

 6  etrunk37.milano50.mil.seabone.net (195.22.196.90)  24.756 ms  18.008 ms  18.164 ms

 7  72.14.196.141 (72.14.196.141)  34.144 ms 72.14.209.236 (72.14.209.236)  19.582 ms 72.14.203.52 (72.14.203.52)  25.146 ms

 8  108.170.245.65 (108.170.245.65)  20.600 ms  20.236 ms 108.170.245.81 (108.170.245.81)  31.219 ms

 9  216.239.42.27 (216.239.42.27)  21.303 ms 216.239.42.25 (216.239.42.25)  21.639 ms 216.239.42.27 (216.239.42.27)  22.431 ms

10  mil04s29-in-f206.1e100.net (216.58.205.206)  33.234 ms  24.451 ms  17.725 ms

root@raspberry:~# traceroute www.google.com

traceroute to www.google.com (216.58.198.4), 30 hops max, 60 byte packets

 1  192.168.147.1 (192.168.147.1)  0.726 ms  0.806 ms  0.946 ms

 2  * * *

 3  172.17.162.33 (172.17.162.33)  7.896 ms 172.17.161.221 (172.17.161.221)  8.792 ms 172.17.161.93 (172.17.161.93)  8.873 ms

 4  172.17.160.157 (172.17.160.157)  11.663 ms 172.17.160.149 (172.17.160.149)  11.572 ms 172.17.160.97 (172.17.160.97)  11.724 ms

 5  172.17.4.30 (172.17.4.30)  21.550 ms  21.469 ms  25.154 ms

 6  etrunk39.milano50.mil.seabone.net (93.186.128.252)  24.253 ms  18.970 ms  18.812 ms

 7  72.14.209.236 (72.14.209.236)  23.267 ms 72.14.196.141 (72.14.196.141)  29.479 ms 74.125.51.12 (74.125.51.12)  20.668 ms

 8  108.170.245.81 (108.170.245.81)  30.674 ms 108.170.245.65 (108.170.245.65)  21.054 ms 108.170.245.81 (108.170.245.81)  20.971 ms

 9  216.239.50.221 (216.239.50.221)  21.183 ms 216.239.50.241 (216.239.50.241)  22.260 ms  32.913 ms

10  mil04s03-in-f4.1e100.net (216.58.198.4)  22.945 ms  24.079 ms  17.383 ms

root@raspberry:~# traceroute photos.google.com

traceroute to photos.google.com (216.58.198.46), 30 hops max, 60 byte packets

 1  192.168.147.1 (192.168.147.1)  0.764 ms  0.773 ms  0.952 ms

 2  * * *

 3  172.17.162.76 (172.17.162.76)  7.885 ms 172.17.162.33 (172.17.162.33)  8.820 ms  8.826 ms

 4  172.17.160.153 (172.17.160.153)  12.080 ms 172.17.160.109 (172.17.160.109)  11.997 ms 172.17.160.161 (172.17.160.161)  11.910 ms

 5  172.17.4.28 (172.17.4.28)  24.280 ms  24.232 ms  24.153 ms

 6  etrunk11.milano50.mil.seabone.net (93.186.128.229)  24.131 ms etrunk36.milano1.mil.seabone.net (195.22.192.72)  19.473 ms etrunk11.milano50.mil.seabone.net (93.186.128.229)  18.904 ms

 7  74.125.146.168 (74.125.146.168)  19.538 ms 72.14.216.96 (72.14.216.96)  18.349 ms 72.14.195.206 (72.14.195.206)  20.719 ms

 8  108.170.245.81 (108.170.245.81)  30.095 ms 108.170.245.65 (108.170.245.65)  19.620 ms 108.170.245.81 (108.170.245.81)  20.229 ms

 9  216.239.48.229 (216.239.48.229)  31.611 ms  22.043 ms 216.239.48.231 (216.239.48.231)  21.718 ms

10  mil04s04-in-f14.1e100.net (216.58.198.46)  22.025 ms  22.061 ms  17.209 ms

Are you really sure that also Google DNS Servers are still in the Milano Google Edge PoP?

If yes, may there is a problem on Google DNS Servers in Milano?

Is it possible to check?

Let me knwow.

Thanks!

Fabio

[Alex Dupuy]

It may be a while before we can re-provision Google Public DNS caches in Milano, we'll update this thread when they are back.

Sorry we can't promise anything on this, or give you an ETA.

[Fabio Ancona]

Hi Alex.

I was almost certain that Google Public DNS in Italy is not more available for almost a year.

I hope that Google soon will go to re-provision Google Public DNS caches in Italy.

I'll stay tuned but I hope this will really made!

Thanks.

[Fabio Ancona]

Hi Alex.

Any news about a re-provision of Google Public DNS caches in Italy?

Thanks!