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

# Connecting to a site

> Point a domain at your server: A record or NS change

Lumi domains are already on Cloudflare, so DNS is managed right in the bot. There are two ways to connect a domain to a server or an external service.

* **A record** — a direct binding of the domain to your server's IP. DNS stays on Lumi's Cloudflare. This is what you want almost every time.
* **NS change** — hand the whole domain over to another service that runs its own DNS.

<Tabs>
  <Tab title="A record (recommended)">
    A direct connection to your own server's IP, with DNS staying at Lumi.

    <Steps>
      <Step title="Find your server's IP">
        The bot shows your VPS IP on the server card in [@lumivps\_bot](https://t.me/lumivps_bot).
      </Step>

      <Step title="Open DNS">
        [@lumibp\_bot](https://t.me/lumibp_bot) → **My Domains** → domain → **DNS settings** → **Add record** → **A** → paste the IP.
      </Step>

      <Step title="Set the name">
        * **Root** (`example.com`) — leave the subdomain field empty.
        * **Subdomain** — the name only (`blog`, not `blog.example.com`).
      </Step>
    </Steps>

    <Tip>
      No SSL on your server? Leave the Cloudflare proxy (orange cloud) on — otherwise HTTPS will throw an error because there's no certificate.
    </Tip>
  </Tab>

  <Tab title="NS change">
    For when a service or host requires delegation and runs DNS itself.

    <Steps>
      <Step title="Copy the NS">
        In the service, find the domain-connection section and copy the two NS.
      </Step>

      <Step title="Open the bot">
        [@lumibp\_bot](https://t.me/lumibp_bot) → **My Domains** → domain → **Change NS**.
      </Step>

      <Step title="Enter the NS">
        Paste both NS separated by a space, then confirm.
      </Step>

      <Step title="Wait">
        Up to 1 hour, in rare cases up to 24. **After changing the NS, Lumi's [Cloudflare](/en/domains/cloudflare) (SSL, DDoS, redirects) stops working on the domain** — the new service runs DNS now.
      </Step>
    </Steps>

    <Warning>
      If **DNSSEC** is enabled on the domain, turn it off at your current DNS provider first (delete the DS records) and wait out the TTL. Changing the NS with DNSSEC still active breaks resolution, and the domain stops opening entirely.
    </Warning>
  </Tab>
</Tabs>

## Managing records in the bot

Under **DNS settings** you add and delete records of types **A, CNAME, AAAA, MX, TXT, SRV** — for a site, subdomains, email, and ownership checks. The **Change NS** button sets your own nameservers.

<Note>
  If the domain's NS aren't on Cloudflare, the first time you touch DNS, redirects, or [Cloudflare settings](/en/domains/cloudflare) the bot offers to move the NS back to Cloudflare for you.
</Note>

## Next

<CardGroup cols={2}>
  <Card title="DNS records" icon="list" href="/en/domains/dns">
    A, CNAME, MX, TXT, and TTL values.
  </Card>

  <Card title="Connect to your server" icon="terminal" href="/en/vps/connect">
    SSH or RDP into your VPS.
  </Card>

  <Card title="Set up a site on your server" icon="server" href="/en/vps/webserver">
    Nginx, PHP, and HTTPS.
  </Card>

  <Card title="When it goes live" icon="clock" href="/en/domains/propagation">
    DNS propagation times and how to check.
  </Card>
</CardGroup>