Skip to content
Craftifact

Use a custom domain

How to switch a Craftifact instance to your own domain, which DNS records are required, and how certificate issuance works.

Quick path

  1. Confirm that your instance runs on Pro or above.
  2. Open the instance in the Control Plane.
  3. In Reachability, note the IP address shown in the UI.
  4. Create or update the DNS A record for your domain so it points to that IP address.
  5. If you use restrictive CAA records, allow Actalis for normal issuance:
DNS 
@	600	IN	CAA	0 issue "actalis.it"
  1. If you also want the fallback issuer to work, allow Let’s Encrypt as well:
DNS 
@	600	IN	CAA	0 issue "letsencrypt.org"
  1. In Reachability, choose Edit, enter your domain in Custom domain, and use Save and restart.
  2. Wait for the restart to finish, then open the domain over HTTPS.

What happens after you save

  • The instance stores the custom domain and starts an application restart if the effective domain changed.
  • Craftifact serves the instance on the new hostname.
  • Caddy requests a TLS certificate automatically.
  • The configured issuer chain is Actalis first, with Let’s Encrypt as fallback if Actalis is unavailable.
Rationale: why the domain change triggers a restart
The active hostname is part of the deployed runtime setup. Applying a new domain is therefore not just a UI setting; it needs a redeploy of the running instance edge.

DNS requirements

  • Point the hostname you want to use to the IP address shown in the instance UI.
  • Keep the record aligned with the current instance IP if the UI ever shows a different value.
  • If you leave Custom domain empty later, the instance falls back to its default domain.

CAA notes

If your DNS zone does not use CAA, you do not need to add anything here.

If you do use CAA, the certificate authority must be explicitly allowed to issue for the domain. For the default path, permit Actalis. If you also want the fallback path to work, permit Let’s Encrypt too.