There are limitations though. Most visitors will come in by direct request, and these visitors will automatically default to what we call the “index” page.

Unfortunately the limitation you are running into is not intrinsic to our solution. That particular limitation is intrinsic to the way the web works.

The reason is very technical. It has to do with the way DNS (the “switchboards” that direct internet traffic) works and can’t be easily explained. I’ll try though though:

A root directory can only have one page in it called “index”, and this will be the sites default landing page. This is a fundamental principle to how the web works. When the web directs a domain name request to a directory on a server without specifying an exact filename the page called “index” gets displayed first. Period. No earthly power can change this.

If you set the new domain up as an Alias the Alias domain will appear in the address bar, but by definition an alias will default to “index” page (again… unless you map it to a specific filename, or page).

In order to have a different domain map to a diferent page on the site you need to use what we call a CName record, and a Cname record is not like an alias. The sites real domain will appear in the address bar.

The only way around this is to set up a separate site. This means a separate DNS zone with a separate root directory with, and here’s the crux, a different index page.

Do you have any alternative solutions that do not include subscribing to additional sites on your server?