Guide
Connect your own domain to your AI-built website
Which DNS records to set, why the check can fail and when HTTPS kicks in. For sites your agent has built.
Your agent has built the site and you like the preview. To make it reachable at your own address, you still need a few records at your domain provider. This is the one step you do yourself: you connect a domain in the VORREN dashboard, not through the agent.
What you need
- A domain with a provider of your choice, for example
studio-example.com. VORREN doesn't sell domains. - Access to the DNS settings of that domain at the provider.
- A project on VORREN with a preview you want to publish. To go live you need slots; each website costs €9 a month while it's live (Pricing).
Step 1: Enter the domain in the dashboard
In the dashboard, open Domains, pick the project and enter your domain. It doesn't matter whether you write studio-example.com or www.studio-example.com: VORREN always connects a main domain together with www. A subdomain like shop.studio-example.com works too, and then only exactly that one.
The dashboard then shows a list of records to create at your provider.
Step 2: Set the records at your provider
For a main domain, there are three kinds of records:
- TXT under
_vorrenwith a value that starts withvorren-verify=. This shows that the domain is yours. - A record for the domain itself (usually written as
@at the provider) pointing to the address the dashboard shows. - CNAME for
wwwpointing toconnect.vorren.io.
For a subdomain, a CNAME to connect.vorren.io replaces the A record. You usually don't have to create the subdomain at your provider first: the CNAME record creates it along the way. The dashboard shows each name the way providers' forms expect it, so @, www or _vorren instead of the full name. If it recognizes your provider, such as IONOS, STRATO, united-domains, Cloudflare or GoDaddy, it links to that provider's instructions.
If your domain still has a parking page from the provider, remove its records. Otherwise the domain points to two targets and the check fails.
Step 3: Have it checked
While the Domains page is open, the dashboard checks on its own every 30 seconds, and you can click Check at any time. VORREN asks your domain's name servers directly, not a cache. How quickly new records arrive there depends on the provider.
The most common reasons it doesn't work yet:
- Record missing or doubled: Some forms append the domain themselves. If you enter
_vorren.studio-example.com, you end up with_vorren.studio-example.com.studio-example.com. Enter only_vorren; the dashboard detects the case and tells you. - Extra address: The domain points to VORREN and somewhere else too, usually a parking page.
- Cloudflare with proxy: If your domain is with Cloudflare, turn off the proxy for the records (gray cloud instead of orange).
- CAA record: If you've specified who may issue certificates for your domain,
letsencrypt.orghas to be on the list.
Step 4: Go live
As soon as the check has passed, tell your agent: "Publish the site." If going live costs something, you confirm it once in the dashboard the first time. VORREN gets the HTTPS certificate itself when you go live; you don't have to deal with it. Anyone who opens studio-example.com ends up on www.studio-example.com.
If the site was already live and you connect another domain, VORREN adds it on its own after the check.
Frequently asked questions
Can my agent connect the domain? No. Connecting and disconnecting domains only works in the dashboard. But your agent can see which domains are connected and can tell you where things are stuck.
What happens if I change a record later? A checked domain stays connected; the dashboard shows a warning until the records are correct again.
Can I take over a domain from another account? Yes, if you set its verification record and the other account's is missing. If the other account's record is still there, the domain stays with that account.