I cannot connect to mirror.centos.org

hlang · Post by **hlang** » 2011/05/13 14:32:55

mirror.centos.org times out when it resolves to 41.215.241.82. It works when it resolves to 87.239.158.226.
It doesn't work from my local network or from a 3G mobile provider. The 2 use different upstream providers.

# nslookup mirror.centos.org
Non-authoritative answer:
Name: mirror.centos.org
Address: 41.215.241.82

A trace from my local network.
# traceroute mirror.centos.org
traceroute to mirror.centos.org (41.215.241.82), 30 hops max, 40 byte packets
1 reserved-for-networks.mweb.co.za (196.28.150.3) 0.384 ms 0.430 ms 0.542 ms
2 GigabitEthernet5-1.cpt-hscore-1.mweb.co.za (196.28.178.65) 0.569 ms 0.641 ms 0.724 ms
3 TenGigE0-2-0-0.11.cpt-up-1.mweb.co.za (196.28.178.97) 2.618 ms 2.593 ms 2.565 ms
4 pos0-0-3-0.lon-up-1.mweb.co.za (196.22.164.2) 199.981 ms 199.960 ms 199.953 ms
5 149.6.98.17 (149.6.98.17) 154.447 ms 154.280 ms 149.6.98.5 (149.6.98.5) 154.658 ms
6 te3-4.ccr02.lon02.atlas.cogentco.com (154.54.36.169) 199.610 ms te7-6.ccr01.lon01.atlas.cogentco.com (154.54.36.165) 154.169 ms te3-4.ccr02.lon02.atlas.cogentco.com (154.54.36.169) 199.653 ms
7 te7-8.ccr01.lon02.atlas.cogentco.com (130.117.1.218) 153.959 ms te7-2.mpd02.lon01.atlas.cogentco.com (130.117.0.97) 153.977 ms te7-8.ccr01.lon02.atlas.cogentco.com (130.117.1.218) 153.905 ms
8 te0-3-0-2.mpd22.jfk02.atlas.cogentco.com (130.117.51.161) 230.610 ms 230.499 ms te0-2-0-0.mpd21.jfk02.atlas.cogentco.com (154.54.24.133) 274.799 ms
9 te0-0-0-1.ccr21.jfk05.atlas.cogentco.com (154.54.7.14) 229.008 ms te0-1-0-0.ccr21.jfk05.atlas.cogentco.com (154.54.3.106) 228.703 ms te0-0-0-4.ccr21.jfk05.atlas.cogentco.com (154.54.6.50) 276.826 ms
10 gblx.jfk05.atlas.cogentco.com (154.54.11.138) 228.052 ms 227.848 ms te0-0-0-6.ccr21.jfk05.atlas.cogentco.com (154.54.5.210) 275.454 ms
11 gblx.jfk05.atlas.cogentco.com (154.54.11.138) 229.943 ms 64.214.151.82 (64.214.151.82) 296.559 ms 296.393 ms
12 172.19.1.26 (172.19.1.26) 296.766 ms 296.768 ms 296.316 ms
13 172.19.1.189 (172.19.1.189) 296.787 ms 172.19.1.21 (172.19.1.21) 304.240 ms 304.228 ms
14 172.19.1.21 (172.19.1.21) 304.506 ms 172.19.1.189 (172.19.1.189) 298.545 ms 172.20.3.146 (172.20.3.146) 302.474 ms
15 172.20.3.38 (172.20.3.38) 304.448 ms 172.20.3.146 (172.20.3.146) 305.281 ms 172.20.2.2 (172.20.2.2) 300.964 ms
16 172.20.2.2 (172.20.2.2) 306.141 ms 172.20.2.10 (172.20.2.10) 307.873 ms 172.17.2.2 (172.17.2.2) 299.913 ms
17 172.17.2.2 (172.17.2.2) 302.696 ms 302.677 ms 172.17.43.102 (172.17.43.102) 347.484 ms
18 172.17.43.102 (172.17.43.102) 349.885 ms 10.172.43.50 (10.172.43.50) 302.202 ms 302.234 ms
19 * * *
20 * * *

# nmap -p 80 41.215.241.82

Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2011-05-13 11:11 SAST
Note: Host seems down. If it is really up, but blocking our ping probes, try -P0
Nmap finished: 1 IP address (0 hosts up) scanned in 2.049 seconds

pschaff · Post by **pschaff** » 2011/05/13 20:09:36

[quote]
hlang wrote:
mirror.centos.org times out when it resolves to 41.215.241.82. ...[/quote]
I can confirm that IP address does not respond to ping, nor is it reachable by HTTP. The other address works, as do the other ones DNS gives me - different from home and work.