: Strategy for hosting 700+ domains names, each with a static HTML site I have a portfolio of more than 700 domain names, and ideally I'd like to put up a single-page HTML/CSS/JavaScript webpage

@Becky754

Use Wildcard Virtual Host Container in Apache

You can configure Apache with a Wildcard virtual host container. You then control what domains are hosted by simply modifying your DNS to point to the appropriate IP address

If you have the same content on all pages, then just upload the content.

If you require different content, you can use a strategy that a customer of ours used.

The use a single index.php page. The page uses the hostname variable to pull the correct content from the database. In their case, they have different layouts that get populated with various content.

Another strategy I've seen is using Rewrite rules and directories for each site.

Use A records
Also I recommend using A records for this. It prevents the domains being CNAMEd back to a common domain. Can help obscure some simple domain mapping tools. Also prevents added DNS lookups.

So I would have

domain.com CNAME to domain.com domain.com to a A record pointing to an IP address.

Hosting Options

I would be surprised if you could do this with a shared hosting service. You will likely need a cloud or VPS system.

You may want to check out lightly managed VPS providers that will handle doing OS updates for you. Once it is setup, then you could stack 1000's of domains on the system if the traffic is low.

Vote Up Vote Down

@Moriarity557

Here is a solution that might work for you.

DNS / WEB SERVER SETUP

Get one static ip address and bind that to your web server. (IIS or Apache). Setup your master domains (example.com) DNS with correct A Records. Now if you visit Example.com then the primary site will show up. For all your other domains just create a Cname record which points to Example.com.

MULTIPLE SITES

If you are on Apache then you can follow this example to create a vhosts file that maps each domain to a different folder. stackoverflow.com/questions/775868/apache-and-mod-rewrite-redirect-domain-to-subdirectory
So in essence example.com/ is loaded form /var/www/example.com example.net is loaded from /var/www/example.net

If you are on Microsoft IIS servers then you cant really map domains that way, You would have to write a bit of RewWrite rules or could use ARR to serve as a reverse proxy to build up this functionality. Lots of posts on that on StackOverflow.

DEPLOYMENTS

If you want to get fancy install git on both your server and your dev box. Use something like BitBucket or GitHub to host your repositories. I would just make a master repo called Sites and have it located at /var/www/ with folders in it for each site. That way you dont have to manage a bunch of Git repos. When you are done coding on your dev machine, push your updates to your Git Host. GitHub / BitBucket both support post- hooks which can tell your server to download the new changes and updates.

Another poor man approach (specially on windows) is to use DropBox. We do this on our windows servers and it works like a charm. The only drawback with this approach is that dropbox will sync all code. So you have to be very careful and aware of the fact of what is in DropBox will be live on the server. We overcome this with series of ASP scripts which copy files from DropBox on the server to our WWW directory where we host all our files. We just call the script every time we want the updates to go live. Its not as fancy as Git but post hooks on windows are a huge pain in the rear. Plus having the ability to code on an ipad to edit files in dropbox is good in emergencies.

Amazon S3?

Lastly. If you are 100% sure your sites are all static and will remain that way consider using Amazon S3 to host your static site. S3 works with Cname records. So each site can be site2343.s3.amazon.bla.bla. The advantage is your code is safe and runs super fast. The disadvantage is that it can get expensive.

Vote Up Vote Down

@Annie201

@jonschlinkert setting up CNAMES has nothing to do with adding a single HTML page to 700 domains. CNAME's won't help any with SEO. If you're creating a single HTML page for each of your domains why not build an HTML template. I don't think you'll find any good method of inserting the copy into each page since you'll have to write the content at some point you may as well do it into the HTML pages themselves.

There are a few applications which let you manage multiple WordPress sites from a single dashboard that my be useful to you.

Vote Up Vote Down