How do I connect my domain name to a Faaaster site?
The site's Domains tab manages the Primary domain and the Secondary domains. The Edit button in the Primary domain block connects your domain to the site, and Add a domain attaches secondary domains to it.
You don't have to buy your domain from Faaaster. A domain purchased elsewhere connects the same way, by pointing its DNS records to the site.
Attaching a domain
- Open the site, Domains tab.
- In the Primary domain block, click Edit: the Connect a domain window opens.
- Enter your domain (for example
www.example.com), then click Connect. - Create the records shown at your registrar, then click Confirm and connect — the button becomes active once the DNS records are verified.
For a secondary domain, click Add a domain in the Secondary domains block, enter the Domain name, then click Add.
Primary domain and secondary domains
- The primary domain is the site's official address.
- Secondary domains point to the same site.
When the site is created, the primary domain is the temporary .faaaster.dev address. The Edit button lets you change it.
The records to create
Faaaster calculates and displays the exact records for your domain. Don't look for them anywhere else: the DNS link, in the Actions column of the Domains tab, lists them with Name and Value, each with a button to copy it. The screen tells you: "Add these records with your registrar to point this domain to your site".
For a secondary domain, the DNS link on its own row shows the records to create for it.
Prefer a subdomain such as
www. A root domain cannot carry a CNAME, which deprives it of the CDN Proxy, the WAF and Edge Caching. Faaaster recommends connecting the site onwwwand redirecting the root domain.
Checking the configuration
The Verify button re-runs the DNS check. Three messages are worth knowing:
Message | What to do |
|---|---|
"No DNS found" | Check that you do own the domain and that the records are saved at your registrar. |
"It looks like your DNS is managed by Cloudflare!" | Turn off the Cloudflare proxy (orange cloud → gray) while the validation runs. |
A record to delete | An existing record conflicts and blocks the certificate from being issued. |
DNS propagation can take several hours. A failed check right after you enter the records doesn't mean your configuration is wrong.
What about HTTPS?
The certificate is issued automatically as soon as the domain responds — there's nothing for you to do. It's a Let's Encrypt certificate, free and included in all plans, renewed without any intervention.
The status shows in the Domains tab, in each domain's HTTPS column: active (with its expiration date) once the certificate is issued, otherwise a status such as generating…, no certificate or failed, with its reason and a Generate certificate or Retry button. Depending on the site, the status may also show as active · automatic ✓ or pending.
A certificate that doesn't arrive almost always means the DNS doesn't point to us yet — the reason shown then says so: "the domain does not answer yet (DNS not propagated?)". It's a consequence, not a cause: fix the DNS, and the certificate will follow.
The primary domain determines the site's canonical URL and the certificate; the other domains redirect to it.
Improving your email deliverability
The same screen checks your SPF record and suggests the value to add if it's missing, or the fragment to insert into an existing SPF record.
👉 How do I manage a domain's DNS? · What are the CDN Proxy and Edge Caching?
Updated on: 10/03/2026
Thank you!