[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [public-dns-discuss] Re: Google DNS resolving Google.com to...London?!



Thanks for the reply.

Yes, that is a static IP and won't change anytime soon.

My system DNS resolver (which I push to all devices via the DHCP server I control for my network) is 8.8.8.8 and 8.8.4.4, so I am using Google Public DNS for all IP address resolutions. I did experiment with running my own local resolver directly querying the root servers, and the behavior was the same, so it seems to be with the Google authoritative name servers' geographic routing, perhaps?

I am using Chrome. However, behavior does replicate when I try Edge or Firefox as well as from the command line:

C:\Users\me>tracert www.google.com

Tracing route to www.google.com [216.58.206.36]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  router [192.168.56.1]
  2     1 ms    <1 ms    <1 ms  100.64.103.1
  3    <1 ms    <1 ms    <1 ms  38.131.218.241
  4     3 ms     2 ms     3 ms  38.65.114.217
  5     9 ms    16 ms     9 ms  v320.core1.mci3.he.net [184.105.41.97]
  6    13 ms    13 ms    13 ms  100ge9-2.core1.oma1.he.net [184.105.65.166]
  7    24 ms    24 ms    25 ms  206.126.235.14
  8    25 ms    25 ms    25 ms  108.170.243.165
  9    25 ms    25 ms    26 ms  209.85.249.136
 10    38 ms    38 ms    38 ms  209.85.252.47
 11   113 ms   113 ms   113 ms  209.85.254.250
 12   113 ms   113 ms   113 ms  216.239.57.206
 13   111 ms   111 ms   111 ms  108.170.246.225
 14   112 ms   112 ms   112 ms  216.239.41.207
 15   111 ms   111 ms   111 ms  lhr35s10-in-f4.1e100.net [216.58.206.36]

Trace complete.

C:\Users\me>nslookup www.google.com
Server:  router
Address:  192.168.56.1

Non-authoritative answer:
Name:    www.google.com
Addresses:  2a00:1450:4009:80c::2004
          216.58.206.36

C:\Users\me>nslookup www.google.com 8.8.8.8
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
Name:    www.google.com
Addresses:  2a00:1450:4009:80c::2004
          216.58.206.132

I can also replicate it on other machines on my network. I have rebooted those machines as well as my router multiple times.

If I watch Resource Monitor on Windows or my Mikrotik firewall's connections info when I load Gmail (or upload a file to Gmail) or YouTube, most of the time, I will see an LHR endpoint (i.e. right now, one of the top connections sorted by total B/sec in Resource Monitor is to lhr25s02-in-f101.1e100.net)

Occasionally, I'll see a DFW endpoint surface, but most of the traffic still goes to London:

C:\Users\me>tracert mail.google.com

Tracing route to googlemail.l.google.com [172.217.6.133]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  router [192.168.56.1]
  2    <1 ms    <1 ms    <1 ms  100.64.103.1
  3    <1 ms    <1 ms    <1 ms  38.131.218.241
  4     3 ms     2 ms     2 ms  38.65.114.217
  5     9 ms     9 ms     9 ms  v320.core1.mci3.he.net [184.105.41.97]
  6    26 ms    21 ms    21 ms  100ge12-1.core1.den1.he.net [184.105.64.49]
  7     *        *        *     Request timed out.
  8    31 ms    31 ms    31 ms  108.170.252.210
  9    31 ms    31 ms    31 ms  209.85.143.215
 10    28 ms    28 ms    28 ms  72.14.237.134
 11    28 ms    28 ms    28 ms  108.170.228.100
 12     *        *        *     Request timed out.
 13    28 ms    28 ms    28 ms  72.14.234.61
 14    27 ms    28 ms    27 ms  dfw25s16-in-f5.1e100.net [172.217.6.133]

Trace complete.

C:\Users\me>tracert ytimg.l.google.com

Tracing route to ytimg.l.google.com [216.58.213.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  router [192.168.56.1]
  2     2 ms    <1 ms    <1 ms  100.64.103.1
  3    <1 ms    <1 ms    <1 ms  38.131.218.241
  4     3 ms     2 ms     2 ms  38.65.114.217
  5     9 ms    16 ms     9 ms  v320.core1.mci3.he.net [184.105.41.97]
  6    21 ms    22 ms    24 ms  100ge12-1.core1.den1.he.net [184.105.64.49]
  7     *        *        *     Request timed out.
  8    31 ms    31 ms    31 ms  108.170.252.195
  9    32 ms    32 ms    32 ms  74.125.37.127
 10    32 ms    31 ms    32 ms  216.239.43.227
 11    33 ms    32 ms    32 ms  72.14.234.8
 12    48 ms    65 ms    45 ms  209.85.250.9
 13   119 ms   118 ms   147 ms  209.85.254.244
 14   118 ms   120 ms   118 ms  216.239.57.236
 15     *        *        *     Request timed out.
 16   119 ms   119 ms   119 ms  216.239.57.121
 17   118 ms   117 ms   118 ms  lhr25s02-in-f14.1e100.net [216.58.213.110]

Trace complete.

BTW, interesting reading at https://static.googleusercontent.com/media/research.google.com/en//pubs/archive/35590.pdf. Perhaps some of the issue is that my upstream ASNs are Cogent and HE (6939 and 174) , which both have widespread networks with several peering points with Google, including London, and so the way Google does geographic routing (by ASN latency, not client latency) might be contributing to the issue?

On Wed, Mar 7, 2018 at 2:32 PM, 'Alex Dupuy' via public-dns-discuss <public-dns-discuss AT googlegroups.com> wrote:
I just checked, and addresses in 38.131.218.0/24 should be getting directed to frontends in Texas, Colorado, or Chicago. It can take a while (days to weeks) for mapping to converge for new address ranges. Are you still at that IP address?

Local IP is 38.131.218.243, and my ASN is 55140. As we speak, I'm receiving YouTube content from lhr25s10-in-f165.1e100.net (216.58.198.165).

I have pushed through internal issues to fix mapping problems in the past, and they have always resolved themselves by the time I got anyone to look at it, I suspect this might be true here as well.

The only other thing I can think of is that your browser or other intermediate DNS resolver is still using or returning cached answers for these lookups.

Have you tried a browser or router restart?

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dns-discuss@googlegroups.com
To unsubscribe from this group, send email to
public-dns-discuss+unsubscribe AT googlegroups.com
For more options, visit this group at
http://groups.google.com/group/public-dns-discuss
For more information on Google Public DNS, please visit
http://developers.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to a topic in the Google Groups "public-dns-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/public-dns-discuss/25JxfnGqe40/unsubscribe.
To unsubscribe from this group and all its topics, send an email to public-dns-discuss+unsubscribe AT googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dns-discuss AT googlegroups.com
To unsubscribe from this group, send email to
public-dns-discuss+unsubscribe AT googlegroups.com
For more options, visit this group at
http://groups.google.com/group/public-dns-discuss
For more information on Google Public DNS, please visit
http://developers.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsubscribe AT googlegroups.com.
For more options, visit https://groups.google.com/d/optout.