> ## Documentation Index
> Fetch the complete documentation index at: https://docs.landerlab.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect a Domain with Manual DNS

> Connect a domain to LanderLab with Manual DNS. Add the DNS record LanderLab shows you at your provider, verify it, and publish landing pages on your own domain.

Use **Manual DNS** when your domain is managed outside Cloudflare, or when you prefer to keep DNS at your current provider.

With this method, you add the record LanderLab shows you at your domain provider, then verify it inside LanderLab. When your domain is not in Cloudflare, LanderLab detects your provider and selects Manual DNS for you automatically.

## Before you start

Make sure the following are true:

* You can access your **domain DNS settings** (GoDaddy, Namecheap, and similar).
* You are an **admin** in LanderLab.
* You are using a **subdomain**, such as `lp.yourdomain.com`. Manual DNS usually requires a subdomain rather than the root domain.

## Connect your domain

<Steps>
  <Step title="Open Domains and add a domain">
    Open **Settings**, then **Domains**, and click **Add Domain** in the top-right corner. Enter the subdomain you want to use, for example `lp.yourdomain.com`.
  </Step>

  <Step title="Confirm Manual DNS">
    When the domain is not in Cloudflare, LanderLab activates **Manual DNS** and shows the provider it detected. Keep Manual DNS selected.
  </Step>

  <Step title="Choose which workspace can use it">
    Set who can publish to this domain:

    * **All Workspaces** lets any workspace publish to the domain, including workspaces you create later.
    * **Specific Workspace** limits publishing to one workspace.
  </Step>

  <Step title="Add the domain">
    Click **Add Domain**. LanderLab opens the verification window and shows the exact DNS record you need to add.
  </Step>
</Steps>

## Add the DNS record at your provider

1. Log in to your **domain provider dashboard**.
2. Open **DNS Management** or the **Zone Editor**.
3. Create the record exactly as shown in LanderLab. Match the **Type**, the **Host or Name**, and the **Value or Target**.

Tips:

* Do not include `https://` in the value.
* If a record already exists with the same host, edit or remove it to avoid conflicts.

## Verify and finish

<Steps>
  <Step title="Verify the record">
    Return to the verification window in LanderLab and click **Refresh**. If the record is correct and DNS has started to propagate, verification continues.
  </Step>

  <Step title="Add any additional record if prompted">
    If LanderLab asks for another record, such as an SSL record to enable HTTPS, add it the same way, then click **Refresh** again.
  </Step>

  <Step title="Confirm the domain is active">
    Go to **Settings**, then **Domains**, and click the **Refresh** icon. When the status shows **Active**, your domain is ready for publishing.
  </Step>
</Steps>

## Root domain notes

Some providers do not allow the required record on a root domain. Because of this, Manual DNS usually works best with a subdomain such as:

```text theme={null}
lp.yourdomain.com
www.yourdomain.com
```

If you need to use the root domain (`yourdomain.com`), connect through [Cloudflare](/features/domain/connect-domain-cloudflare) instead, or point a subdomain like `www` to your landing pages and redirect the root domain to it.

## Common issues

<AccordionGroup>
  <Accordion title="Domain still shows Pending">
    DNS propagation can take a few minutes, and up to 24 to 48 hours depending on your provider. Click **Refresh** to check again.
  </Accordion>

  <Accordion title="The host format looks different at my provider">
    Some providers expect just the subdomain (`lp`), while others expect the full host (`lp.yourdomain.com`). Follow your provider's format, but make sure the intent matches what LanderLab shows.
  </Accordion>

  <Accordion title="My provider does not allow the record on the root domain">
    Use a subdomain, or connect through [Cloudflare](/features/domain/cloudflare/connect-domain), which supports root domains.
  </Accordion>
</AccordionGroup>