8.8.8.8 timing out the last two days

[Sniper Fox]

> server 8.8.8.8
DNS request timed out.
timeout was 2 seconds.
Default Server: [8.8.8.8]
Address: 8.8.8.8

> server 8.8.4.4
Default Server: google-public-dns-b.google.com
Address: 8.8.4.4

[Yunhong Gu]

Hello

Can you post the traceroute result?

> traceroute 8.8.8.8

Thanks,

Yunhong

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

[Tom C]

Hello
Do you seem to have a problem with querying from your infrastructure
coming from NTT & Qwest. Reply from your end seem to be intermittent:

$ while true; do echo `date` - `dig +short www.google.com @8.8.8.8` ;
sleep 3 ; done
Fri Jan 6 23:55:22 UTC 2012 - www.l.google.com. 74.125.224.211
74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
Fri Jan 6 23:55:25 UTC 2012 - www.l.google.com. 74.125.224.211
74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
Fri Jan 6 23:55:28 UTC 2012 - ;; connection timed out; no servers
could be reached
Fri Jan 6 23:55:46 UTC 2012 - ;; connection timed out; no servers
could be reached
Fri Jan 6 23:56:04 UTC 2012 - ;; connection timed out; no servers
could be reached
Fri Jan 6 23:56:22 UTC 2012 - www.l.google.com. 74.125.224.211
74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
Fri Jan 6 23:56:25 UTC 2012 - www.l.google.com. 74.125.224.211
74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
Fri Jan 6 23:56:28 UTC 2012 - www.l.google.com. 74.125.224.211
74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
Fri Jan 6 23:56:31 UTC 2012 - www.l.google.com. 74.125.224.211
74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
Fri Jan 6 23:56:34 UTC 2012 - ;; connection timed out; no servers
could be reached
Fri Jan 6 23:56:52 UTC 2012 - ;; connection timed out; no servers
could be reached
Fri Jan 6 23:57:10 UTC 2012 - ;; connection timed out; no servers
could be reached
Fri Jan 6 23:57:28 UTC 2012 - www.l.google.com. 74.125.224.211
74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
Fri Jan 6 23:57:31 UTC 2012 - www.l.google.com. 74.125.224.211
74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
Fri Jan 6 23:57:34 UTC 2012 - www.l.google.com. 74.125.224.211
74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
Fri Jan 6 23:57:37 UTC 2012 - www.l.google.com. 74.125.224.211
74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
Fri Jan 6 23:57:40 UTC 2012 - www.l.google.com. 74.125.224.211
74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
Fri Jan 6 23:57:43 UTC 2012 - ;; connection timed out; no servers
could be reached
Fri Jan 6 23:58:01 UTC 2012 - www.l.google.com. 74.125.224.211
74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
Fri Jan 6 23:58:04 UTC 2012 - ;; connection timed out; no servers
could be reached

Is there something wrong on your end or on a peer?

From my other sites though the connection's fast.

[Paul S. R. Chisholm]

Thanks for the report, Tom. Nothing wrong on Google's end; possibly
something wrong with a peer, but hard for us to tell. The support
staff at your ISP(s) (NTT and/or Qwest?) are probably the best folks
to help you: It's their job to get you connected to hosts on the
Internet, and they know their peering arrangements better than we do.

As described at:
http://code.google.com/speed/public-dns/docs/using.html#troubleshooting
you should verify that your client can communicate with the Google
Public DNS servers:
Windows:
tracert -d 8.8.8.8
Mac OS X:
/usr/sbin/traceroute -n -w 2 -q 2 -m 30 8.8.8.8
Linux:
sudo traceroute -n -w 2 -q 2 -m 30 8.8.8.8

From any platform, you can also try:
ping -c 8.8.8.8
which will give you a sense of how reliably you can reach the Google
Public DNS servers.

If your ISP(s) can't or won't help, please post the traceroute and
ping output here, along with the response you got from your ISP(s).

Hope things clear up quickly, one way or another. --PSRC

[Elie Ciment]

We are having the same issues from time to time.

Here's the tracert from just now:

1 * * * Request timed out.
2 * * * Request timed out.
3 9 ms 18 ms 9 ms xe-0-1-0-0-
sur01.woodlawn.md.bad.comcast.net [68
.85.112.125]
4 10 ms 13 ms 14 ms xe-5-0-3-0-
ar04.whitemarsh.md.bad.comcast.net [6
8.85.115.189]
5 15 ms 18 ms 15 ms pos-3-6-0-0-
cr01.newyork.ny.ibone.comcast.net [6
8.86.93.89]
6 15 ms 15 ms 21 ms pos-0-0-0-0-
pe01.111eighthave.ny.ibone.comcast.n
et [68.86.87.122]
7 16 ms 13 ms 16 ms 66.208.228.206
8 21 ms 16 ms 20 ms 209.85.255.68
9 40 ms 23 ms 17 ms 209.85.251.35
10 107 ms 24 ms 22 ms 209.85.249.11
11 24 ms 21 ms 24 ms 64.233.175.109
12 29 ms 34 ms 34 ms 72.14.232.21
13 22 ms 20 ms 23 ms google-public-dns-a.google.com
[8.8.8.8]

Trace complete.

> > $ while true; do echo `date` - `dig +shortwww....@8.8.8.8` ;
> > sleep 3 ; done
> > Fri Jan 6 23:55:22 UTC 2012 -www.l.google.com. 74.125.224.211
> > 74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
> > Fri Jan 6 23:55:25 UTC 2012 -www.l.google.com. 74.125.224.211

> > 74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
> > Fri Jan 6 23:55:28 UTC 2012 - ;; connection timed out; no servers
> > could be reached
> > Fri Jan 6 23:55:46 UTC 2012 - ;; connection timed out; no servers
> > could be reached
> > Fri Jan 6 23:56:04 UTC 2012 - ;; connection timed out; no servers
> > could be reached

