Point the DNS at the server
One wildcard DNS record sends each app hostname to your server.
The browser asks the DNS for the address of hello.apps.example.com.
Create the records
Create a wildcard DNS record for the apps at your DNS provider. Add one record for each custom domain.
| Record | Type | Value |
|---|---|---|
*.apps.example.com | A (and AAAA for IPv6) | the IP address of the server |
shop.example.com (a custom domain) | A, or CNAME to a name that resolves to the server | the server |
What you get
Each web service and each static site gets <name>.apps.example.com. The dashboard can use ferry.apps.example.com.
Ferry asks for one certificate for each hostname through the HTTP-01 challenge. Thus the wildcard record is all the DNS that Ferry needs. You need no DNS API and no wildcard certificate.
You can leave --base-domain out. When the server runs, connect the domain from the dashboard. Ferry shows the record to create, with the address of the server. Ferry tells you when the DNS reaches the server. You add more domains the same way.
In that case, add --dashboard-host none, or a hostname of your own. The cause: a server with the default base domain also answers its dashboard on the public proxy at ferry.localhost.