Connect your domain

Connect a company domain

Open Boni Panel, switch to the company that owns the domain, and open Domain Management. If it is not installed, use Add modules to request it. An authorized company administrator can use this workflow.

Domain registration and renewal stay with your registrar. Changing nameservers lets Boni manage DNS through Cloudflare for that domain. The Verify domain ownership shortcut in company email setup performs a TXT ownership check; full DNS management uses this Domain Management workflow.

Tell Boni what must keep working

Enter the root domain, such as example.com, and its registrar. Select the current website and mailbox providers, whether to keep or migrate each service, and list other services, custom subdomains, verification records and DKIM selectors. Indicate whether DNSSEC is currently enabled. Confirm the service list and click Save domain details.

Keep existing services unless you have deliberately chosen to replace them. A DNS scan cannot discover every custom record.

Prepare and review DNS

1. In Prepare the replacement zone, paste your current provider's BIND or zone-file export into DNS export (optional but recommended) when available.
2. Click Prepare safely. Boni creates or reuses the domain's Cloudflare zone while the current nameservers remain live.
3. Click Review discovered records. Confirm every record needed by your website, mailbox and other services, including MX, SPF, DKIM, DMARC and verification TXT records.
4. Click Confirm this record review, then Run website and mail safety check.

An export plus your service inventory helps preserve records that a public scan can miss. Resolve missing records or unclear service choices before continuing. The prepared zone keeps the old nameservers and source records as rollback evidence.

Handle old DNSSEC if required

If the safety check asks for DNSSEC handover, turn off the old DNSSEC configuration and remove its DS record at the registrar. Keep the old nameservers while that change propagates, then rerun the safety check. An old DS record can break resolution after a nameserver change. After connection, DNSSEC can be enabled using the new provider's values.

Copy the nameservers to your registrar

After the safety check passes, the Connect your domain card checks the current DNSSEC state and shows the domain's assigned nameservers. Use each Copy button; nameserver values are unique to your domain.

1. Open Nameservers or Custom nameservers at your registrar.
2. Replace the current entries with exactly the values from Boni and save.
3. Keep your existing website and mailbox services.
4. Return to the connection card.

Boni checks every 30 seconds while this screen is visible, for up to 10 minutes. Check connection now starts another check period. You can return later; registrar propagation may take longer. DNSSEC or service-safety problems pause checks and explain the required action.

Domain connected appears when the assigned nameservers resolve, Cloudflare reports the domain active, DNSSEC is safe and the preservation check has passed. After cutover, check your website, HTTPS and mailbox receive/send. The connection badge proves DNS connection; those service checks confirm their own delivery.

Manage future services through Boni

Once connected, authorized Boni workflows can manage the domain's DNS for websites, email and subdomains without another nameserver change. Creating a mailbox or linking it to Bow Chat remains its own company setup action.

Your company Assistant uses the same organization-scoped Domain Management APIs as Panel. It can guide preparation, record review, the safety check and connection verification. It cannot access another company's domain or the DNS provider credential.

API integrations

Authorized integrations use /v1/organizations/:organizationId/domains on https://platform.boni.one for the same company domain records and managed-DNS preparation/review workflow.

• GET /v1/organizations/:organizationId/domains/:domainSetupId/managed-dns/connection reads current connection state without changing DNS or saved setup.
• POST /v1/organizations/:organizationId/domains/:domainSetupId/managed-dns/delegation/verify confirms and saves the current verified connection.

Reads require domains.read; confirmation requires domains.write. Both use the installed domains workspace and that organization's authorized access. A connected response requires nameserver parity, actual provider activation, preservation readiness and safe DNSSEC. Waiting or handover states remain explicit; clients must not infer success from nameservers alone.