Custom domains, TLS included
Add two DNS records and we issue the certificate. Every domain gets its own CDN zone, and a custom domain is included on the free plan.
Two records, then it is yours.
Copy two values into your DNS provider: one sends visitors to your site, one proves the domain is yours. A subdomain takes a CNAME, a root domain an ALIAS.
| You have | Type | Name | Value |
|---|---|---|---|
| A subdomain | CNAME | blog | deploybase-d-0123456789abcdef.b-cdn.net |
TXT | _deploybase-verify.blog | 0123456789abcdef0123456789abcdef | |
| A root domain | ALIAS | @ | deploybase-d-fedcba9876543210.b-cdn.net |
TXT | _deploybase-verify | fedcba9876543210fedcba9876543210 |
Never an A record. The CDN has no fixed IP address, so a certificate could never be issued for one. Values here are examples; yours are in the dashboard.
Or let us host your DNS
Switch your nameservers once and we set up the records, add www for a root domain, and copy over the mail records we can find.
In beta. Turn DNSSEC off at your registrar first.
Checked from outside
We look your records up in public DNS, the way a visitor's browser would. Check again whenever you like, once a minute at most.
The certificate is our job.
As soon as your records check out, we request a Let's Encrypt certificate and renew it for you. This real domain went from added to serving over HTTPS in under two minutes.
Retries on its own
A certificate that fails is tried again every 30 minutes, and the dashboard names the likely cause: a leftover challenge record, an IPv6 record pointing elsewhere, a CAA record.
TLS 1.2 and up
Older protocols are switched off on every domain, with no setting to get wrong.
One domain, one CDN zone.
Your domain never shares a zone with another customer's. Each one gets its own, named by a hash so your domain does not appear in our hostnames. These are three real ones, renamed.
- example.com
deploybase-d-0a1b2c3d4e5f6071.b-cdn.net - example.nl
deploybase-d-8192a3b4c5d6e7f8.b-cdn.net - www.example.fr
deploybase-d-f0e1d2c3b4a59687.b-cdn.net
One primary address
Choose which address is the real one. Every other address of the site, including its deploybase address, redirects there with a 301.
Keep countries out, or in
Block a list of countries on a domain, or allow only some. example.nl above blocks one.
What custom domains do not do yet.
- Redirecting http to https A visitor who types http:// gets the site over plain HTTP. Forcing HTTPS, and the HSTS header with it, is not on yet.
- Wildcard domains Each hostname is added on its own. *.example.com is not supported.
- A domain on a preview Custom domains serve production. Previews keep their own address.
- DNSSEC with hosted DNS The zones we host are not signed yet, which is why DNSSEC has to be off.
Questions about custom domains.
Something else? Write to support@deploybase.eu. A person answers.
Is a custom domain included on the free plan?
Yes. Every plan, Free included, can serve its sites on your own domains, each with a TLS certificate we issue and renew for you.
Plan limitsWhy can't I use an A record?
Our CDN has no fixed IP address, so an A record would point at an address that changes, and the certificate could never be issued. Use a CNAME for a subdomain, an ALIAS or ANAME for a root domain, or let us host your DNS.
The setup guideHow long does it take?
Once your DNS provider publishes the records, usually a few minutes. The domain on this page went from added to serving with its certificate in under two minutes. DNS changes themselves can take longer to spread.
Can I use both the root domain and www?
Yes. Add both as separate domains and pick one as the primary address; the other redirects to it. If we host your DNS, www is set up and redirected for you.
Does it work over IPv6?
Yes. The CDN answers custom domains over IPv6 as well as IPv4.
Put your site on your own domain.
Create a team on the free plan, add your domain, and copy two records.