Can we get a closer 8.8.8.8 Server for Montreal?

David P

unread,

Dec 31, 2018, 1:32:31 PM12/31/18

to public-dns-discuss

I ask because there appears to be an extra 20ms of unnecessary additional latency as it seems to get forwarded to Toronto or New York -- and other google services (like youtube) are hosted directly in a Montreal datacenter.

Testing done from a VDSL Connection with 3.9 ms first-hop

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

1 10.11.16.193 (10.11.16.193) 4.536 ms 8.462 ms 13.568 ms

2 10.178.206.160 (10.178.206.160) 3.743 ms 3.778 ms 4.039 ms

3 10.178.206.161 (10.178.206.161) 3.605 ms 3.468 ms 4.189 ms

4 tcore3-montreal01_1-2-0-1.net.bell.ca (64.230.94.152) 8.759 ms tcore4-montreal01_1-2-0-1.net.bell.ca (64.230.94.154) 8.602 ms 10.321 ms

5 tcore3-montreal02_be30.net.bell.ca (64.230.33.95) 6.482 ms 7.096 ms tcore4-montreal02_be30.net.bell.ca (64.230.33.93) 5.726 ms

6 bx1-montrealgz_et-0-0-5.net.bell.ca (64.230.26.135) 4.041 ms bx1-montrealgz_et-0-0-1.net.bell.ca (64.230.26.133) 4.436 ms 3.941 ms

7 google_bx1-montrealgz.net.bell.ca (184.150.167.189) 4.454 ms 4.605 ms 4.223 ms

8 108.170.251.34 (108.170.251.34) 4.251 ms 108.170.251.50 (108.170.251.50) 4.671 ms 4.082 ms

9 74.125.37.198 (74.125.37.198) 13.226 ms 12.172 ms 108.170.235.210 (108.170.235.210) 15.471 ms

10 108.170.236.133 (108.170.236.133) 18.985 ms 108.177.3.51 (108.177.3.51) 20.488 ms 18.714 ms

11 216.239.48.2 (216.239.48.2) 26.970 ms 216.239.48.9 (216.239.48.9) 27.384 ms 216.239.48.31 (216.239.48.31) 26.097 ms

12 216.239.50.80 (216.239.50.80) 26.831 ms 72.14.236.168 (72.14.236.168) 25.417 ms 216.239.49.255 (216.239.49.255) 25.213 ms

13 * * *

14 * * *

15 * * *

16 * * *

17 * * *

18 * * *

19 * * *

20 * * *

21 * * *

22 * * *

23 google-public-dns-a.google.com (8.8.8.8) 25.305 ms 26.007 ms 24.230 ms

traceroute to google.ca (172.217.13.131), 30 hops max, 38 byte packets

1 10.11.16.193 (10.11.16.193) 4.206 ms 6.452 ms 10.309 ms

2 10.178.206.160 (10.178.206.160) 4.228 ms 3.947 ms 4.224 ms

3 10.178.206.161 (10.178.206.161) 4.204 ms 3.963 ms 4.226 ms

4 tcore3-montreal01_1-2-0-1.net.bell.ca (64.230.94.152) 7.472 ms tcore4-montreal01_1-2-0-1.net.bell.ca (64.230.94.154) 5.323 ms 6.609 ms

5 tcore3-montreal02_be30.net.bell.ca (64.230.33.95) 3.959 ms 6.475 ms 7.985 ms

6 bx1-montrealgz_et-0-0-1.net.bell.ca (64.230.26.133) 4.992 ms bx1-montrealgz_et-0-0-5.net.bell.ca (64.230.26.135) 4.048 ms 3.611 ms

7 google_bx1-montrealgz.net.bell.ca (184.150.167.189) 4.221 ms 4.093 ms 4.262 ms

8 108.170.251.49 (108.170.251.49) 4.236 ms 4.360 ms 4.927 ms

9 108.170.231.55 (108.170.231.55) 5.262 ms 5.028 ms 4.667 ms

10 yul02s05-in-f3.1e100.net (172.217.13.131) 4.253 ms 4.250 ms 3.934 ms

traceroute to youtube.com (172.217.13.142), 30 hops max, 38 byte packets

1 10.11.16.193 (10.11.16.193) 10.434 ms 12.423 ms 4.211 ms