> > Fri Jan 6 23:56:22 UTC 2012 -www.l.google.com. 74.125.224.211
> > 74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
> > Fri Jan 6 23:56:25 UTC 2012 -www.l.google.com. 74.125.224.211
> > 74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
> > Fri Jan 6 23:56:28 UTC 2012 -www.l.google.com. 74.125.224.211
> > 74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
> > Fri Jan 6 23:56:31 UTC 2012 -www.l.google.com. 74.125.224.211

> > 74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
> > Fri Jan 6 23:56:34 UTC 2012 - ;; connection timed out; no servers
> > could be reached
> > Fri Jan 6 23:56:52 UTC 2012 - ;; connection timed out; no servers
> > could be reached
> > Fri Jan 6 23:57:10 UTC 2012 - ;; connection timed out; no servers
> > could be reached

> > Fri Jan 6 23:57:28 UTC 2012 -www.l.google.com. 74.125.224.211
> > 74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
> > Fri Jan 6 23:57:31 UTC 2012 -www.l.google.com. 74.125.224.211
> > 74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
> > Fri Jan 6 23:57:34 UTC 2012 -www.l.google.com. 74.125.224.211
> > 74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
> > Fri Jan 6 23:57:37 UTC 2012 -www.l.google.com. 74.125.224.211
> > 74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
> > Fri Jan 6 23:57:40 UTC 2012 -www.l.google.com. 74.125.224.211

> > 74.125.224.209 74.125.224.210 74.125.224.212 74.125.224.208
> > Fri Jan 6 23:57:43 UTC 2012 - ;; connection timed out; no servers
> > could be reached

> > Fri Jan 6 23:58:01 UTC 2012 -www.l.google.com. 74.125.224.211

[MinJae Hwang]

Elle, Thanks for the report. I agree with Paul. tracert failure
possibly indicates that something's wrong on ISP. Could you follow
Paul's suggestion that contact your ISP and report here if they can't
or won't help.

> > > $ while true; do echo `date` - `dig +shortwww.google....@8.8.8.8` ;

[Shen Wan]

Could you post the tracert result to 8.8.8.8? Thanks!

On Thursday, April 18, 2013 7:57:30 AM UTC-4, ravi...@rustomjee.com wrote:

We are also facing same issue.

We have checked the DNS IP (8.8.8.8) through the Sify and Reliance data modem, form both links receiving RTO's at a time.

Regards,

Ravi G.Thota

[Shen Wan]

So you can actually reach 8.8.8.8, right? Please open an issue at https://code.google.com/a/google.com/p/public-dns/issues/list and tell us in detail what is working and what is not. Thanks!

On Friday, April 19, 2013 12:25:08 AM UTC-4, ravi...@rustomjee.com wrote:

Hi, 

Kindly go through below mentioned Google public DNS.

From Sify Network.

C:\>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]

over a maximum of 30 hops:

  1     4 ms     3 ms     3 ms  dc-router.rustomjee.com [10.0.0.100]

  2    13 ms    89 ms    11 ms  segment-119-226.sify.net [119.226.128.245]

  3    13 ms    12 ms   100 ms  segment-119-227.sify.net [119.227.108.10]

  4    31 ms    12 ms    11 ms  72.14.210.200

  5    15 ms    11 ms    12 ms  72.14.232.202

  6   109 ms    43 ms   122 ms  66.249.94.39

  7   144 ms    73 ms    74 ms  72.14.239.22

  8    80 ms    80 ms    82 ms  209.85.242.243

  9    91 ms    90 ms     *     209.85.250.237

 10     *        *        *     Request timed out.

 11    24 ms    26 ms    29 ms  72.14.232.99

 12     *        *        *     Request timed out.

 13    24 ms    24 ms     *     72.14.232.99

 14    13 ms    13 ms    11 ms  google-public-dns-a.google.com [8.8.8.8]

Trace complete.

From Reliance Network 

C:\>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]

over a maximum of 30 hops:

  1    62 ms    78 ms    72 ms  220.224.141.129

  2    64 ms    66 ms    77 ms  115.255.239.97

  3    89 ms   124 ms    64 ms  124.124.251.241

  4     *       64 ms    67 ms  115.255.239.49

  5    80 ms    67 ms    82 ms  72.14.212.118

  6    66 ms    84 ms    85 ms  209.85.241.52

  7   105 ms    98 ms   142 ms  209.85.251.95

  8   143 ms   144 ms   173 ms  66.249.94.74

  9   134 ms   153 ms   130 ms  209.85.242.243

 10   142 ms   152 ms   143 ms  209.85.241.173

 11     *        *        *     Request timed out.

 12   198 ms   128 ms   146 ms  google-public-dns-a.google.com [8.8.8.8]

Trace complete.

Regards,

Ravi G.Thota

On Friday, January 6, 2012 8:11:47 PM UTC+5:30, Sniper Fox wrote:

[mo_ah...@hotmail.co.uk]

I think if it goes beyond 13 hops its unreliable or will fail. Maybe its a time-out for reaching the destination. You could possibly try changing the router IP DNS to 8,8,8,8 or use it as the secondary DNS if that is an option and makes sense to your organization. Obviously you can't choose the IP address and the DNS that your ISP provides but on some routers you can force use of DNS on the WAN side.

I hope this helps.

Mo

[กฤษฎา สวัสเอื้อ]

555

ในวันที่ วันศุกร์ที่ 19 มกราคม ค.ศ. 2018 เวลา 20 นาฬิกา 39 นาที 39 วินาที UTC+7 mo_ah...@hotmail.co.uk เขียนว่า: