I have an interesting problem to sort out. I have a number of websites that I'm building using Drupal. At present, I'm building each site in my "localhost" (just getting the modules customized, themed, etc.), and I will eventually be moving each to its own live server account using a HostGator Reseller account.
The problem comes with domains. Each site is going to replace an existing site with a domain, but before redirecting the DNS to the new servers (based in HostGator Reseller accounts), I need to have the Drupal sites working first.
One thought I had was to create each site under a temporary domain name, and then simply redirect the DNS's when the development was complete. The main problem I see with this is that it may be necessary to register a temporary domain if the client doesn't currently have one. The other concern with this is that when switching domains, some Drupal modules / features might break. This would be a problem for sure, especially considering we're using ecommerce modules across the board.
Another thought I had was to create new sites under subdomains of our company's website, and then redirect the DNS when the development is complete. But I've seen lots of posts showing problems with this, and furthermore, I would have the same issues noted above.
What to do? Am I going to HAVE to take the clients' existing sites down in order to get Drupal up and running, or is there a way I can develop it behind-the-scenes?