Custom domains and SSL
Point a domain at a cloud hosting app, read the DNS state indicators, and get a valid certificate without retry loops.
Every app answers on a Zoophost hostname immediately. A custom domain needs two things: a DNS record pointing at Zoophost, and a certificate for the name.
Add the domain
- Open the app → Settings → Networking.
- Add the hostname under Domains, one per line, including the protocol:
https://app.example.com https://www.app.example.com - Save.
Add apex and www as separate lines if you want both. Use Redirect mode to choose whether www redirects to the apex, the apex redirects to www, or both serve the site.
Point DNS at Zoophost
The Overview tab shows a Domains card with the exact record to create and the current state.
| State | Meaning |
|---|---|
| DNS hosted here | The zone is on Zoophost nameservers and the record is managed for you |
| Points here | Public DNS resolves to Zoophost |
| Does not point here | The name resolves somewhere else |
| No A record yet | The name has no address record |
| Not a hostname | The value is not a valid hostname |
If the zone is on Zoophost nameservers
Use Host this domain here on the card, or open Domains & DNS and use the record editor. Zoophost writes the A record for you when the zone is hosted here.
If DNS is elsewhere
Create an A record for the hostname pointing at the address shown in the console. If the console offers a CNAME target instead, use that. Do not proxy the record while the certificate is being issued — a proxy hides the origin from the validation request in some setups. Turn proxying back on after the certificate is active.
DNS changes are cached. A new record with a short TTL usually takes effect in minutes; old records with long TTLs can take hours. Flush your local resolver cache before concluding that the record is wrong.
Certificate issuance
Zoophost requests a free Let's Encrypt certificate once the name resolves correctly. Issuance is automatic and renewal is automatic.
Two practical rules:
- Do not retry in a loop. Let's Encrypt rate-limits failed validations per hostname (5 per hour). Repeated retries keep failing even after you fix DNS. Fix the record, wait, then try once.
- Point DNS first, certificate second. A certificate cannot validate while the name resolves elsewhere.
Force HTTPS and compression
Settings → Networking also controls:
- Force HTTPS — redirect plain HTTP to HTTPS. Leave it on.
- Gzip compression — compress text responses.
- Strip base path prefix — for apps mounted under a subpath.
- Exposed port and Port mapping — only change these if the container does not listen on the expected port.
Common problems
The site loads on the Zoophost hostname but not the custom domain
DNS is not pointing here yet, or the hostname was added with a typo. Check the Domains card state and compare the record name exactly, including www.
“Does not point here” but DNS looks right
You may be looking at a cached answer. Query the name from a public resolver and confirm it returns the Zoophost address. If you use Cloudflare, make sure the record is not proxied during issuance.
Certificate pending for a long time
Check that port 80 reaches Zoophost for that hostname. A firewall, a redirect rule or a proxy in front of the origin can break HTTP validation.
www works, apex does not (or the reverse)
They are separate hostnames with separate certificates. Add both to the app and create both DNS records.
Mixed content warnings
The certificate is fine; the page loads assets over http://. Update the asset URLs or the framework's public URL setting to https://.
Next
- domain
- custom domain
- dns
- ssl
- https
- certificate
- lets encrypt
Ready to use this
Git-push containers, previews and custom domains, billed monthly in INR.
- 5 websites on the smallest plan
- Free SSL and custom domains