2 10.178.206.160 (10.178.206.160) 3.701 ms 4.203 ms 3.970 ms

3 10.178.206.161 (10.178.206.161) 3.451 ms 3.966 ms 3.961 ms

4 tcore3-montreal01_1-2-0-1.net.bell.ca (64.230.94.152) 10.024 ms tcore4-montreal01_1-2-0-1.net.bell.ca (64.230.94.154) 4.092 ms 10.458 ms

5 tcore3-montreal02_be30.net.bell.ca (64.230.33.95) 8.217 ms 6.382 ms 7.754 ms

6 bx1-montrealgz_et-0-0-5.net.bell.ca (64.230.26.135) 4.696 ms 4.462 ms bx1-montrealgz_et-0-0-1.net.bell.ca (64.230.26.133) 4.655 ms

7 google_bx1-montrealgz.net.bell.ca (184.150.167.189) 4.130 ms 4.376 ms 3.964 ms

8 108.170.251.1 (108.170.251.1) 4.251 ms 3.954 ms 4.443 ms

9 108.170.231.55 (108.170.231.55) 5.276 ms 108.170.231.53 (108.170.231.53) 4.791 ms 108.170.231.55 (108.170.231.55) 5.525 ms

10 yul02s05-in-f14.1e100.net (172.217.13.142) 4.348 ms 3.915 ms 4.443 ms

the ISP's default DNS Server

1 10.11.16.193 (10.11.16.193) 9.736 ms 4.674 ms 3.963 ms

2 10.178.206.160 (10.178.206.160) 4.520 ms 3.995 ms 4.298 ms

3 10.178.206.161 (10.178.206.161) 4.003 ms 4.248 ms 4.909 ms

4 tcore4-montreal01_1-2-0-1.net.bell.ca (64.230.94.154) 4.746 ms tcore3-montreal01_1-2-0-1.net.bell.ca (64.230.94.152) 9.392 ms 8.869 ms

5 tcore4-montreal02_be30.net.bell.ca (64.230.33.93) 6.489 ms 6.613 ms tcore3-montreal02_be30.net.bell.ca (64.230.33.95) 7.534 ms

6 dis71-montreal02_7-2-0.net.bell.ca (64.230.90.159) 3.821 ms 3.912 ms dis71-montreal02_5-2-0.net.bell.ca (64.230.90.157) 4.285 ms

7 mtrlpq02dnsvp1.srvr.bell.ca (67.69.184.11) 4.052 ms 4.067 ms 4.220 ms

Competing DNS Server

1 10.11.16.193 (10.11.16.193) 10.239 ms 4.530 ms 13.319 ms

2 10.178.206.160 (10.178.206.160) 4.168 ms 4.095 ms 3.769 ms

3 10.178.206.161 (10.178.206.161) 3.849 ms 3.515 ms 3.954 ms

4 tcore4-montreal01_1-2-0-1.net.bell.ca (64.230.94.154) 14.495 ms 21.219 ms tcore3-montreal01_1-2-0-1.net.bell.ca (64.230.94.152) 13.485 ms

5 tcore4-newyorkaa_hundredgige0-3-0-0.net.bell.ca (64.230.79.144) 14.494 ms 64.230.78.138 (64.230.78.138) 13.312 ms 14.237 ms

6 bx7-newyork83_hundredgige0-7-0-0.net.bell.ca (64.230.79.91) 11.985 ms bx7-newyork83_hundredgige0-6-0-0.net.bell.ca (64.230.79.89) 14.281 ms bx7-newyork83_hundredgige0-7-0-0.net.bell.ca (64.230.79.91) 11.258 ms

7 198.32.118.206 (198.32.118.206) 20.311 ms 33.676 ms 13.395 ms

8 one.one.one.one (1.1.1.1) 13.750 ms 13.442 ms 13.705 ms

Alex Dupuy

unread,

Jan 2, 2019, 11:17:15 AM1/2/19

to public-dns-discuss

Thanks for the report. We're looking into why Google Public DNS is not enabled in the Montreal PoP and will see what we can do to bring this up.

Alex Dupuy

unread,

Feb 27, 2019, 5:53:53 PM2/27/19

to public-dns-discuss

We were able to restore Google Public DNS edge presence in Montreal today, users in Quebec should be seeing shorter latencies once again.

Reply all

Reply to author

Forward