Skip to main content
Custom domains let your Edge Compute function respond at a domain you own — for example, api.acme.com — instead of the default *.telnyxcompute.com URL. Both URLs keep working; the custom domain is additive. You bring your own TLS certificate. Telnyx encrypts and stores it so your domain stays live even if infrastructure is rebuilt. Verification works with any DNS provider via a TXT record — Telnyx does not need to own your DNS zone.

​
How it works

  1. Declare the domain in telnyx.toml
  2. Register it with telnyx-edge domains add — get a DNS TXT record and routing IP
  3. Add DNS records — TXT for verification, plus an A or CNAME record pointing your domain to Edge Compute
  4. Verify ownership with telnyx-edge domains verify — Telnyx checks the TXT record and deploys HTTP routing
  5. Upload your cert with telnyx-edge domains cert upload — Telnyx validates, encrypts, and deploys HTTPS routing
  6. Manage with telnyx-edge domains list and telnyx-edge domains delete
The default *.telnyxcompute.com URL continues to work alongside your custom domain.

​
Prerequisites

  • A deployed Edge Compute function
  • A domain you own, with access to its DNS configuration
  • A TLS certificate (PEM-encoded cert + private key) covering the domain
  • Edge Compute CLI v0.5.0 or later

​
Telnyx vs a reverse proxy

You could put your own CDN or reverse proxy in front of a telnyxcompute.com URL. Custom domains remove that need:

​
What’s not supported

  • Auto-provisioned certificates (ACME): You must obtain and renew your own TLS certificate. ACME support is planned for a future release.
  • Wildcard domains: Each domain must be registered individually.
  • HTTP-only custom domains: HTTPS is required. The domain is reachable over HTTP after verification but HTTPS is enforced once a cert is uploaded.