> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://docs.flyinghost.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Connect your domain to FlyingHost

Connect a custom domain to your live WordPress site from FlyingHost Cockpit. If you’re migrating an existing site, test it on the temporary FlyingHost address and agree on the DNS switch with your migration team before updating the live domain.

## Start in Cockpit

1. Open your live site in Cockpit and go to **Domains**.
2. Select **Connect domain** and enter the hostname you want to use, such as `example.test` or `blog.example.test`.
3. Follow the guided DNS setup. If you manage DNS manually, use the records shown for your domain and add them at your DNS provider.

![Domains tab with the Connect domain button](https://storage.crisp.chat/users/helpdesk/website/-/3/5/a/3/35a3c3ffe31dc000/domains-tab_15u4qix.png)

![Connect a domain dialog filled with an example hostname](https://storage.crisp.chat/users/helpdesk/website/-/3/5/a/3/35a3c3ffe31dc000/connect-a-domain_131jd1d.png)

## Update DNS manually

Use the exact record types, names, and targets provided during setup. They depend on the hostname and DNS provider.

- For a root domain such as `example.test`, check the records for both the root domain and `www`. For a subdomain such as `blog.example.test`, use the records for that subdomain.
- Add the certificate validation CNAME exactly as shown. On Cloudflare, keep the `_acme-challenge` record **DNS only**.
- Replace any old website records that conflict with the new ones. Leave email records such as MX, SPF, DKIM, and DMARC in place.
- If you use your own Cloudflare account and want to keep its proxy enabled, follow the [Cloudflare Orange-to-Orange guide](https://docs.flyinghost.com/en/article/use-your-own-cloudflare-account-with-flyinghost-1nfkfik/) for the proxied website CNAMEs.

## Check the connection

Allow time for the DNS changes to take effect. Open the new domain over HTTPS in a private browser window. For a root domain, check both the root and `www`. If the old site still loads or HTTPS shows a certificate error, compare the website and certificate validation records against the setup instructions. If the issue persists, contact FlyingHost support with the domain and what you see.

If FlyingHost is handling your migration, you can choose **Invite FlyingHost to DNS** in the migration request and invite `migrations@flyinghost.com` with DNS edit access. You can also choose to connect the domain yourself after the migration.