Freq---
One thing i forgot to mention:
i own the domain <snip> Example.com (what we are discussing now) for more than 1 year. a week ago i had to renew the domain. This domain was registered at registerfly.com and i pointed the dns to my host, it was always like this. So a week ago when i wanted to renew it, i was thinking to transfer the domain to host and i did. After about 30 min i found out that the domain transfer can only be purchased with a hosting plan which i don't need. So i called the customer service and told them to cancel the purchase. I guess during that time the domain Example.com was already registered with a new IP address. So after i renew the domain at registerfly.com again, i started getting this error everyday, sometime it works, most of the time not. I'm guessing the problem is at the DNS, because i can access the page using ftp or by typing the ip address.
[edited by: Webwork at 10:39 pm (utc) on Dec. 29, 2005]
[edit reason] Charter [webmasterworld.com] [/edit]
Set up hosting for the domain and it'll show up once it resolves.
[edited by: Webwork at 1:51 pm (utc) on Dec. 30, 2005]
[edit reason] No hotlinks to personal websites [/edit]
Why not change it back to the IP you had it pointed to for a year? IMHO you'd best ask the host and/or the registrar's tech support if you can't figure it out and it still isn't working.
There are a number of web sites sharing the same IP address. Modern browsers will work correctly, as long as the domain name is used. If somebody uses a very old browser, or uses the IP address instead of the domain name, then they are going to see the message that you are getting. The message is generated by the web server.
I wouldn't use a name-based virtual host. Get your own IP address. They're OK for casual, personal web sites. Not for a professional site.
The only thing I would use name-based virtual hosting for would be if I had several aliases for the same website. e.g. examplesite.com, example-site.com, examplesite.net, etc. etc. You might want to use name-based virtual hosts if you want each one to display a unique name (instead of examplesite.com for all of them, as you would get if you simply CNAMEd them all to examplesite.com).
I was able to get the message you described by using the IP address instead of the URL. You ARE typing the domain name into your browser, right? Not the IP address? If you type the IP address, you are going to get that message, and it is correct that you should get the message.
Did you, at some point, have your hosting provider issue you your own dedicated IP address for your website? If so, you need to use that in your A records. NOT the shared address. It's quite possible they have it configured so that it will respond to either a shared address or a dedicated address.
But, in either case, you should still be seeing your web site, unless you have a very old browser, or are typing in the IP address rather than the domain name.
Anyway, if it works for everyone else, then it's not a problem, right? :)
If you have been trying to access your domain from your present ISP for these few days, your ISP's proxy may also be caching the previous version of your site.
Also if you are using windows, you can try to clear your DNS resolver cache by typing ipconfig /flushdns.
>>If you have been trying to access your domain from your present ISP for these few days, your ISP's proxy may also be caching the previous version of your site.
i think this could be something that have caused this problem. During that time i've tried to access the page couple times and i saw this error page which i could understand, because the DNS is not active at that time. How can i clear the cache of my ISP (comcast), do they aware of such as problem?
How can i clear the cache of my ISP (comcast), do they aware of such as problem?
You can't. They'll keep hitting on your old ip until the zone information for your domain expires. So you'll just have to wait. You can change your default DNS to your hosting's or another ISP for the time being or your could just nail the new ip address for your domain in your hosts file.
Again, if you're using windows, you can also type ipconfig /displaydns to show the list of the domains in your dns resolver and its ip addresses. If you see your domain in the list, check the ip address that is current resolving to.
i used ipconfig /displaydns and found my domain, before that i try to open the page. right now it works for me but i'm sure not for long. So i found my domain in the list and with the correct IP address, so i assume that is ok right now. If the site not accessible in the other time, will the ipconfig /displaydns show other IP address for my domain?
