2 domains to same root folder

[mangoprint]

Hi there,

Currently using Hostpapa.

I currently have www.examplewebsite.co.uk pointing to /public_html/examplewebsite.co.uk

Now, I also need the domain www.examplewebsite.com pointing to /public_html/examplewebsite.co.uk

Also, I need an SSL to work with both addresses. What's the best way to achieve this?

Many thanks!

 

[CS-Cart]

Since your hosting seems to work with cPanel, you may add a parked domain for the same folder, as described here:

http://cpanelguide.net/park.php

(Also, if you use some external domain registrar, please, do not forget to set the DNS for the second domain)

As for your second question: SSL certificate is issued to only one domain name (even yoursite.com and www.yoursite.com need different certificates). What you can do is redirect user from parked domain to the main domain, which has correct certificate and would not raise any warnings.

 

[mangoprint]

Thanks for that.

One thing i'm wondering is, if its parked won't that change the address from .co.uk to .com which would bugger up the SSL? I guess I need the .com working more as a forwarding address. Can this be done with the parking tool? I've already used it when setting up the .co.uk as that was purchased via another host.

 

[needaprint]

You could use masking but i am not sure an SSL will serve the .com site as the SSL is per domain name

 

[nickpp]

the ssl is tied to a domain unless you use a wildcard.
IAs mentioned above, just forward the non ssl domain to the ssl one.
Easy to do in cpanel.

most of our customers forget when the y set up the csr for the ssl is that the ssl is www. sensitive.

Ie make sure you set up the csr using http://www.yourdomain.com not http://yourdomain.com

 

[needaprint]

just another note: a wildcard wont serve a .com and .co.uk only http://*.yourdomain.com - so to do this two different IP's and two different certificates. then you get duplicate content probs.

 

[edmondscommerce]

dont forget as well you cant run two SSL certificates off the same IP address.

One way to get around this kind of thing that i have used in the past is to set up a generic third domain eg secure.co.uk or something which both domains can use as their secure section, perhaps as subdomains

eg

domain1.com
domain2.com
domain1.secure.com
domain2.secure.com