Jump to content

Recommended Posts

Posted

Due to circumstances i had to delete my account (not a big deal, not anything on it (due to those circumstances :P)) and since i usually miss the signup times for Stevie i went with Johnny again (might use ASP for the site in the future anyway)

So i deleted the first account and tried to create it again but i got this error:

"Your hosting account at HelioHost has encountered an error during installation. The error is:

Sorry, a DNS entry for one-woman-wolfpack.heliohost.org already exists, please delete it first (from all servers in the dns cluster)"

 

Would it be possible for me to do that? :) it is (well, was) my previous site. Don't know what other info i need to give you, so just ask :D

 

Thanks in advance

Posted (edited)

How long ago did you delete the account? Did you use the deletion script?

 

The account sits in a deletion queue just like new accounts sit in a creation queue. It may be that the script has not run on your account yet.

 

 

This is a link to an older post but with a similar situation. Check it out. http://www.helionet....h__1#entry70467

 

* not sure if you saw this post before I edited it. At first I thought the script may not have worked and I was going to suggest that you manually remove the info at godaddy.

While that may still be a possibility, I would not do that until you have waited a sufficient amount of time for the HelioHost deletion script to run its course.

 

Recommended wait time is 48 hours.

__________________________________________________________________________________________________________________________________

 

 

This is what I see when I DIG your account using the DIG tool at this URL - http://http://helioh...pl/dns-checker/

 

Edited by xwinuser
Posted

The only people who can delete the domain if it was not automatically deleted is the admins. They should see this thread soon and do whatever they need to do.

Posted

True, if the script failed the admins would need to fix. I would like to know if it worked after waiting which would indicate the queue was just backed up.

 

Also, some of the admins have stated they have been a little tied up the last few days.

 

I just want to get to the bottom of the issue for future references.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...