Articles on: General

How to connect your Hostinger domain to systeme.io

On this page, you will learn how to add DNS records to Hostinger to connect your main domain name. This will allow you to add your complete website (www.domain.com) to systeme.io and use it as a custom domain for your sales funnels and blogs, which can be useful for your branding.


What you will need:

  • A systeme.io account
  • A domain name purchased from Hostinger


Important: Please follow the first step of this article before completing this one.


After adding the root domain in systeme.io, you need to access the DNS settings in your Hostinger account


Note 1: Each domain added to systeme.io comes with its own CNAME records that need to be added to your hosting provider’s DNS settings.


Example: 

In this example, we will connect the domain www.team-sio.com with systeme.io


First, hover over your profile picture, click "Settings", then go to "Custom Domains" and add your custom domain.


Before adding the 2 CNAME records, you must add 10 CAA records so that our servers can generate the SSL certificate for your domain, as a CAA error will display:


To do this, you must add two types of CAA for each certificate authority (CA):

  • Issue: allows the issuance of standard certificates.
  • Issuewild: allows the issuance of wildcard certificates.

Instructions for adding CAA type DNS records on Hostinger


Log into your Hostinger account, then at the level of your domain, click on "Manage".


Go to the "DNS / Name Servers" section to start adding the CAA records.

You need to add the 10 CAA records as described in the steps below:


1. Adding the "Issue" record for the CA domain "amazon.com" :

  • Type: CAA
  • Name: @
  • Flag: 0
  • Tag: issue
  • CA Domain: amazon.com
  • Click on Add

2. Adding the "Issuewild" record for the CA domain "amazon.com" :

  • Type: CAA
  • Name: @
  • Flag: 0
  • Tag: issuewild
  • CA Domain: amazon.com
  • Click on Add

3. Adding the "Issue" record for the CA domain "amazontrust.com" :

4. Adding the "Issuewild" record for the CA domain "amazontrust.com" :

  • Type: CAA
  • Name: @
  • Flag: 0
  • Tag: issuewild
  • CA Domain: amazontrust.com
  • Click on Add

5. Adding the "Issue" record for the CA domain "awstrust.com" :

  • Type: CAA
  • Name: @
  • Flag: 0
  • Tag: issue
  • CA Domain: awstrust.com
  • Click on Add

6. Adding the "Issuewild" record for the CA domain "awstrust.com" :

  • Type: CAA
  • Name: @
  • Flag: 0
  • Tag: issuewild
  • CA Domain: awstrust.com
  • Click on Add

7. Adding the "Issue" record for the CA domain "amazonaws.com" :

  • Type: CAA
  • Name: @
  • Flag: 0
  • Tag: issue
  • CA Domain: amazonaws.com
  • Click on Add

8. Adding the "Issuewild" record for the CA domain "amazonaws.com" :

  • Type: CAA
  • Name: @
  • Flag: 0
  • Tag: issuewild
  • CA Domain: amazonaws.com
  • Click on Add

9. Adding the "Issue" record for the CA domain "SomeCA.com" :

  • Type: CAA
  • Name: @
  • Flag: 0
  • Tag: issue
  • CA Domain: SomeCA.com
  • Click on Add

10. Adding the "Issuewild" record for the CA domain "SomeCA.com" :

  • Type: CAA
  • Name: @
  • Flag: 0
  • Tag: issuewild
  • CA Domain: SomeCA.com
  • Click on Add

Notes:

  • The TTL field is typically left at the default 14400 seconds(4 hours).
  • The character @ in the Name field represents the main domain (e.g., yourdomain.com).
  • These records are necessary to allow certain certificate authorities (CA) to issue SSL certificates for your domain.


Instructions for adding CNAMEs :

First CNAME:

  • Go to the "DNS / Nameservers" section of your domain name, then navigate to the "Manage DNS Records" section and select the record type "CNAME".

  • Add "www" in the "Name" field >> then add "dx0kitehhr3rp.cloudfront.net." in the "Target" field. Finally, click on "Add Record" to save the addition of your first CNAME.

Note: If a CNAME record with the name "www" exists, edit the target to "dx0kitehhr3rp.cloudfront.net."


Second CNAME:

  • Go to the "Manage DNS records" section of your domain name.
  • Select the type "CNAME" >> add in the "Name" field everything that is before the domain name, which in our example is "_d4817a3f3bbedeeecd67969a77dd7f16" >> then add "_cb26254000362fb7f45515ce07ffe73e.zfyfvmchrl.acm-validations.aws." in the "Target" field. Finally, click on "Add Record" to save the addition of your second CNAME.

Once the 10 CAA records and the 2 CNAME records have been correctly added to your host, you can check their functionality on the following site:


The indicators should all be green as shown in the example below. If not, the entries were not made correctly, and you need to review your DNS.


Checking the 10 CAA:


Checking CNAME 01:


Checking CNAME 02:


Add a redirection rule:


To redirect the root domain without the "www" to the one with the "www" (that is, from "team-sio.com" to "www.team-sio.com"), you need to create an ALIAS record from the root to the same destination used for the first CNAME record for your domain integration :

irst, please select the type "CNAME", then add "@" in the "Name" field, then add "d2gj8ppwppt8gt.cloudfront.net." in the "Target" field. Finally, click on "Add Record" to save the redirection.

Note 2: it can sometimes take 24 to 48 hours for DNS records to fully propagate.


Note 3: sometimes your host may not be able to register your CNAMEs due to a conflict with other DNS. This usually occurs when adding the first CNAME.


At that point, you need to contact your host to understand the importance of these DNS and to get the go-ahead for their removal.

Updated on: 13/06/2025

Was this article helpful?

Share your feedback

Cancel

Thank you!