I have a question:

Suppose I own a site, and a domain, 'mysite.com'.
I provide services to different clients, so clients open sub-domains under my site.
For example, the site 'test.com' will be at my site, at 'mysite.com/test.com', so the clients of 'test.com' will enter this sub-domain.

What I want, is that instead of this, the clients will enter 'test.com', and will see 'mysite.com/test.com'. Offcourse I want that all its sub-sub-domains, e.g. 'mysite.com/test.com/service2' will also be seen like 'test.com/service2', so simple redirect or something like that is not what needed.

The process is:
1. The client, 'test.com', will add a CNAME ( http://www.google.com/support/blogger/bin/answer.py?hl=en&answer=58317 ) at his side, with 'mysite.com'.
(So I can see it with NSLOOKUP Linux command)
2. I will do a thing to achieve what I want.

My question is how to do step 2 of the process ?
I am on Linux, Ubuntu, and maybe the way is something with OPENSSL LINUX command ?
If so, how exactly ? Or what other way ?
I want to do this from the terminal, or with Python, maybe even with both ways, so I can choose.

* First, I want to do this with uncertified sites, without SSL certificates, and later I want to add the option for SSL certificates also.


6 Years
Discussion Span
Last Post by davidchilders

Your question deals with a very complicated subject. We need more information in order to help.

Who has the authority to answer DNS lookups for your domain 'mysite.com' ?

Who has the authority to answer DNS lookups for your client's domains 'test.com' ?

Where ever these domains are point, that is where the changes / additions will need to be made.

If your domain 'mysite.com' can be reached at public IP address then your client will need to map their domain 'test.com' to the same public IP address.

Then, the web server that answers at that address will need to be configured to respond to 'test.com' in addition to 'mysite.com'.

But these are just the basics - if you could let us know more details, such as the exact domains, we can answer with more details.

Thank you!


Actually, I managed to do this partially (with help).
After the site, e.g. 'test.com' added the CNAME, I did so when users enter https://test.com, they will see https://test.com as the address, where they are actually at https://mysite.com/test.com - as I wanted.
However, now they get a message from the browser that this site is not secured, because a SSL certificate is missing. So now, all that missing is that 'test.com' will buy a SSL certificate, give me the details, and I should proceed with 'openssl' command, like this:
and then:

Am I right about the last steps ?



Yes - but be very careful that the SSL certificate is issued for exactly the text string that matches your URL -


This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.