How to connect your Hostinger domain to SystemeScale
On this page, you will learn how to add DNS records to Hostinger to connect your main domain name. This allows you to add your complete website, such as www.domain.com, to SystemeScale and use it as a custom domain in your sales funnels and blogs, helping strengthen your brand.
What you will need:
- A SystemeScale account
- A domain name purchased from Hostinger
Add your root domain in SystemeScale first
After adding your root domain to SystemeScale, you will need to access the DNS settings in your Hostinger account.
www.team-sio.com is being connected to SystemeScale. Your own records will be generated inside your SystemeScale account.First, hover over your profile picture, click Settings, then go to Custom Domains and add your custom domain.
Add the required CAA records in Hostinger
Before adding the two CNAME records, you must add 10 CAA records. This allows the servers to generate an SSL certificate for your domain and helps prevent CAA-related errors.
You will need to add two types of CAA records for each Certificate Authority (CA):
- Issue: allows the issuance of standard certificates.
- Issuewild: allows the issuance of wildcard certificates.
Log into Hostinger and click Manage next to the domain you want to connect. Navigate to the DNS / Nameservers section.
Add the 10 CAA records below:
| # | Type | Name | Flag | Tag | CA Domain | Action |
|---|---|---|---|---|---|---|
| 1 | CAA | @ | 0 | issue | amazon.com | Click Add Record |
| 2 | CAA | @ | 0 | issuewild | amazon.com | Click Add Record |
| 3 | CAA | @ | 0 | issue | amazontrust.com | Click Add Record |
| 4 | CAA | @ | 0 | issuewild | amazontrust.com | Click Add Record |
| 5 | CAA | @ | 0 | issue | awstrust.com | Click Add Record |
| 6 | CAA | @ | 0 | issuewild | awstrust.com | Click Add Record |
| 7 | CAA | @ | 0 | issue | amazonaws.com | Click Add Record |
| 8 | CAA | @ | 0 | issuewild | amazonaws.com | Click Add Record |
| 9 | CAA | @ | 0 | issue | SomeCA.com | Click Add Record |
| 10 | CAA | @ | 0 | issuewild | SomeCA.com | Click Add Record |
14400 (4 hours). The @ character in the Name field represents the main domain, such as yourdomain.com. These records are necessary to allow certain certificate authorities to issue SSL certificates for your domain.Add the first CNAME record
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 Value field. Finally, click Save to register the addition of your first CNAME.
www exists, edit the target to dx0kitehhr3rp.cloudfront.net.Add the second CNAME record
Go to the DNS Zone section of your domain name. Click Add new record, select the type CNAME, and add in the Name field everything that appears before the domain name. In this example, use _d4817a3f3bbedeeecd67969a77dd7f16.
Then add _cb26254000362fb7f45515ce07ffe73e.zfyfvmchrl.acm-validations.aws. in the Value field. Finally, click Save to register the addition of your second CNAME.
Check the records with DNS Checker
Once the 10 CAA records and the 2 CNAME records have been correctly added to your host, you can check their functionality using DNS Checker.
To check your records, enter the full CNAME name, including your domain name, into the search bar.
The indicators should all be green. If not, the entries were not made correctly and you need to review your DNS.
- Check the 10 CAA records.
- Check CNAME 1.
- Check CNAME 2.
Add a redirect rule
To redirect your root domain, such as domain.com, to the www version, such as www.domain.com, create an ALIAS-style root record from the root to the same destination used for the first CNAME record for your domain integration.
In Hostinger, select the type CNAME, add @ in the Name field, then add dx0kitehhr3rp.cloudfront.net. in the Target field. Finally, click Add record to save the redirection.
Important notes
- It can sometimes take 24 to 48 hours for DNS records to fully propagate.
- Sometimes your host may not be able to register your CNAMEs due to a conflict with other DNS records. This usually occurs when adding the first CNAME. If you encounter a record conflict, contact Hostinger support to determine if existing records are necessary or if they can be safely removed.