Accidentally deleted Domain

[mycoo368]

@Anna

mycoolweb.x10host.com

I accidentally deleted it from DirectAdmin, can staff put it back please? I try to add it back and it keeps telling me it already exists. Or to at least apply a backup from yesterday on the account that puts everything back. Thank you in advanced.

 

[mycoo368]

So that this way the backup can put all of my DNS records back on.

 

[paragond]

@Anna

http://paragondezign.x10.mx/

Did the same as above. Can you please restore my domain as I can no longer log into my directadmin page or my FTP.

 

[Anna]

So that this way the backup can put all of my DNS records back on.

There are no option to use a backup for the DNS records for individual users (that is only part of the serverwide backup in case of crashes). It would be part of the migration package though, but I do not have access to that, and using it would restore everything to how it was just after the migration of your account was done with all settings and email etc.

The reason you got a message that it already existed was due to the folder still being there with the name of the domain, I renamed that to end with _back. Once I had the domain recreated I copied the files from public_html of the _back folder to the one that would be in use. When you have verified that it works properly and that all files are where you expect them you can remove the extra folder.

 

[Anna]

@Anna

http://paragondezign.x10.mx/

Did the same as above. Can you please restore my domain as I can no longer log into my directadmin page or my FTP.

It would seem that you did not do the same as above, you renamed the default domain and that should not affect your ability to login. However I did find your IP as being blocked by firewall, reason was: "Failed DirectAdmin login".
I have unblocked your IP.

 

[paragond]

It would seem that you did not do the same as above, you renamed the default domain and that should not affect your ability to login. However I did find your IP as being blocked by firewall, reason was: "Failed DirectAdmin login".
I have unblocked your IP.

Thank you I can now login.

I was having issues with my email before as well. Prior to the cpanel switch to new system my email was ****@paragondezign.com

after the switch I could no longer use that email to login to my email. I had to use ****@paragondezign.x10.mx to login even though my email was setup as john@paragondezign.com

I was trying to fix this issue, which is why i was trying to change the domain. After logging in, my email accounts are gone except the default. I added the email account I wanted and am able to login but the email account has nothin gin it.

And now I can't login to the ****@paragondezign.x10.mx where all my emails were before I was locked out.

 

[paragond]

@Anna

It did it again and I have been paying more attention to what is going on.

My normal method to login to admin panel is to go to x10 hosting website and login to through there.

I get this page....

And I was able to login normally without issue.

Then while I was in the Admin Panel, after changing some settings, it automatically logged my out and pulled up a login screen for Direct Admin (I am sorry I do not have a screen shot of this page as I cannot get back into my account)

This login page did not accept the same login credentials as the first login page shown above.

Which is probably why it locked my out for failed login. Any way to find out why this is happening?

Also any way to recover my email as mentioned above?

 

[mycoo368]

There are no option to use a backup for the DNS records for individual users (that is only part of the serverwide backup in case of crashes). It would be part of the migration package though, but I do not have access to that, and using it would restore everything to how it was just after the migration of your account was done with all settings and email etc.

The reason you got a message that it already existed was due to the folder still being there with the name of the domain, I renamed that to end with _back. Once I had the domain recreated I copied the files from public_html of the _back folder to the one that would be in use. When you have verified that it works properly and that all files are where you expect them you can remove the extra folder.

I guess I can wait a bit for all the DNS Records. I don't mind if it restores to the original transfer date, as I don't make many changes, just minor content optimizations here and there. I already use a 3rd party for emails, so they'll remain safe. A portion of my DNS Records came back on their own after adding it back on, but at the moment, it seems to be mostly good.

 

[mycoo368]

There are no option to use a backup for the DNS records for individual users (that is only part of the serverwide backup in case of crashes). It would be part of the migration package though, but I do not have access to that, and using it would restore everything to how it was just after the migration of your account was done with all settings and email etc.

The reason you got a message that it already existed was due to the folder still being there with the name of the domain, I renamed that to end with _back. Once I had the domain recreated I copied the files from public_html of the _back folder to the one that would be in use. When you have verified that it works properly and that all files are where you expect them you can remove the extra folder.

@Anna

Would it be possible to reuse the migration package at some point to re-perform it? The only reason I ask is because of Cloudflare. It seems by using the migration package itself, it allows Cloudflare to function after re-adding the CNAME records such as for www.mycoolweb.x10host.com.cdn.cloudflare.net for the www subdomains and go through Cloudflare's network. Now with having it re-added itself manually, it results in an Origin DNS Error 1016 on Cloudflare.

 

[Anna]

The migration process is done on a higher access level then I have so I wouldn't be able to pull the package from the old servers, and I'm not sure I'd have the access to restore the package onto the new server either given it needs to be run through some conversions as it is going from cpanel to directadmin.

Technically it should be possible, though it would likely be a long wait before it could be done, to my knowledge there is one server that is not yet fully migrated as well.

If you know the records that needs to be added, perhaps it would work if I add them from the dns managerinterface as admin, not sure though but surely fairly fast to test.

 

[mycoo368]

The migration process is done on a higher access level then I have so I wouldn't be able to pull the package from the old servers, and I'm not sure I'd have the access to restore the package onto the new server either given it needs to be run through some conversions as it is going from cpanel to directadmin.

Technically it should be possible, though it would likely be a long wait before it could be done, to my knowledge there is one server that is not yet fully migrated as well.

If you know the records that needs to be added, perhaps it would work if I add them from the dns managerinterface as admin, not sure though but surely fairly fast to test.

@Anna,

After the domain came back on, some of the records came back on their own, where its only the Cloudflare records now that are out of touch.

 

[Anna]

I guess I can wait a bit for all the DNS Records. I don't mind if it restores to the original transfer date, as I don't make many changes, just minor content optimizations here and there. I already use a 3rd party for emails, so they'll remain safe. A portion of my DNS Records came back on their own after adding it back on, but at the moment, it seems to be mostly good.

I have bad news, appears that they didn't actually keep the migration packages after accounts were transferred (makes sense really as we'd have needed at least double diskspace to keep all those).

The old servers are online so in the event of failed transfers there would have been an option to redo them, however that wouldnt solve your issues since the nameservers are the same on both the old and the new servers so you'd get the updated, now incorrect, records only.

However, you can actually change the name servers of your domain from within directadmin, so perhaps you can manage to get cloudflare working that way instead. I myself does not use cloudflare but I did test and it updates the nameservers properly throughout internet when changing to something else

 

[mycoo368]

I have bad news, appears that they didn't actually keep the migration packages after accounts were transferred (makes sense really as we'd have needed at least double diskspace to keep all those).

The old servers are online so in the event of failed transfers there would have been an option to redo them, however that wouldnt solve your issues since the nameservers are the same on both the old and the new servers so you'd get the updated, now incorrect, records only.

However, you can actually change the name servers of your domain from within directadmin, so perhaps you can manage to get cloudflare working that way instead. I myself does not use cloudflare but I did test and it updates the nameservers properly throughout internet when changing to something else

I was actually just able to get Cloudflare to work now. I was missing the Cloudflare-resolve-to CNAME record so Cloudflare network could resolve it. A friend of mine tried the name servers change and realized nothing was still pointing to Cloudflare even after a day and he reached out to Cloudflare and they show even though it was added, the registrar needs to have it updated. Not sure if it is a propagation issue and it hasn't propagated those changes.