Request timed out

5 views
Skip to first unread message

Zero3K

unread,
Dec 5, 2009, 10:56:47 AM12/5/09
to public-dns-discuss
I get that message when pinging 8.8.4.4 (My ISP is BellSouth.net and I
live in Louisville, KY). Here's a traceroute of it:

Tracing route to google-public-dns-b.google.com [8.8.4.4]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms * 8 ms 68.152.237.169
3 9 ms 8 ms 8 ms 68.152.237.141
4 15 ms 14 ms 15 ms ixc01sdf-ge-1-0-7.bellsouth.net
[205.152.156.29]
5 14 ms 15 ms 15 ms ixc00owb-pos-1-0-0.bellsouth.net
[205.152.229.61]
6 15 ms 15 ms 14 ms ixc01owb-ge-0-0-0.bellsouth.net
[205.152.229.83]
7 44 ms 15 ms 15 ms axr00bna-so-2-0-0.bellsouth.net
[65.83.239.24]
8 14 ms 15 ms 15 ms 65.83.238.82
9 14 ms 14 ms 14 ms 65.83.238.157
10 34 ms 34 ms 35 ms cr2.nsvtn.ip.att.net [12.123.129.94]
11 35 ms 35 ms 33 ms cr2.attga.ip.att.net [12.122.1.241]
12 32 ms 33 ms 32 ms ggr3.dlstx.ip.att.net [12.122.139.21]
13 34 ms * * 192.205.35.222
14 34 ms 34 ms 34 ms ae-73-70.ebr3.Dallas1.Level3.net
[4.69.145.116]
15 * 42 ms * ae-7.ebr3.Atlanta2.Level3.net
[4.69.134.22]
16 56 ms 67 ms 55 ms ae-2.ebr1.Washington1.Level3.net
[4.69.132.86]
17 54 ms 54 ms 55 ms ae-91-91.csw4.Washington1.Level3.net
[4.69.134.142]
18 53 ms 55 ms 54 ms ae-4-99.edge1.Washington1.Level3.net
[4.68.17.208]
19 87 ms 68 ms 168 ms GOOGLE-
INC.edge1.Washington1.Level3.net [4.79.228.38]
20 83 ms 75 ms 73 ms 209.85.240.136
21 55 ms 56 ms 56 ms 64.233.175.109
22 154 ms * 55 ms 72.14.232.21
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Zero3K

unread,
Dec 5, 2009, 7:55:07 PM12/5/09
to public-dns-discuss
Umm, no one cares about my problem? I hope that's not the case...

Jeremy Chen (陳康本)

unread,
Dec 7, 2009, 8:37:47 AM12/7/09
to public-dn...@googlegroups.com
Hi Zero3K,

We did not ignore your problem.  Our engineering team has some thoughts about this kind of behavior with traceroute but is not completely sure what the problem is.  We are not sure if it is just a bug in traceroute, and we are still investigating it before making any conclusion.  In the meantime, we would like to know about your DNS queries against 8.8.4.4.  Are you able to successfully use Google Public DNS to resolve DNS queries?  If you have problems, please share with us the results of dig or nslookup (to the degree that you feel comfortable).  Thanks!

Jeremy

--
========================================================
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-dn...@googlegroups.com
To unsubscribe from this group, send email to
public-dns-disc...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================



--
Jeremy Chen, Google New York Software Engineer
Reply all
Reply to author
Forward
0 new messages