Issue with google.com and www.google.com resolving to IPs in India?

[Colin Griffith]

Hi all,

I am hoping this is the right place for this, but if it is not I apologize.

DNS results for google.com and www.google.com (and youtube) seem to be resolving to IP addresses in India. 

Since our public IP ranges are routed in the US out of Minnesota, I am trying to figure out why we are getting IP's in India from google URLs. It is really slowing down googles use for our company. 

C:\Users\coling>nslookup www.google.com 216.239.34.10
Server:  ns2.google.com
Address:  216.239.34.10

Name:    www.google.com
Addresses:  2404:6800:4002:81a::2004
          142.250.193.36

C:\Users\coling>ping 142.250.193.36

Pinging 142.250.193.36 with 32 bytes of data:
Reply from 142.250.193.36: bytes=32 time=310ms TTL=111
Reply from 142.250.193.36: bytes=32 time=310ms TTL=111
Reply from 142.250.193.36: bytes=32 time=310ms TTL=111
Reply from 142.250.193.36: bytes=32 time=310ms TTL=111

C:\Users\coling>nslookup www.google.com 8.8.8.8

Server:  dns.google

Address:  8.8.8.8

Non-authoritative answer:

Name:    www.google.com

Addresses:  2607:f8b0:4009:814::2004

          142.250.190.132

C:\Users\coling>ping 142.250.190.132

Pinging 142.250.190.132 with 32 bytes of data:

Reply from 142.250.190.132: bytes=32 time=11ms TTL=116

Reply from 142.250.190.132: bytes=32 time=11ms TTL=116

Reply from 142.250.190.132: bytes=32 time=11ms TTL=116

Reply from 142.250.190.132: bytes=32 time=11ms TTL=116

Ping statistics for 142.250.190.132:

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

Approximate round trip times in milli-seconds:

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

The ns2.google.com is returning an IP that ping with 300 ms, where as 8.8.8.8 is returning a normally expected 11 ms.

Is there anything we can do about this? 

[Gardar Georg Nielsen]

Hi,

Did you find any resolution to this?  I am experiencing the same from Denmark.  Using standard DNS resolves google.com and youtube.com to servers in India with 330ms latency.  But resolving using 8.8.8.8 gives EU based servers with 12ms latency.  I tried to write to Google NOC but it seems they don't understand the issue.

/Georg.