Skip to content

Use your own domain

Instead of the automatic {app}-{username}.{domain} hostname, you can put an HTTP service on a domain you own, like blog.example.com, over HTTPS. DedNets checks that you control the domain and that its DNS points at the right place, then provisions a Let’s Encrypt certificate for you automatically. (Since v0.2.3.)

You choose where TLS terminates:

  • DedNets shared edge - you point the domain at our edge with a CNAME (or an A record for an apex domain). Our servers terminate TLS. This is the zero-infrastructure option.
  • Your own node - you point the domain at one of your own hosts running the entrypoint role, and that host terminates TLS. Traffic never passes through our edge in plaintext.

On the Services page, click the globe action on an HTTP service and choose Attach a custom domain. Enter the domain, pick a front, and the dialog shows the exact DNS records to create:

  1. A TXT record at _dednets-challenge.<your-domain> with a token. This proves you own the domain.
  2. A CNAME (or A) record pointing the domain at the chosen front.

Create both records at your DNS provider, then click Verify. DedNets checks the token and that the domain resolves to the expected target. When both pass, the domain goes live and the certificate is issued on the first HTTPS request. A green https:// chip appears on the service.

DNS changes can take a few minutes to propagate. DedNets re-checks your domains periodically, so a domain will activate on its own once the records are visible; you can also click Verify again at any time.

A CNAME is not allowed on an apex domain (example.com with no subdomain). For the shared edge, use the A records shown in the dialog instead. For your own node, an apex is always an A record to the node’s address.

To offer the My own node option, run the entrypoint role on one of your hosts (a VPS with a public IP and a local Caddy). That host then appears as a node front, and DedNets verifies the domain resolves to its address before pushing the site to it. Removing the domain removes the site from your node.

Use the ✕ on the domain chip, or the Attach a custom domain dialog. Routing stops immediately.