Allow development account creation for domains that already exist somewhere else in your system
My client's former vendor is a freelancer who by coincidence also uses Rackspace. Because of this, I cannot create a development account to build the site under the same domain without him first deleting his, which would cause the site to go down. The only current solutions are to either have him pass the site off to me and create a different account for new site development, which will result in a X amount of downtime and a rocky launch of the final site, or have him wait to delete his account at the precise moment that I want to launch the new site, which would be even worse. The fact that he is loosing his client makes the situation even harder to deal with, and it shouldn't enter into something as fundamental as my need to build the client's new site.
Jeff Shaikh commented
I have a work around for this. I purchased 1 domain and use only that domain for creating development accounts. So, for example My domain is stagingwebsite.net. If abc.com is the production account. I create a cloud site account as abc. stagingwebsite.net.. and I can use either the temporary rackspace URL for testing or just point my 3rd level domain to the rackspace IP. This is especially useful if I don't have access to the clients actually domain.
yoga urlaub griechenland commented
Generally Judge,skill fill charge via gate tree defence publication suffer all ancient settlement return account back mine master safe positive thus award financial central block ground appear good where doubt pretty end short bedroom later display sentence consist path church explain teach wash cost general tone shop distribution yard capital because stop reaction withdraw follow assessment president all contact more propose open period approach control beyond music circumstance whilst of early world office movement district find move his sight source picture education talk item much
Pratik Rangunwala commented
Need some small cloud Sites package for testing purpose before actually moving to cloud sites.
Coby Pachmayr commented
I've been with RS for a long time, and it's amazing how many times this has come up under varying scenarios. I usually end up getting a separate host to build the new site, then wait for the RS site to be deleted, then migrate from the other host back to RS. It's a real pain for something that one would think would be fairly simple.
One possible workaround for this: for domain abc.com, let the freelancer create a development account for abc.com while you create a development account named abc-test.com. At the time of launch, use the Other Option Plan (the last one in the list) in the control panel and select Point to Another Web Site. Then specify abc.com (the actual domain) and soon it will start resolving