DNS system is back to normal!

[RichardK]

I still cannot get http://coltpixy.com My other domain took about 3 hours to propagate but this one still does not work after 16 hours. Any help would be much appreciated.

Hello,

I just tested this and it comes up fine.

You have a page up that says:

We're doing some maintenance. Check back soon.







Can anyone else on here confirm this for Colty?

[bytesback]

UPDATE: In less than a minute after I posted this, http://www.roseprojectfund.com started resolving from my work ISP again. If anyone at NameCheap did anything to correct this just now, THANK YOU!

I changed over to the backup DNS about 18 hours ago but I still can't resolve http://www.roseprojectfund.com (which is a URL forward) from my work ISP. Other ISP's I've tried seem OK. I was previously told that some ISP's take longer to see the change than others... but 18 hours?? Support just said to give it time...18 hours ago.

My real site domain is http://sites.google.com/site/roseprojectfund/ which resolves fine from my work ISP and any other I've tried. I do want to point out that the "www" is required on the beginning of my domain name http://www.roseprojectfund.com because Google Sites does not support naked links (i.e roseprojectfund.com).

Any help would be appreciated. http://www.roseprojectfund.com always came up fine on my work ISP before the DoS attack.

OK...now my site mysteriously is not resolving again from my work ISP. What is going on???

[RichardK]

Bytesback, your site works fine as well.

[coltpixy]

That is what it is supposed to say. Wonder why it is taking so long on my end? As long as you can see it I know it is there and will show up for me eventually.
Thank you for checking. I was beginning to think I did something wrong when doing the temp fix.

[bytesback]

Bytesback, your site works fine as well.

All I can figure is that is must be something about my work network that is having issues with my domain. I consistently have issues accessing my domain over this network since yesterday's ordeal even though I have tried on my network between 2 different stores that have different ISP's.

The site will work for me fine for a while then will bring up "The Page Cannot Be Displayed" message. Any idea on why my access would be intermittent? As I said, only my domain is affected on this network. All other sites work normally.

[coltpixy]

bytesback, I can see The Rose Project.
Still cannot see my site but RichardK could. I am at home so I don't know what is causing my problem. I set mine around 7pm and it is now 11:17am and thought that would have been more than enough time to propagate. I know it is frustrating but apparently our sites are there for other people.

[bytesback]

bytesback, I can see The Rose Project.
Still cannot see my site but RichardK could. I am at home so I don't know what is causing my problem. I set mine around 7pm and it is now 11:17am and thought that would have been more than enough time to propagate. I know it is frustrating but apparently our sites are there for other people.

Thanks, coltpixy. If it's any comfort, I can see your site, too.

[vladoliki]

Hi and thanx for the support today! Yet it seems that some problems persist. My domain vladoliki.com started working normally several hours again when I reset the settings back to the original DNS (as advised by you I entered "ns1.namecheaphosting.com" at "dns to webhost" and then immediately switched back to "transfer dns back to us"). However, few minutes ago when I tried to access mail.vladoliki.com (or any other subdomain set at this domain) I got an "Address Not Found" message so we're back at the beginning

[RichardK]

Hello,


mail.vladoliki.com is resolving fine.

Guys, the reason you guys can see each others sites but not your own is because of cache issues. You guys have accessed your sites before therefore they are cached but the people testing them haven't so they get to the live site. Just give it some time to clear out.

[codefruit]

Yesterday, during the outage, I selected the 'Transfer DNS to webhost' and transferred the nameservers to an external provider (I had been intending to do this anyway, but the outage forced me to do it earlier than expected). Very quickly I could access the site from my machine and I began to see visitors again. But over 24hrs later, some people are still having problems. For example, using just-ping.com, the domain name resolves correctly for 32 out of 34 locations. It is all very frustrating as we were featured in an important article today and still some people cannot reach us.

Is there any way that namecheap can expidite the propagation to the external provider? Or is there anything that could have gone wrong with the propogation due to yesterday's problems? Or is it just a case of waiting for the propagation to complete?

Thanks,

Jamie