Custom domains

Serve a web service on your own hostname with automatic HTTPS.

Every web service gets a Guidal-assigned URL as soon as it deploys. Adding your own domain points a hostname you control at that service, with a TLS certificate issued and renewed automatically.

Plan requirement

Custom domains are available on Pro and Team. On Starter, services are reachable at their assigned Guidal URL.

Add a domain

bash
guidal domains add app.example.com --service api

The command prints the DNS record to create. Add that record at your DNS provider, then verify:

bash
guidal domains verify app.example.com

Verification confirms the record resolves as expected. DNS changes can take anywhere from a minute to a few hours to propagate depending on your provider's TTL, so a verification that fails immediately after you add the record is usually just early.

Check status

bash
guidal domains list
guidal domains get app.example.com
guidal domains ssl app.example.com

domains ssl reports certificate state. A certificate is requested once verification passes; until then the domain resolves but does not serve HTTPS.

Remove a domain

bash
guidal domains remove app.example.com

Traffic to that hostname stops being routed immediately. The service stays reachable at its Guidal URL.

In the dashboard

  1. In the navigation pane, choose Domains.
  2. Choose Add domain.
  3. Enter the hostname and choose the target service.
  4. Choose Add, then create the DNS record shown.
  5. Choose Verify.

Apex domains and subdomains

Subdomains such as app.example.com are pointed with a CNAME record.

Apex domains — example.com with no subdomain — cannot use CNAME under the DNS specification. Providers that support ALIAS, ANAME or flattened CNAME records handle this; if yours does not, serve from a subdomain and redirect the apex at your DNS or CDN provider.

Troubleshooting

If verification keeps failing, confirm the record with a direct query:

bash
dig +short app.example.com

The answer should match the target Guidal printed. A common cause is a proxy sitting in front — providers that proxy traffic by default may need it disabled until verification completes.