# Connect a domain

Add a domain, preserve important DNS records, connect nameservers and attach addresses to applications.

## Before you start

Prepare the domain without interrupting services that already use it.

- Access to the registrar account where the domain nameservers are changed.

- A list or export of current DNS records, especially mail, verification and third-party service records.

- The application addresses that should use the root domain or subdomains.

- Time for DNS changes to propagate; different networks can see the change at different times.

Add and manage root domains from the active workspace.
- [Open Domains](/dashboard/domains) — Add a domain or review an existing one.
- [Open Applications](/dashboard/applications) — Connect verified domains to an application.

## 1. Add the root domain

1. Open Domains and select Add Domain.
2. Enter the root domain without https, a path or a port.
3. Complete ownership verification when the platform requires it. A verified root domain cannot be claimed by another workspace.
4. Open the domain drawer and review its current connection status.

## 2. Preserve and review DNS records

Run Scan DNS before changing nameservers, or import a standard zone file. Review every detected record. Website records can be pointed to Ghost Deploy; mail, verification and deliberately external services should normally keep their current values.

> **warning:** Do not replace MX, SPF, DKIM, DMARC or provider-verification records unless you intend to move or reconfigure those services. DNS changes can interrupt email even when the website continues working.

## 3. Change nameservers and verify the connection

1. Copy the two Ghost Deploy nameservers shown in the Nameservers tab.
2. Replace the registrar nameservers with those values. Do not add them as ordinary NS records at the old DNS provider.
3. Return to Ghost Deploy and select Check Nameservers.
4. Wait until the domain shows connected. Cached resolvers may take longer even after authoritative DNS is correct.
5. Connect the root domain, a subdomain or a wildcard address from the application's Domains section.

> **success:** A domain is ready when nameserver delegation is connected, the intended application record resolves correctly and HTTPS opens without a certificate warning.

## If something does not work

- Nameservers remain pending: verify the change at the registrar, not inside the old DNS zone, and check for registrar-specific glue requirements.

- A record or CNAME conflicts: one hostname cannot use CNAME alongside other record types. Keep the intended record and remove only the conflicting duplicate after review.

- Website works on one network only: allow resolver caches to expire and compare authoritative results before making more changes.

- HTTPS is pending: confirm the hostname resolves to Ghost Deploy first, then retry after certificate issuance.

- A subdomain is already used: detach it from the existing application before assigning it elsewhere.

## Related guides and references

- [Open DNS Records](/dashboard/domains) — Select a domain and open DNS Records to scan, import or edit records.

- [Deploy your first application](/docs/getting-started/deploy-your-first-application) — Create the application that will receive domain traffic.

- [ICANN nameserver overview](https://www.icann.org/resources/pages/dns-2012-02-25-en) — Background on DNS and nameserver delegation.

Source: https://ghostdeploy.com/docs/domains/connect-a-domain