3 ms·
depends highly on your software stack that you're using to handle requests. for starters you'll need to define a wildcard in your domain so that *.mysite.com a
by there 17y ago
depends highly on your software stack that you're using to handle requests.
for starters you'll need to define a wildcard in your domain so that *.mysite.com all resolves to the same ip.
then you may have to configure your web server with the same wildcard, then once it trickles down to your application, you'll probably have to look at the SERVER_NAME variable passed by the web server.
- dtby 17y agoIf there is only one company requiring this functionality, you don't need a wild card. In the customer's DNS zone file: mysite.customer1.com. IN CNAME customer1.mysite.com. In your DNS zone file: customer1.mysite.com. IN CNAME www.mysite.com. Then, you'll need to decide how to configure the web server to provide the proper resource on requests for "customer1.mysite.com" In simple static situations, this could be as simple as a virtual host... more complex dynamic situations may require a redirector.
- dannyr 17y agoIt will be for all my customers. I just checked and my host supports wildcard domains. Posterous is doing the same thing. They are using an IP address to map the DNS though. I wonder if you can use a domain (e.g. ns1.mysite.com) in case the IP address changes. http://posterous.com/help/custom_domain http://posterous.com/help/custom_domain