google.com.tr problem

7 views
Skip to first unread message

cnrdzn

unread,
Jan 8, 2010, 4:21:40 AM1/8/10
to public-dns-discuss
google.com.tr very slow.. sometimes doesn't open

C:\Documents and Settings\CNR>ping www.google.co.uk

Pinging www.l.google.com [74.125.87.103] with 32 bytes of data:

Reply from 74.125.87.103: bytes=32 time=56ms TTL=53
Reply from 74.125.87.103: bytes=32 time=56ms TTL=54
Reply from 74.125.87.103: bytes=32 time=56ms TTL=54
Reply from 74.125.87.103: bytes=32 time=56ms TTL=54

Ping statistics for 74.125.87.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 56ms, Average = 56ms

C:\Documents and Settings\CNR>ping www.google.com.tr

Pinging www.l.google.com [74.125.87.147] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 74.125.87.147:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


C:\Documents and Settings\CNR>ping www.google.com.tw

Pinging www.l.google.com [74.125.87.103] with 32 bytes of data:

Reply from 74.125.87.103: bytes=32 time=56ms TTL=53
Reply from 74.125.87.103: bytes=32 time=57ms TTL=53
Reply from 74.125.87.103: bytes=32 time=58ms TTL=54
Reply from 74.125.87.103: bytes=32 time=56ms TTL=54

Ping statistics for 74.125.87.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 58ms, Average = 56ms


__________________________________________


C:\Documents and Settings\CNR>nslookup www.google.com.tr 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8

Non-authoritative answer:
Name: www.l.google.com
Addresses: 74.125.87.147, 74.125.87.99, 74.125.87.104, 74.125.87.105
74.125.87.103
Aliases: www.google.com.tr, www.google.com


C:\Documents and Settings\CNR>nslookup www.google.com.tr 8.8.4.4
Server: google-public-dns-b.google.com
Address: 8.8.4.4

Non-authoritative answer:
Name: www.l.google.com
Addresses: 74.125.87.147, 74.125.87.99, 74.125.87.104, 74.125.87.105
74.125.87.103
Aliases: www.google.com.tr, www.google.com


Paul S. R. Chisholm

unread,
Jan 8, 2010, 7:47:39 AM1/8/10
to public-dn...@googlegroups.com
Sorry to hear that. Are you in Turkey when you're having these problems?

The three hosts you pinged (www.google.co.uk, www.google.com.tr,
www.google.com.tw), as well as www.google.com, all have "canonical
names" (CNAMEs) of www.l.google.com. That's why you see that "Pinging
www.l.google.com" message for all three hosts. All three hosts return
the same family of IP addresses; your computer happened to pick one
for www.google.co.uk and www.google.com.tw (which worked), and a
different one for www.google.com.tr (which didn't work). The
time-to-live for the A records (IPv4 addresses) is about five minutes;
if you wait a few minutes, your computer might pick a different
address for www.google.com.tr. Does waiting help?

You can resolve www.google.com.tr to an IP address, so it's not
specifically a Google Public DNS problem. Whether it's a problem with
your ISP or a problem with Google, the next question is: What does:
tracert www.google.com.tr
report?

Hope this helps. --PSRC

Paul S. R. Chisholm

unread,
Jan 8, 2010, 7:55:55 AM1/8/10
to public-dn...@googlegroups.com
Or (better) what are the results of:
tracert 74.125.87.147
(for the address that doesn't work) and
tracert 74.125.87.103
(for the address that does work).

Hope this helps even more. --PSRC

Reply all
Reply to author
Forward
0 new messages