Same here,loads with Brad's link but I get the x's as well ??????

For those who can't get it to work, what do you get when you run nslookup? Type "nslookup thepsas.org" on a command prompt. It could be that your DNS server has an older ip address cached. Show us the output so we can find out which DNS server you are using as well.


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>nslookup thepsas.org
Server: s142-179-67-167.bc.hsia.telus.net
Address: 142.179.67.167

Non-authoritative answer:
Name: thepsas.org
Address: 65.18.214.18

I am not running XP.. and I am unaware of a similar command for ME...

Chad

Darren had the same problem. I checked with our hosting service and there are no IPs blocked or anything. For some reason some folks can't get to our site. Darren used to be able to, but no longer. He is checking with his ISP for any answers. Are those that are having troubles using the same ISP by chance?




------------------
MDM
http://www.thepsas.org/images/7-26-03_psas_banner.jpg

Well it works for me now??? Nice work Mike. Were are the photo's from?

Chuck, they are, but most of us that can get there also use the same ISP. I believe it might have something to do with router tables managed by our ISP.

If they can reach the site by IP address but not by domain name, then it shouldn't be a router issue but a DNS issue. They are probably using different DNS servers which is what we can find out if they run nslookup or ipconfig. For example "ipconfig /all"

If it starts working after a while, then it sounds like the DNS server they were using had an older and different IP address that was cached and then eventually refreshed with the correct one.

Sam, I think all BC Shaw customers use the same DNS. Funny, but doing a trace from my web server gives me a "Dest. hosdt unreachable" erro. I can see the site fine though.

They probably filter traceroutes with their firewall. Still, I would like to see which DNS servers they are using to confirm the DNS issue. Whenever I see this type of problem from my clients, it has always been a DNS issue. Its very easy to diagnose as long as we get the output from their ipconfig or nslookup command.

What we should see in this case is that by tomorrow when all the DNS's have refreshed, everyone will be able to access that site just fine.

I have been trying since thursday or friday to get on there. no go. so if the DNS is refreshed each day that isn't the fix.