mirror of
https://github.com/coollabsio/coolify-docs.git
synced 2026-06-19 07:35:55 +00:00
Andras Bacsai
a64450ae9d
Replace VitePress/Vue stack with Fumadocs MDX, TanStack Start, React 19, and Vite. Migrate all documentation content to MDX under content/docs/. Add full src/ app with React components, routing, search, and API page. Remove Korrektly integration from CI/CD workflows, Dockerfile, and env vars. Update build pipeline to output to .output/public instead of docs/.vitepress/dist.
74 lines
2.6 KiB
Plaintext
74 lines
2.6 KiB
Plaintext
---
|
|
title: "DNS Configuration"
|
|
description: "Configure A records, wildcard domains, and autogenerated subdomains for Coolify applications with DNS setup examples and preview deployments."
|
|
---
|
|
|
|
|
|
# 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.**
|
|
|
|
|
|
<Callout type="info" title="Note">
|
|
|
|
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 in Coolify.
|
|
|
|
For example:
|
|
- `münchen.example.com` → `xn--mnchen-3ya.example.com`
|
|
|
|
Most DNS providers automatically convert these domains, but if you experience issues you should manually use the punycode representation.
|
|
|
|
</Callout>
|
|
|
|
|
|
## Single Domain
|
|
|
|
Let's say you want deploy your resource to `example.com` with the IP address `1.1.1.1`.
|
|
|
|
- You need to set an `A` record for `example.com` pointing to `1.1.1.1`.
|
|
|
|
|
|
<Callout type="success" title="Tip">
|
|
|
|
You can also add `www.example.com` as an `A` record and redirect it inside Coolify with the chosen reverse proxy.
|
|
|
|
</Callout>
|
|
|
|
|
|
Then you can use `https://example.com` as a FQDN (Fully Qualified Domain Name) for any of your resources, even for your Coolify instance.
|
|
|
|
## Wildcard Domains
|
|
|
|
Let's say you want deploy your resource to `*.example.com` with the IP address `1.1.1.1`.
|
|
|
|
- You need to set an `A` record for `*.example.com` pointing to `1.1.1.1`.
|
|
|
|
This allows you to use any subdomain of `example.com` as a FQDN (Fully Qualified Domain Name) for any of your resources, even for your Coolify instance.
|
|
|
|
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 Coolify to autogenerate domains for your resources.
|
|
You just need to 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`.
|
|
|
|
|
|
<Callout type="success" title="Tip">
|
|
|
|
The Preview URL template could be modified in the application's page / `Preview Deployments` tab.
|
|
|
|
</Callout>
|
|
|
|
|
|
## Instance Domain
|
|
|
|
If you self-host Coolify, you can set your Coolify instance a custom domain in the `/settings` page.
|