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

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



Alex, I really need your help. This is driving me nuts.

Today I'm connecting to lhr25s14-in-f5.1e100.net and lhr35s06-in-f5.1e100.net. Pretty soon I will probably have a complete list of every server in your London datacenter, ha.

The problem is the long transatlantic link and high latency makes using Gmail difficult. The interface is laggy, uploading attachments is often tediously slow, and sometimes it breaks completely (like right now, a long message I tried to send has been stuck stuck on "Sending..." in the Gmail web interface for several minutes). I've already mentioned the issues with YouTube.

There is a problem here that should not exist and I need your help resolving it.

On Saturday, February 17, 2018 at 10:52:57 PM UTC-5, Chris Luth wrote:
This is still happening constantly and it's driving me nuts. Gmail gets annoyingly unresponsive sometimes. YouTube can barely stream to me in SD.

Today's server is lhr35s05-in-f69.1e100.net.

I know it's not strictly on-topic here (though I do use Google Public DNS), but since there appears to be no other way to report this issue to Google, I'm reliant on Alex or someone else at Google monitoring this list to pass my issue along to someone in the right department.

Again, as noted below, my local IP is 38.131.218.243 on ASN 55140 and every site I check correctly geolocates that to Southwest Missouri, so there is no reason that I should be getting served from London, yet London-based Google servers are almost always at the top of my network activity lists.

On Saturday, January 27, 2018 at 5:08:02 PM UTC-5, Chris Luth wrote:
OK, so it's not a Google DNS issue. I set up Unbound as a local resolver and I'm getting the same thing. It's especially frustrating today as YouTube is now being served to me out of the London endpoint, meaning that I'm lucky to get smooth playback at 360p resolution. HD is impossible without buffering.

So it's obviously an issue with Google's internal CDN set-up/nameservers/whatever, not Google Public DNS (which makes sense, since I'm getting the same results from Google Public DNS, which passes my EDNS client subnet, as if I just run a resolver locally) and so off-topic for this mailing list. Alex or anyone else here, do you have contact info for someone in the right department at Google, or can someone here pass this along to the right place?

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).

Thanks.

On Friday, January 12, 2018 at 5:05:22 PM UTC-5, Chris Luth wrote:
Just wanted to bump this and say there's been no change over the past week since I posted -- the exact endpoint fluctuates (today, it's 216.58.198.100), but it still resolves to some permutation of *lhr*.1e100.net with pings around 110ms.

On Thursday, January 4, 2018 at 12:52:00 PM UTC-5, Chris Luth wrote:
Thanks for the reply.

It's Windows, so I'm using nslookup, but with and without 8.8.8.8, I get 

edns0-client-subnet 38.131.218.243/32

and

"{'ecs_payload':{'family':'1','optcode':'0x08','cc':'US','ip':'38.131.218.0','mask':'24','scope':'0'},'ecs':'True','ts':'1515088007.77','recursive':{'cc':'US','srcip':'74.125.113.133','sport':'56313'}}"

Full results below. I'll not bother to obfuscate my ISP's CGNed public IP, as it's kinda pointless anyway. ;)

> set type=txt
Server:  router
Address:  192.168.56.1

Non-authoritative answer:

        "74.125.113.145"

        "edns0-client-subnet 38.131.218.243/32"
Server:  [8.8.8.8]
Address:  8.8.8.8

Non-authoritative answer:

        "74.125.183.72"

        "edns0-client-subnet 38.131.218.243/32"
Server:  router
Address:  192.168.56.1

Non-authoritative answer:
edns-client-sub.net     text =

        "{'ecs_payload':{'family':'1','optcode':'0x08','cc':'US','ip':'38.131.218.0','mask':'24','scope':'0'},'ecs':'True','ts':'1515087998.46','recursive':{'cc':'US','srcip':'173.194.94.129','sport':'50825'}}"
Server:  [8.8.8.8]
Address:  8.8.8.8

Non-authoritative answer:
edns-client-sub.net     text =

        "{'ecs_payload':{'family':'1','optcode':'0x08','cc':'US','ip':'38.131.218.0','mask':'24','scope':'0'},'ecs':'True','ts':'1515088007.77','recursive':{'cc':'US','srcip':'74.125.113.133','sport':'56313'}}"


On Thursday, January 4, 2018 at 1:48:20 AM UTC-5, Alex Dupuy wrote:
What do you see when you make the following dig queries?

dig TXT o-o.myaddr.test.l.google.com. # (with @8.8.8.8 and without, using default resolver configuration)
dig TXT edns-client-sub.net. # (with and without @8.8.8.8)

These would reveal what EDNS Client Subnet (ECS) data is being sent to authorities. Perhaps somehow your DNS requests are going out with ECS value of 100.64.103.1 (which is a Carrier Grade NAT address, no more meaningful than 192.168.56.1.

--
--
========================================================
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.