Myrax docs

Custom domains

A published build can answer on a domain you own. Two moving parts: a DNS record you control, and a certificate the server issues only for hostnames it already knows.

A published build can be served from a domain you own instead of the Myrax address. There are two moving parts: a DNS record you control, and a certificate the server issues for you. Neither involves uploading anything.

The DNS record

Point the domain, or a subdomain, at this server with an A record:

TypeHostValue
Ayourdomain.com or shop for a subdomainThe server address we give you

Use a CNAME only if your DNS provider requires it for a subdomain; an A record to the given address is simpler and avoids a second lookup. Do not proxy the record through a third-party proxy unless you are prepared to configure TLS at that proxy as well, because the certificate is issued to this server, not to the proxy.

What the server checks before it serves

The certificate is issued on demand, and on-demand issuance is a well-known way to let anyone request a certificate for any hostname pointed at your server. So before issuing, the server asks the application whether that hostname belongs to a published build. If it does not, the request is refused and no certificate is created.

That check is why a domain has to be added to the project before DNS is switched, not after.

The order that works

  1. Add the domain on the project and save it.
  2. Create the DNS record at your registrar.
  3. Wait for the record to be visible. This is the step that fails most often: a certificate cannot be issued for a name that does not resolve yet, and the retry is automatic but not instant.
  4. Open the domain. The first request issues the certificate.

When it does not work

SymptomUsual cause
TLS error, no certificateThe name does not resolve to this server yet, or the domain was never saved on the project so issuance was refused.
Myrax landing page instead of your buildThe host is being treated as the app host. The domain is not registered to a published build.
404 at the rootThe domain resolves, but no published build is attached to it.

What a custom domain does not do

  • It does not publish for you. The build must already be published; a domain points at a published build.
  • It does not add mail. This is a web address, not an inbox.
  • It does not remove the Myrax address. Both work; the domain is an extra front door.

Publishing itself is described in Publishing.