Overview
Start here
Getting started
Concepts
Team & ownership
Deployment regions
Guides
Custom domains
Connecting a coding agent ↗Resources
Release notes ↗System status ↗Guide · Networking
Adding a custom domain
Point your own domain (e.g. app.yourcompany.com) at any environment of a syntica application. TLS certificates are issued and renewed automatically, with nothing to configure beyond one DNS record.
Requirements
Any hostname you control: a subdomain like app.example.com, or a root domain like example.com on its own. Both are supported, and each takes a different DNS record.
Access to your domain's DNS settings, to add one record.
Add a domain
1
Open your application, select the environment (Dev / Staging / Production) you want to attach the domain to, and go to Settings → Custom domains.
2
Click + Add domain and enter your hostname (e.g. app.example.com).
3
Add the DNS record shown in the dialog at your DNS provider. Which record it is depends on whether you are pointing a subdomain or a root domain. The dialog picks the right one for the hostname you entered.
Subdomain, a CNAME at your hostname:
Type: CNAME
Name: app.example.com (your hostname)
Value: ingress.syntica.io
Root domain. A root domain cannot hold a CNAME, so it takes an A record pointing at our ingress. The dialog shows the exact address once you have added the domain:
Type: A
Name: example.com (your root domain)
Value: the IP shown in the dialog
If your provider offers ALIAS, ANAME or CNAME flattening at the root (Cloudflare, Route 53, DNSimple and others do), you can point that at ingress.syntica.io instead. Those answer with A records, so they work exactly the same way, and they keep working if our ingress address ever changes.
4
Save. That's it: syntica automatically detects the DNS record and issues a TLS certificate for you.
Status
Once added, the domain moves through these states automatically (checked roughly every minute):
Stuck on Waiting for DNS? Check the record's Name matches your hostname exactly, and that its Value is exactly ingress.syntica.io for a CNAME, or the IP from the dialog for an A record. A trailing dot is a common cause, as is using the wrong record for the hostname: a subdomain needs the CNAME, and a root domain needs the A record, since most providers will not accept a CNAME there at all.
Failed domains
If DNS or certificate issuance keeps failing, syntica retries automatically and marks the domain Failed after 5 attempts, with a reason shown inline. Fix the underlying DNS record and syntica will pick it up on its next check, with no need to remove and re-add the domain.
Bringing your own certificate
Need a certificate you manage yourself (e.g. an EV cert, or one issued by your own internal CA)? You can upload a certificate and private key for a domain instead of using the automatic one.
While a custom certificate is active, syntica will not auto-renew it. You're responsible for replacing it before it expires. You'll get email reminders at 30, 7, and 1 day(s) before expiry. Switch back to automatic renewal any time and syntica will re-issue a managed certificate.
We use cookies
We use essential cookies to run the site and optional ones to understand usage. See our Privacy Policy.