Re: Can you see this site
by Chip Wiegand <chip(at)wiegand.org>
|
Date: |
Sun, 3 Mar 2002 21:58:54 +0000 |
To: |
Susan Vollmer <susanvollmer(at)yahoo.com> |
Cc: |
hwg-techniques(at)hwg.org |
References: |
yahoo |
|
todo: View
Thread,
Original
|
|
On Sun, 3 Mar 2002 18:45:28 -0800 (PST)
Susan Vollmer <susanvollmer(at)yahoo.com> wrote:
> Can someone let me know if you can bring up this site
> or not on your computer?
>
> http://www.nostalgicgarden.com
>
> I keep receiving this error message, and I don't know
> what it means:
>
> "Unable to Fetch Domain
> The requested URL cannot be loaded."
>
> Also, I'm not able to FTP into the site anymore.
>
> Any ideas would be most appreciated.
>
> Thanks in advance,
> Susan
I got the same error message you did. I did a traceroute to the site and
came up with this:
bash-2.05a$ traceroute www.nostalgicgarden.com
traceroute to www.nostalgicgarden.com (207.150.192.12), 64 hops max, 40
byte packets 1 192.168.1.10 (192.168.1.10) 0.521 ms 0.498 ms 0.430
ms 2 pia152-1.pioneernet.net (66.114.152.1) 89.073 ms 25.624 ms
25.298 ms 3 sea-gw.isomedia.com (207.115.64.129) 25.932 ms 25.533 ms
25.838 ms 4 361.atm3-0.gw8.sea1.alter.net (157.130.177.9) 40.806 ms
29.177 ms 32.575 ms 5 103.atm2-0.xr2.sea1.alter.net (146.188.200.46)
26.120 ms 26.074 ms 26.172 ms 6 0.so-0-0-0.xl2.sea1.alter.net
(152.63.106.233) 46.683 ms 26.128 ms 32.868 ms 7
0.so-0-1-0.tl2.por3.alter.net (152.63.107.157) 42.984 ms 29.715 ms
30.713 ms 8 0.so-3-0-0.tl2.lax9.alter.net (152.63.0.166) 53.953 ms
51.132 ms 50.450 ms 9 so-1-0-0.xl2.lax2.alter.net (152.63.3.186)
676.681 ms 51.454 ms 54.204 ms 10 pos5-0.xr2.lax2.alter.net
(152.63.115.234) 683.135 ms 51.066 ms 58.730 ms 11
194.atm7-0.gw3.lax2.alter.net (152.63.53.45) 58.402 ms 51.187 ms
74.011 ms 12 affinity-lax-gw.customer.alter.net (157.130.229.246)
593.734 ms 58.486 ms 54.421 ms 13 somehost.affinity.com
(207.150.223.1) 56.767 ms 54.437 ms 53.517 ms 14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
and it just keeps going without ever resolving. Might want to call your
ISP and find out what's going on with the DNS settings.
--
Chip
HWG hwg-techniques mailing list archives,
maintained by Webmasters @ IWA