Integrating your subdomain with SystemeScale
In this article, you will learn how to map a custom subdomain into your account dashboard and configure the required DNS routing parameters inside your web hosting platform.
What you will need:
- A SystemeScale account
- A custom subdomain name (e.g.,
subdomain.domain.com)
⚠️
Single-Platform Allocation Rule
A specific subdomain can only link to one website entity at a time. If your chosen prefix currently points to an active external site, completing this integration will overwrite that connection. Avoid using subdomains with pre-existing live web traffic.
Step 1: Declare your subdomain inside your portal settings
1
Profile picture → Settings → Custom Domains → Add domain
Hover over your user profile avatar, select Settings, click Custom Domains, and click Add domain.
2
Add domain
In the pop-up modal, type your full subdomain path (e.g.,
subdomain.yourdomain.com), then click Save. A validation popup will appear containing two unique CNAME records — keep this panel open.Step 2: Add your CNAME configurations inside your web host
Log into your domain host (GoDaddy, OVH, Namecheap, Cloudflare, etc.) and open your target domain's DNS records tab.
3
Go to your DNS zone
Locate your core domain management board and open your active DNS zone to add new records.
Create two CNAME type records using the values from your portal popup:
A. Configure your First CNAME record
- Type: Select
CNAME. - Host (Name): Input your subdomain prefix only (e.g., for
blog.domain.com, enter onlyblog). - Value (Target): Paste your provided Cloudfront destination path (e.g.,
d2dce8ts2ciq5z.cloudfront.net.).
B. Configure your Second CNAME record
- Type: Select
CNAME. - Host (Name): Paste the security token string before your main domain (e.g.,
_a41fe7898323c8ea5ebaf16307a266e6.subdomain). - Value (Target): Paste the matching validation path (e.g.,
_ce87b78e58e47e4cfc0ba0e4800001a2.mzlfeqexyx.acm-validations.aws.).
🔍
Verifying your network records propagation status
Go to dnschecker.org. Input your full subdomain address, change the verification type to CNAME, and click search. Your custom paths should match with green indicators.
📌
Propagation timelines
DNS entries can take 24–48 hours to fully propagate. If your host refuses a new entry, check for pre-existing conflicting A, AAAA, or CNAME records on the same prefix label. Contact your domain host support to safely remove old placeholders.
Prefer connecting your primary root apex domain?
If you want to integrate a root apex domain (e.g.,
www.domain.com) instead of a subdomain, view our root domain connection guide.Was this article helpful?