| |
It works fine from Sweden;)
I included some info to you, maybe you can find it usefull?
8 164 ms 144 ms 176 ms bar1-serial6-1-1-0.NewYorknyr.cw.net
[206.24.200.157]
9 168 ms 136 ms 170 ms acr2-loopback.NewYorknyr.cw.net
[206.24.194.62]
10 175 ms 178 ms 185 ms corerouter2.WestOrange.cw.net [204.70.9.139]
11 238 ms 218 ms 194 ms hs-core7-loopback.WestOrange.cw.net
[166.49.67.97]
12 243 ms 225 ms 193 ms savvis-communications-hou.WestOrange.cw.net
[166.49.67.106]
13 273 ms 266 ms 162 ms pairnet-1.uspitb.savvis.net [209.83.160.130]
14 * * * Request timed out.
15 173 ms 161 ms 168 ms my.lugnet.com [209.197.108.235]
Trace complete.
/Joakim
"Todd Lehman" <lehman@javanet.com> wrote in message
news:G1FJn3.G5u@lugnet.com...
> Someone in the Washington, D.C. area is reporting having trouble accessing
> things on img.lugnet.com and news.lugnet.com...possibly some kind of DNS
> confusion somewhere. (img.lugnet.com is where images from the sets • database
> are served.)
>
> Anyone else noticing any troubles? Can anyone -not- access any of the
> following?--
>
> http://my.lugnet.com/
> http://img.lugnet.com/
> http://news.lugnet.com/
> http://guide.lugnet.com/
> http://market.lugnet.com/
> http://members.lugnet.com/
> http://gallery.lugnet.com/
>
> DNS on these has been up for...hmm...about a month...so it should really • be
> propagated everywhere it needs to be by now. The weird thing is, the • people
> who are having trouble with this today weren't having trouble with it at • all
> earlier; it just sorta started not working for them all of a sudden.
>
> According to server HTTP logs, things seem to be going out without a • hitch.
> Of course, the logs can't possibly show connection attempts that didn't • even
> make it to the server.
>
> --Todd
|
|
Message is in Reply To:
8 Messages in This Thread:
  
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
