Depending on your license, you have the option to host publications on a custom domain. This can be either a subdomain (e.g. subdomain.yourdomain.com) or a root domain (e.g. www.yourdomain.com).

In this article, we’ll talk about how you connect your custom domains to Foleon. 

Before setting this up, make sure you have access to your domain’s DNS settings.

Important note: the steps described in this article might not match your domain management portal documentation. Make sure you check out your portal documentation as well.

In this article

  • Connecting a subdomain to Foleon (e.g. ebook.yourdomain.com)
  • Connecting a root domain to Foleon (e.g. www.yourdomain.com)

Connecting a subdomain to Foleon (e.g. ebook.yourdomain.com)

If you want to publish your Foleon publications on a subdomain (e.g. ebook.yourdomain.com), follow the instructions below:

Step 1. Setting up a subdomain
This step requires access to your domain’s DNS settings. You can access this by signing into your domain management portal or reaching out to their support team.

From the DNS settings, you can create a subdomain by setting up a new CNAME record.

When creating the CNAME record, you’ll need to give it a name (or host) that matches the subdomain you want to create. For instance, if you want to set up a subdomain for eBooks you could name the record “ebook”. You would then end up with the following URL: ebook.yourdomain.com.

Next, you’ll need to enter a value that points the CNAME record to the Foleon servers. This is where you’ll need to insert the following:

s1.foleon.com.

The period at the end of this value is not always necessary. 

We suggest taking a look at your hosting overview and checking if your domain value also has a period at the end: 

If it does, add it to the value of the subdomain. If it doesn’t, don’t add it to the value of the subdomain.

Here’s a screenshot of what creating an ebook subdomain in GoDaddy would look like:

In our case, the domain value didn’t end with a period so we didn’t add it to the CNAME record value.

Step 2. Wait and verify your setup
Once you’ve created the new subdomain, you’ll need to wait a bit before verifying. It can take up to 48 hours (or even longer) before DNS records are processed.

To check if your new subdomain has been set up, navigate to the newly created subdomain (e.g. ebook.yourdomain.com) in your browser and keep refreshing the page until you see this Foleon 404 page:

If you see this 404 page, your subdomain has been pointed to our servers correctly. The 404 page shows because you haven’t published any publications on the subdomain yet.

If you see something different than the Foleon 404 page (for example a grey browser error page) it means that the subdomain hasn’t been linked correctly. 

This could be a result of improper configuration or that the DNS records aren’t processed yet.

We recommend refreshing the page or checking with your IT department on whether you’ve followed the above steps accordingly. If you still don’t see the Foleon 404 page and you’re sure you’ve followed all instructions properly, please reach out at support@foleon.com.

Step 3. Publishing on your subdomain
Once you’ve created the subdomain and verified that it’s working correctly, you can exit the DNS settings of your domain and go back to the Foleon editor. 

From dashboard > projects menu select the project you want to connect to the subdomain.

Next, click on the project settings button at the top of the page.

Once in project settings, select “Use your own custom domain” to connect the newly created subdomain.

Here you can change your domain setup. Under Domain, insert the entire subdomain (e.g. ebook.yourdomain.com) and hit Save.

That’s it! Publications in this project, will now be published on the newly created subdomain. These settings apply to the whole project so you only have to add and edit them once.

Important note: changing the hostname on a project will affect all publications within that project. If you’ve already published any publications within that project you might not want to change this.

Connecting a root domain to Foleon (e.g. www.yourdomain.com)

Besides publishing on a subdomain, you can also publish your Foleon publications on a root domain (e.g. www.yourdomain.com). This option is available only when the root domain isn’t already being used for anything else.

Usually, when setting up hosting for a root domain, you would edit (or create) an A record to point to an IP address. We don't recommend this because our IP address is subject to change.

We advise you to point your www subdomain to the Foleon servers, instead.

We’ll walk you through the process of setting this up and connecting your domain to Foleon.

Step 1. Setting up www as a subdomain

This step requires access to your domain’s DNS settings. You can access this by signing into your domain management portal or reaching out to their support team.

Once you’re in the DNS settings, you'll need to remove the existing www A record (if one exists). You don’t have to worry about this for now as it can always be set up again later. Once this is done, you’ll need to create a www subdomain as a new CNAME record (or edit it if it’s already there).

When creating the CNAME record, name it “www”.

Next, you’ll need to enter a value that points your www subdomain to the Foleon servers. This is where you’ll need to insert the following:

s1.foleon.com.

The period at the end of this value is not always necessary. 

We suggest taking a look at your hosting overview and checking if your domain value also has a period at the end: 

If it does, add it to the value of the subdomain. If it doesn’t, don’t add it to the value of the subdomain.

Here’s an example screenshot of what it would look like:

Step 2. Setting up a redirect
Please note that in order to send traffic to your Foleon publications, users will have to navigate to www.yourdomain.com. If they omit the www, they will land on the default location defined in your domain's A record.

There are a few ways to get around this.

If you have access to your .htaccess file, you can create a rule that forces all traffic to your root domain to be redirected to the www subdomain. Alternatively, you could use many domain registrars with forwarding options. 

For example, you can redirect http://yourdomain.com to http://www.yourdomain.com.

Step 3. Wait and verify your setup

Once you’ve created the new www subdomain, you’ll need to wait a bit before verifying. It can take up to 48 hours (or even longer) before DNS records are processed.

To check if your new subdomain has been set up, navigate to your domain (prefixed with www, e.g. www.yourdomain.com) in your browser and keep refreshing the page until you see this Foleon 404 page:

If you see this 404 page, your www subdomain has been pointed to our servers correctly. The 404 page shows because you haven’t published any publications on the subdomain yet.

If you see something different than the Foleon 404 page (for example a grey browser error page) it means that the subdomain hasn’t been linked correctly. 

This could be a result of improper configuration or that the DNS records aren’t processed yet.

We recommend refreshing the page or checking with your IT department on whether you’ve followed the above steps accordingly. If you still don’t see the Foleon 404 page and you’re sure you’ve followed all instructions properly, please reach out at support@foleon.com.

Step 4. Publishing on a root domain

Once you’ve created the www subdomain and verified that it’s working correctly, you can exit the DNS settings of your domain and go back to the Foleon editor. 

From dashboard > projects menu select the project you want to connect to the subdomain.

Next, click on the project settings button at the top of the page.

Once in project settings, select “Use your own custom domain” to connect the newly created subdomain.

Here you can change your domain setup. Under Domain, insert the entire subdomain (e.g. www.yourdomain.com) and hit Save.

That’s it! Publications in this project, will now be published on the newly created subdomain. These settings apply to the whole project so you only have to add and edit them once.

Important note: changing the hostname for a project will affect all publications within that project. If you’ve already published any publications within that project you might not want to change this.

Related articles

Did this answer your question?