DNS Configuration
In general you need an A record for all the domains or subdomains you want to use, pointing to the IP address of your server where you would like to deploy your application.
Note that you can use the same IP address for multiple domains and subdomains.
In the examples, 1.1.1.1 is your server's IP address.
If your domain contains special or non-ASCII characters (for example å, ä, ö, é, etc.), you must use the punycode version of the domain when configuring DNS or entering the FQDN.
For example: münchen.example.com → xn--mnchen-3ya.example.com
Single Domain
Let's say you want to deploy your resource to example.com with the IP address 1.1.1.1.
- You need to set an
Arecord forexample.compointing to1.1.1.1.
You can also add www.example.com as an A record and redirect it inside the platform with the chosen reverse proxy.
Then you can use https://example.com as a FQDN (Fully Qualified Domain Name) for any of your resources, even for your Corelix instance.
Wildcard Domains
Let's say you want to deploy your resource to *.example.com with the IP address 1.1.1.1.
- You need to set an
Arecord for*.example.compointing to1.1.1.1.
This allows you to use any subdomain of example.com as a FQDN for any of your resources.
For example, you can use https://app.example.com or https://api.example.com as a FQDN.
Autogenerated Domains
If you set a wildcard domain in your DNS settings, you can also use the platform to autogenerate domains for your resources.
Go to the Server settings and set the Wildcard Domain field to your domain, for example https://example.com.
Then if you create a new resource:
- You will get a random subdomain for your application, for example
https://random.example.com. - Also for your Preview Deployments, for example
https://<PRId>.random.example.com.
The Preview URL template can be modified in the application's page under the Preview Deployments tab.
Instance Domain
If you self-host, you can set a custom domain for your instance in the /settings page.