* dig gcc.gnu.org succeeds (12.107.209.250), but traceroute gcc.gnu.org fails.
[not found] <E1BNVVs-000MK2-Sy@hercules.takinfo.hu>
@ 2004-05-11 18:56 ` llewelly
2004-05-11 18:58 ` Angela Marie Thomas
2004-05-11 19:59 ` Matthew Galgoci
0 siblings, 2 replies; 6+ messages in thread
From: llewelly @ 2004-05-11 18:56 UTC (permalink / raw)
Cc: overseers
I'm now able to do a dns lookup of gcc.gnu.org (it was failing for a
short period of time after the move):
; <<>> DiG 8.3 <<>> gcc.gnu.org
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63641
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4
;; QUERY SECTION:
;; gcc.gnu.org, type = A, class = IN
;; ANSWER SECTION:
gcc.gnu.org. 18h9m6s IN A 12.107.209.250
;; AUTHORITY SECTION:
gnu.org. 1h33m45s IN NS ns1.gnu.org.
gnu.org. 1h33m45s IN NS ns2.gnu.org.
gnu.org. 1h33m45s IN NS ns3.gnu.org.
gnu.org. 1h33m45s IN NS ns4.gnu.org.
;; ADDITIONAL SECTION:
ns1.gnu.org. 16h5m14s IN A 199.232.41.12
ns2.gnu.org. 16h5m14s IN A 213.228.62.2
ns3.gnu.org. 16h5m14s IN A 66.193.87.115
ns4.gnu.org. 16h5m14s IN A 193.201.200.170
But traceroute dies:
traceroute to gcc.gnu.org (12.107.209.250), 64 hops max, 40 byte
packets
1 192.168.1.25 (192.168.1.25) 1.118 ms 1.054 ms 1.034 ms
2 c6400-nrp2.xmission.com (166.70.4.75) 54.668 ms 55.107 ms
55.658 ms
3 c6509-core.xmission.com (166.70.4.76) 53.385 ms 53.144 ms
54.938 ms
4 gbr1-gi1-0.slc.xmission.com (166.70.4.8) 51.220 ms 52.421 ms
51.202 ms
5 12.127.106.97 (12.127.106.97) 53.625 ms 55.608 ms 53.101 ms
6 gbr3-p30.dvmco.ip.att.net (12.122.2.238) 64.483 ms 64.248 ms
63.770 ms
7 gbr4-p60.dvmco.ip.att.net (12.122.5.34) 62.244 ms 61.301 ms
64.595 ms
8 tbr1-p012702.cgcil.ip.att.net (12.122.10.121) 80.338 ms 81.445
ms 81.805 ms
9 tbr1-cl1.n54ny.ip.att.net (12.122.10.1) 99.121 ms 102.996 ms
100.798 ms
10 tbr2-cl2.n54ny.ip.att.net (12.122.9.130) 100.733 ms 101.833 ms
100.343 ms
11 tbr2-cl1.wswdc.ip.att.net (12.122.10.54) 110.665 ms 108.933 ms
108.957 ms
12 gar1-p370.rlgnc.ip.att.net (12.122.3.61) 111.978 ms 110.915 ms
112.531 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
and so on. (I let it go till it reached 64.)
I still get mail from the lists.
What's wrong here? Bad IP? Bad routing info? Sunspots? Am I the only one
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: dig gcc.gnu.org succeeds (12.107.209.250), but traceroute gcc.gnu.org fails.
2004-05-11 18:56 ` dig gcc.gnu.org succeeds (12.107.209.250), but traceroute gcc.gnu.org fails llewelly
@ 2004-05-11 18:58 ` Angela Marie Thomas
2004-05-11 20:19 ` llewelly
2004-05-11 19:59 ` Matthew Galgoci
1 sibling, 1 reply; 6+ messages in thread
From: Angela Marie Thomas @ 2004-05-11 18:58 UTC (permalink / raw)
To: llewelly; +Cc: overseers
The system moved physically. The firewall at the new location
blocks traceroute. You'll see this with the other hosts there
as well such as vger.kernel.org.
--Angela
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: dig gcc.gnu.org succeeds (12.107.209.250), but traceroute gcc.gnu.org fails.
2004-05-11 18:56 ` dig gcc.gnu.org succeeds (12.107.209.250), but traceroute gcc.gnu.org fails llewelly
2004-05-11 18:58 ` Angela Marie Thomas
@ 2004-05-11 19:59 ` Matthew Galgoci
1 sibling, 0 replies; 6+ messages in thread
From: Matthew Galgoci @ 2004-05-11 19:59 UTC (permalink / raw)
To: llewelly; +Cc: overseers
> But traceroute dies:
>
> traceroute to gcc.gnu.org (12.107.209.250), 64 hops max, 40 byte
> packets
> 1 192.168.1.25 (192.168.1.25) 1.118 ms 1.054 ms 1.034 ms
> 2 c6400-nrp2.xmission.com (166.70.4.75) 54.668 ms 55.107 ms
> 55.658 ms
> 3 c6509-core.xmission.com (166.70.4.76) 53.385 ms 53.144 ms
> 54.938 ms
> 4 gbr1-gi1-0.slc.xmission.com (166.70.4.8) 51.220 ms 52.421 ms
> 51.202 ms
> 5 12.127.106.97 (12.127.106.97) 53.625 ms 55.608 ms 53.101 ms
> 6 gbr3-p30.dvmco.ip.att.net (12.122.2.238) 64.483 ms 64.248 ms
> 63.770 ms
> 7 gbr4-p60.dvmco.ip.att.net (12.122.5.34) 62.244 ms 61.301 ms
> 64.595 ms
> 8 tbr1-p012702.cgcil.ip.att.net (12.122.10.121) 80.338 ms 81.445
> ms 81.805 ms
> 9 tbr1-cl1.n54ny.ip.att.net (12.122.10.1) 99.121 ms 102.996 ms
> 100.798 ms
> 10 tbr2-cl2.n54ny.ip.att.net (12.122.9.130) 100.733 ms 101.833 ms
> 100.343 ms
> 11 tbr2-cl1.wswdc.ip.att.net (12.122.10.54) 110.665 ms 108.933 ms
> 108.957 ms
> 12 gar1-p370.rlgnc.ip.att.net (12.122.3.61) 111.978 ms 110.915 ms
> 112.531 ms
> 13 * * *
> 14 * * *
> 15 * * *
> 16 * * *
> 17 * * *
> 18 * * *
Traceroute icmp is blocked at the last hop you see. This is fairly common
practice and does not indicate anything in regard to the reachability of
the host. When traceroute works, the only thing that it indicates it the
path across the internet at that _exact_ point in time that you had from
point A to point B. Traceroutes can also change right out from under you.
--
Matthew Galgoci
System Administrator and Sr. Manager of Ruminants
Red Hat, Inc
919.754.3700 x44155
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: dig gcc.gnu.org succeeds (12.107.209.250), but traceroute gcc.gnu.org fails.
2004-05-11 18:58 ` Angela Marie Thomas
@ 2004-05-11 20:19 ` llewelly
2004-05-12 2:02 ` Ian Lance Taylor
0 siblings, 1 reply; 6+ messages in thread
From: llewelly @ 2004-05-11 20:19 UTC (permalink / raw)
To: angela; +Cc: overseers
Angela Marie Thomas <angela@foam.wonderslug.com> writes:
> The system moved physically. The firewall at the new location
> blocks traceroute. You'll see this with the other hosts there
> as well such as vger.kernel.org.
But the only reason I tried traceroute is beacuse I couldn't get to
gcc.gnu.org any way at all; w3m, ftp, wget, all fail.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: dig gcc.gnu.org succeeds (12.107.209.250), but traceroute gcc.gnu.org fails.
2004-05-11 20:19 ` llewelly
@ 2004-05-12 2:02 ` Ian Lance Taylor
2004-05-12 8:39 ` llewelly
0 siblings, 1 reply; 6+ messages in thread
From: Ian Lance Taylor @ 2004-05-12 2:02 UTC (permalink / raw)
To: llewelly; +Cc: overseers
llewelly@xmission.com writes:
> Angela Marie Thomas <angela@foam.wonderslug.com> writes:
>
> > The system moved physically. The firewall at the new location
> > blocks traceroute. You'll see this with the other hosts there
> > as well such as vger.kernel.org.
>
> But the only reason I tried traceroute is beacuse I couldn't get to
> gcc.gnu.org any way at all; w3m, ftp, wget, all fail.
The system has not been up reliably. It has been crashing such that
it responds to ping but not to anything else. Matthew has been
investigating.
It is up at the moment.
Ian
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: dig gcc.gnu.org succeeds (12.107.209.250), but traceroute gcc.gnu.org fails.
2004-05-12 2:02 ` Ian Lance Taylor
@ 2004-05-12 8:39 ` llewelly
0 siblings, 0 replies; 6+ messages in thread
From: llewelly @ 2004-05-12 8:39 UTC (permalink / raw)
To: Ian Lance Taylor; +Cc: overseers
Ian Lance Taylor <ian@airs.com> writes:
> llewelly@xmission.com writes:
>
> > Angela Marie Thomas <angela@foam.wonderslug.com> writes:
> >
> > > The system moved physically. The firewall at the new location
> > > blocks traceroute. You'll see this with the other hosts there
> > > as well such as vger.kernel.org.
> >
> > But the only reason I tried traceroute is beacuse I couldn't get to
> > gcc.gnu.org any way at all; w3m, ftp, wget, all fail.
>
> The system has not been up reliably. It has been crashing such that
> it responds to ping but not to anything else. Matthew has been
> investigating.
>
> It is up at the moment.
ok. Thanks to all of you, for your hard work and your repsonses.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2004-05-12 3:09 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <E1BNVVs-000MK2-Sy@hercules.takinfo.hu>
2004-05-11 18:56 ` dig gcc.gnu.org succeeds (12.107.209.250), but traceroute gcc.gnu.org fails llewelly
2004-05-11 18:58 ` Angela Marie Thomas
2004-05-11 20:19 ` llewelly
2004-05-12 2:02 ` Ian Lance Taylor
2004-05-12 8:39 ` llewelly
2004-05-11 19:59 ` Matthew Galgoci
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).