Multiple Domain Question

[Guest dave cohen]

Just a reality check request...

 

I am currently working on the next iteration of a Web site for a client. He already has a site at a different hosting company, but I set the new one up at TCH. Now the new site will have shopping cart, list manager, ssl...I was concerned about the coordination issues when it is time to make new site live: DNS pointers, ssl certificate install, all the internal changes. Then, the idea hit me - register a new domain, use that for the new site, then when the new site will go live, change the old domain to also point to the new site. So, if old site is abc.com, I build new abcd.com, and when it's ready, just point abc.com to it as well.

 

Is this as good an idea as I think it is? :-)

 

- Dave

[TCH-Andy]

HI Dave,

 

Yes that's a good way of doing it.

 

The only other thing you will need to change is the SSL cert ( as it will be for abcd not abc )

[Guest dave cohen]

HI Dave,

 

Yes that's a good way of doing it.

 

The only other thing you will need to change is the SSL cert ( as it will be for abcd not abc )

 

Thanks, Andy.

 

Oh, huh...so if they come into the site as via abc, and SSL cert was purchased for abcd, the SSL certificate won't be in force during checkout...right? I guess I'm not sure exactly what happens under the covers for multiple domains. Is there a 'primary' domain, so if they access the site via abc, then just acts like site abcd when they are there? ie, come in via www.abc.com, will they see www.abcd.com in address after they get there?

 

- Dave

[TCH-Andy]

If you go to https for abc.com and it's parked on abcd.com - and the certificate is for abcd.com - they will getting a warning in their browser that the certificate if for a different domain than the URL.

 

It will still work - but they will get a warning - and may decide not to continue

[Guest dave cohen]

If you go to https for abc.com and it's parked on abcd.com - and the certificate is for abcd.com - they will getting a warning in their browser that the certificate if for a different domain than the URL.

 

It will still work - but they will get a warning - and may decide not to continue

 

Ok, great - thanks again, Andy.

 

How about this approach. Again, old domain is abc.com, new one is acbd.com. Create SSL certificate for abcd.com and set up everything on TCH. Then, when I move abc.com to TCH - park it - can abc.com be set up with something like a permanent redirect to abcd.com? Thus, users visiting abc.com will seamlessly go to abcd.com, which will be all set up with certificate and other stuff. I'm just fuzzy on the whole parking/multiple domain thing. Again, my goal is to set up everything on abcd.com - ssl, cart, cc gateway, etc - and have it ready to roll before moving abc.com.

 

- Dave