Odd Question

[Dyslexic Penguin]

Alright, I recently signed up here and according to just about everybody I talk to, my website, http://www.dyslexicpenguin.com is up and running.

However, me, and my friend Emily are unable to see it. The website is coming up as non-existant to us. Considering I've seen a SCREEN SHOT of my website working, I am very confused and am wondering if there is any way to fix this problem?

If it helps, I'm using Verizon DSL, and am currently in a dorm in Philadelphia, PA.

[Ron]

Perhaps your DNS is cached.
Maybe you transposed a couple of letters?

Dyslexic too, eh? I once joined DAM: Mothers Against Dyslexia.

[Dyslexic Penguin]

Everything seems to be in working order. My friend Sean, and Emily can't see the site either, and the only common bond is that we're in the same city.

[mattsiegman]

Your DNS server probably hasn't yet propogated the new IP entry. The site works fine for me.

[Dyslexic Penguin]

How long does that usually take?

[lookout]

Give it another day. The whois record on that domain name shows it was created on April 24th. Generally speaking, it takes between 24-72 hours for a domain name to propagate across the net, and it may take a bit longer in some locations.

[Vin DSL]

Originally posted by Dyslexic Penguin
How long does that usually take?

Evidently others can see your website, so what this comes down to are the zone files at your local ISP. Give your ISP a call and kick 'em in the butt...

[Vin DSL]

Yep, I can see it just fine... It's your ISP's fault...

EDIT: Oops! I re-read the post. You're in a dorm. So, it's Bush's fault...

[Galen]

Screw the ISP. If you're using Windows, edit your hosts file. Under Win2k, it's here:

C:\WINNT\system32\drivers\etc\hosts

Open it with notepad and add

xx.xx.xx.xx www.domain.com
xx.xx.xx.xx domain.com

replace the xx.xx.xx.xx with your site's IP addy. Save and close. Your system will use the hosts file FIRST before checking DNS servers.

Easy as pie. Completely bypass nameservers.

[jason]

Was the site hosted elsewhere before you came here? That would certainly explain what's going on--you and your friends who have visited the site recently (and anyone else using the same DNS servers as you) are getting cached results from your old host, while the rest of us, who haven't been to the site before, are getting fresh results from JPC.

BTW: looks fine from here.

--Jason

[lookout]

Yes, that would have an effect. It also generally takes longer for transferred domains to resolve than newly created ones. Some webhosts claim it can take up to a week in such cases, although my own experience has been it's usually quicker than that when the transfer is a clean one.

Per Galen's suggestion, AFAICT, the site is using a shared IP, like most new accounts here. So the account name will enter into the mix if D.P. wants to reach the site via an IP address. BTW, it might be a good idea to clear your browser's cache before checking whether the website has resolved or not.

Editing the hosts file should not be necessary. I wouldn't recommend doing so myself, unless one really doesn't care whether or not the domain name is actually resolving at one's location. I expect all this will resolve itself within the next day or so without additional user intervention, if it hasn't already.

[Dyslexic Penguin]

It's working for me now, so it was probobly just the DNS thing. Now I can move on to figuring out the e-mail address deal.