A friend of mine has this week bought herself a domain, its set up fine, and everyone can access it, everyone except her. she gets errors when she tries to access the domain with IE6 and has to use a webproxie to get to the site at all.
My first idea was that maybe her ISP is the problem, but she can ping the domain from her computer and gets standard results. I went through the IE settings with her and didnt find anything unusual.
Any ideas because I am well out of them (and yes cleaning cookies and history was the first thing).
Alright, if nothing else, I’ll give you a bump. Since you dropped off the first page with only six views and no responses, I take pity on your soul.
My guess: The problem is already resolved.
When you say she can “ping the domain”, do you mean she can go to a DOS prompt and type “ping wwwherdomain.com” and get successful replies? If so, take the dotted IP address that shows up in the ping output and type that into the browser Address field. Does the page resolve (just not by domain name)? If it does, then it is likely a DNS issue. Wait a day, and if it still isn’t working, have her check her ISP’s technical support pages for information on DNS. If it doesn’t…
Cookies and History aren’t going to fix it, but the browse cache could. Be sure to clear that (delete tempoary internet files).
Otherwise, there could still be a web-caching server that is serving back the Page Not Found) message (that was the error she was getting, wasn’t it?). If this is the case, other than trying to connect via another ISP, the only option is to wait until the cached page expires.
If all else seems to be working, I’m not sure what else it could be.
AZCowboy had the answer buried in there someplace. It’s a DNS issue. A new domain, or one which has been moved, needs to propagate, that is every DNS server on earth msut be told that www.somesite.com equates to the IP address 123.45.678.90, for example. This process can take up to a few days to complete. So, just give it time, and eventually she’ll be able to access it using the domain name. For now, she can use the IP address to get there.
I agree, it’s probably just DNS. However, she may not even be able to get there by IP address. Most websites use virtual hosting and have to be accessed by their domain name. Just having the IP address won’t always do it. There probably aren’t enough IPs available for every website to have its own.
For an example of this, check out www.tagor.com. Works just fine when you put www.tagor.com in the address bar, but when you put in just the IP address (216.153.37.100) you get a DNS error.
So she shouldn’t be alarmed even if the IP doesn’t work. Her domain will probably resolve soon.