How to connect your Cloudflare subdomain to SystemeScale
This guide shows you how to add a subdomain, such as subdomain.domain.com, to SystemeScale.
Using a custom subdomain for your sales funnels and blogs helps maintain a professional and consistent brand.
What you will need:
- A SystemeScale account
- A domain managed by Cloudflare
Add your subdomain in SystemeScale first
After adding the subdomain in SystemeScale, you need to see the DNS settings in your Cloudflare account.
example.test-sio.org is being connected to SystemeScale. Your own CNAME values will be generated inside your SystemeScale account.Log in to your SystemeScale account and click on your profile picture, then go to Custom Domains and add your subdomain.
First CNAME
Go to DNS, then click on the Records tab of your domain name.
Click Add record, select the type CNAME, enter example in the Name field, then add dv5xmtsih8vdv.cloudfront.net. in the Target field.
Set the Proxy status to DNS only, then click Save.
example already exists, edit its value to dv5xmtsih8vdv.cloudfront.net.Second CNAME
Follow the same process described above to add a new CNAME record.
In the Name field, copy and paste the string before your domain name, which in this example is _1e366b448745f61ccc649902693d7606.example.
In the Target field, add _c70c6d7febc99dd01828cb70f1c6b5c6.xlfgrmvvlj.acm-validations.aws..
Set the Proxy status to DNS only and click Save.
Check CNAME propagation
After adding both CNAME records, you can verify their status using DNS Checker.
To check your records, you must enter the full CNAME name, including your domain name, into the search bar.
You should see the same value you added next to a green checkmark. If not, the records have not been added correctly, and you need to review your DNS zone.
- CNAME 1 verification: verify the CloudFront CNAME record.
- CNAME 2 verification: verify the validation CNAME record.
Important notes
- It can take up to 24β48 hours for DNS records to propagate completely.
- Sometimes, your host may not be able to register a CNAME record due to a conflict with other existing DNS records. This usually happens when adding the first CNAME. If you encounter a conflict, contact Cloudflare support to determine if those existing records are required or if they can be safely deleted to allow your subdomain to connect.