RE: [SLE] still can't get www.suse.com
21 www.SuSE.com (202.58.118.8) 226 ms 418 ms 262 ms>
can you resolve the hostname www.suse.com anyway? I have the same problem as he does. I just did a lookup and got
Martin Mielke wrote: the same number you did
are you able to actually go to www.suse.com at this moment?
Damon Register
The answer is "yes" if you mean me with your question. I can actually access www.suse.com and browse the whole site. Let's take a closer look and find out where is the problem. I'm now located in Madrid (Spain) and this is the route to www.suse.com : [...] 6 pos1-0.cr1.NYC3.gblx.net (208.48.24.237) 170 ms 150 ms 155 ms 7 pos4-0-155M.cr2.NYC3.gblx.net (208.49.138.29) 155 ms 156 ms 181 ms 8 * pos6-0-2488M.cr2.IAD3.gblx.net (208.51.66.166) 170 ms 154 ms 9 so1-0-0-622M.br1.IAD3.gblx.net (208.178.254.109) 155 ms 157 ms * 10 sl-gw1-rly-1-0-0-155M.sprintlink.net (144.232.184.1) 491 ms 196 ms 218 ms 11 sl-bb21-rly-3-2.sprintlink.net (144.232.14.37) 192 ms 180 ms 180 ms 12 sl-bb22-rly-15-0.sprintlink.net (144.232.25.26) 292 ms 169 ms * 13 sl-bb20-sj-9-0.sprintlink.net (144.232.9.218) 227 ms 238 ms 282 ms 14 sl-bb21-sj-15-0.sprintlink.net (144.232.3.158) 270 ms 266 ms 257 ms 15 sl-bb20-stk-13-0.sprintlink.net (144.232.9.166) 261 ms 281 ms 227 ms 16 * sl-gw28-stk-8-0.sprintlink.net (144.232.4.110) 289 ms 228 ms 17 sl-southb-25-0.sprintlink.net (144.232.229.10) 299 ms 240 ms 260 ms 18 * ded1-fa12-0-0.snfc21.pbi.net (209.232.130.69) 230 ms 230 ms 19 63.206.215.82 (63.206.215.82) 250 ms 240 ms 256 ms 20 10.87.100.1 (10.87.100.1) 244 ms 230 ms 240 ms 21 * www.SuSE.com (202.58.118.8) 230 ms 239 ms Cliff Sarginson (The Netherlands) said he can't reach suse.com neither, so maybe it's not a SuSE's issue but a provider's issue. Damon, I assume you are in the States (at least lmco.com does, according to RIPE). I still can access/browse www.suse.com using ns1.lmco.com to resolve names so I guess it's not a corrupted DNS issue. Let's see what's next... Martin
Let's take a closer look and find out where is the problem. I'm now located in Madrid (Spain) and this is the route to www.suse.com :
My route: Node Time (msec) Address Name 001 0 192.168.7.33 tnorala 002 35 194.236.7.1 ? 003 18 62.20.227.201 ? 004 20 213.64.49.18 ? 005 27 213.64.49.45 apv-b1-pos6-0.telia.net 006 30 194.17.1.157 sto-b2-atm2-0-1.telia.net 007 129 194.17.0.250 ny-b2-pos1-3.telia.net 008 128 209.95.128.166 ny-i8-atm2-0.telia.net 009 129 144.232.171.109 sl-gw5-nyc-6-0-0.sprintlink.net 010 144 144.232.13.225 sl-bb20-nyc-0-0.sprintlink.net 011 131 144.232.18.37 sl-bb20-pen-9-0.sprintlink.net 012 205 144.232.18.46 sl-bb20-stk-12-0.sprintlink.net 013 207 144.232.4.110 sl-gw28-stk-8-0.sprintlink.net 014 209 144.232.229.10 sl-southb-25-0.sprintlink.net 015 205 209.232.130.4 ded1-fa11-1-0.snfc21.pbi.net 016 210 63.206.215.82 ? 017 207 10.87.100.1 ? 018 208 202.58.118.8 www.suse.com So, we definately have a working route to suse.com over sprintlink.net
Cliff Sarginson (The Netherlands) said he can't reach suse.com neither, so maybe it's not a SuSE's issue but a provider's issue.
Damon, I assume you are in the States (at least lmco.com does, according to RIPE). I still can access/browse www.suse.com using ns1.lmco.com to resolve names so I guess it's not a corrupted DNS issue.
Let's see what's next...
It can't really be anything else than a misconfigured route. We have seen in previous postings that alternet has a nice routerloop going on. ´ So please guys and gals, don't flame SuSe, it's probably not their fault that someone upstream from them has screwed up the routing.
participants (2)
-
Martin Mielke -
Mikke Mattsson