Boni
Boni
Browse documentation
Boni Platform·guide·Version 4

Connect your domain

Use the guided Panel setup to preserve your website and email, review existing DNS records, and receive the exact nameservers to connect.

Start in Boni

  1. Sign in at panel.boni.one.
  2. Switch to the company workspace that owns the domain.
  3. Open Email CPaaS in the left navigation.
  4. Open Setup & Health.
  5. In Connect your domain once, start with What already uses this domain?

The setup starts blank. Enter the real current state; Boni does not guess or prefill it.

What to enter

Field in PanelWhat to enter
DomainThe root domain, such as example.com—not www.example.com
RegistrarThe company where the domain is registered and renewed
Current websiteThe current website host or platform; choose No website if there is none
Website planUsually Keep the current website unless you deliberately want to move it
Current mailbox providerGoogle Workspace, Microsoft 365, another provider, or no mailbox
Mailbox planUsually Keep the current mailbox unless you deliberately want to migrate it
Other connected servicesOne per line: helpdesk, forms, marketing tools, verification records, VPN, DKIM selectors, and custom subdomains
DNSSECSelect this only when DNSSEC is currently enabled at the registrar or DNS provider

Confirm that you have listed the services that must keep working, then click Save domain details.

Where to provide the current email and DNS records

After saving, the same page opens Prepare the replacement zone. In DNS export (optional but recommended), paste the BIND or zone-file export from the current DNS provider. Most providers place this under DNS, Manage zone, or Export zone file. The export includes website records and email records such as MX, SPF, DKIM, DMARC, verification TXT, and mail-related CNAME records.

You normally do not need to retype every email record. Boni combines the export with a public DNS scan. Then:

  1. Click Prepare safely. Your current nameservers remain live.
  2. Click Review discovered records.
  3. Check the MX, TXT, CNAME, A, AAAA, and other records shown. Keep every record used by a service that should continue.
  4. Click Confirm this record review.
  5. Click Run website and mail safety check.

If you do not have an export, continue with the public scan but list every non-obvious service and DKIM selector in Other connected services. An automatic scan can miss uncommon records. Do not continue until every current mail and website record appears in the review. An authorized workspace Assistant can use the same organization-scoped Email API to add a confirmed missing record before the safety check.

Where Boni shows the exact nameservers

Nameservers are unique to the prepared domain, so they are never copied from this public guide. After the website and mail safety check passes, the same Setup & Health page shows a green Ready to connect card directly below the preparation section. That card displays the exact nameservers, one per box.

If the green card is not visible, Boni has not finished proving that the current website and email will survive. Complete the unfinished step above it; do not change nameservers yet.

Make the one registrar change

When the green card is visible:

  1. Open the registrar account where the domain is registered.
  2. Find Nameservers, Custom nameservers, or Use my own nameservers.
  3. Replace the current nameservers with exactly the values in the Boni card.
  4. Save the change. Do not cancel the website or mailbox and do not recreate DNS records at the registrar.
  5. Return to the same Boni card and click I changed them — check connection.

Boni watches propagation and verifies the website, HTTPS, and email records. After the domain is connected, future subdomains and email sender records can be managed through Boni without another registrar round trip.

Let your Assistant guide the setup

In the company workspace, you can ask: Help me connect example.com while keeping the current website and mailbox. Tell me exactly what information is still missing.

The Assistant uses the same tenant-scoped setup and DNS APIs as the Panel. It can prepare and review the zone, add a confirmed missing record, run the safety check, and verify the connection; it cannot access another organization's domain or DNS credentials.