Can't find/load webpage for new domain

[tuongo]

Hi guys,

I just bought a domain (registerfly) and signed up for hosting (ripplehost). I'm suppose to wait 24-72 hours for the name to propagate across the internet after I change domain servers?

Well, I was fiddling around w/my website and 5 different people can see it now, but I can't. When I go through my VPN, I can see it, but that's it. Otherwise it just says it can't find my website. I have Verizon DSL (PPPoE). I called them, they said it's not them.

I've seen articles like this: http://www.annoyances.org/exec/show/article04-107
I tried it, but I still can't ping my own website.

I don't know what's up. Any suggestions?
Let me know if you need any more info from me.

 

[amdskip]

It may take a while for your Verizon DSL to update some type of server name list thingy I can't remember what's its called.

 

[T3C]

what amdskip meant to say was it may take up to 48 hours for the DNS to update

 

[QurazyQuisp]

Hello, you may want to clear all your cookies, history and everything then restart windows and if it still doesn't work then wait for verizon's dns servers to update.

 

[tuongo]

thanks guys. I've gone ahead and cleared everything, but it still doesn't work. Since everyone but me can see it (except through my VPN), it's Verizon that I'm waiting on? Maybe they just lag overall?

It's been over 48 hours, but I'll wait a couple more days before I start worrying. thanks again.

One last question: Why do I see a different screen when I use the IP vs. when I use the domain? I thought these were the same. Moreover, that's not what anyone else sees - they actually see the test page I have posted.

w/the IP I see:
Hey, it worked !
The SSL/TLS-aware Apache webserver was
successfully installed on this website.
If you can see this page, then the people who own this website have just installed the Apache Web server software and the Apache Interface to OpenSSL (mod_ssl) successfully. They now have to add content to this directory and replace this placeholder page, or else point the server at their real content.

w/the domain, the browser just can't find it.

 

[labgeek]

Webhosts no longer just hand out UNIQUE IP addresses without a reason to need them. Having a website no longer requires an unique ip address for that website. They now use virtual servers. A single IP can host dozens or even hundreds of websites. When the browser requests a page it now sends the actual request string, so the webserver knows which website to send back. Early on the client used to lookup the ip address for the server, and send just the directory/page portion of the request. So webhosts had to assign a unique IP address to every website. When you connect to the ip addressed version you'll usually see a default page for apache - the "Hey it worked" page.

If you want to see your website in the meantime add a line to your hosts file. For windows NT/2000/XP this should be in the /WINNT/system32/drivers/etc directory. Add a line:
ipa.ddr.ess.here www.yourdomain.com

where ipa.ddr.ess.here is the dotted notation ip address (xxx.xxx.xxx.xxx) followed by spaces or a tab then the fully qualified domain name including host (www.yourdomain.com) you may also want to put in another space and the domain name without the www. (ie just yourdomain.com) on the same line, like:
ipa.ddr.ess.here www.yourdomain.com yourdomain.com

Once your dns propagates you can comment out the line with a # at the beginning of it. When you change the file you should close Ineternet Explorer and restart it. It's not usually necessary to shutdown and restart (at least under NT/2000/XP).

Edit -
BTW, a couple of valid reasons you may need to have an ip addressed assigned are your own nameservers, and needing SSL for your website.