PLEASE HELP!! Emergency!

• 

  phenomenality · Member · Feb 17, 2011 at 4:31 am

  • Copy link
  • Add topic to favorites

  I started a blog (originspreschool.wordpress.com) before I bought my domain name originspreschool.org. A few days later I purchased the domain and paid to have wordpress be the host. I soon found that it was not going to work for my needs. I used iWeb to create my entire site and then purchased hosting through iPage. I connected my ftp to my new iPage account and as I was about to upload it I remembered that I would have to turn off the domain that was pointing to wordpress. I deleted (I thought) the wordpress domain but what it did was make the originspreschool.wordpress.com the official site that now my actual url is directing to.

  I don’t know if any of that made sense but I am literally in tears right now.. How can I fix this? I need my domain back!!!

  The blog I need help with is: (visible only to logged in users)

• 

  auxclass · Member · Feb 17, 2011 at 6:32 am

  • Copy link

  originspreschool.org does not go to a WordPress.COM site – so did you get the changes to work? – keep in mind that it can take 24 to 72 hours for a Domain Name change, edit the name servers etc for the changes to make it to the far corners of the internet.

• 

  phenomenality · Member · Feb 17, 2011 at 6:51 am

  • Copy link

  I don’t know what you are seeing, but I’ve tried it on multiple browsers since you replied and when I go to http://www.originspreschool.org it goes right to originspreschool.wordpress.com

  I’ll try to breathe and wait till morning. ;)

• 

  justjennifer · Member · Feb 17, 2011 at 7:42 am

  • Copy link

  Clicking on your link it takes me to http://www.originspreschool.com/Origins_Preschool/Home.html So, problem solved?

• 

  raincoaster · Member · Feb 17, 2011 at 9:59 am

  • Copy link

  Yikes, you will want to shorten that URL.

• 

  auxclass · Member · Feb 17, 2011 at 2:39 pm

  • Copy link

  Check your DNS status: http://www.whatsmydns.net/#NS/originspreschool.org

  Looks like nothing related to WordPress.COM (good)

  There can be problems with local caching issues also, that just take time to resolve.