Point your domain (DNS) — one step, then it's automatic

Nimbopanel runs on your server and includes its own DNS server (authoritative, like cPanel/WHM's). That means you do not need Cloudflare, or any third-party DNS service, and you never have to create records by hand: the panel publishes panel., mail., www., every subdomain, email records (MX/SPF/DKIM/DMARC), add-on domains, and your resellers' customer domains automatically.

There is exactly one thing only you can do, because only you have the login to where your domain was bought: tell the domain that your server is its nameserver. Every hosting panel in the world — cPanel included — needs this same single step. It takes about five minutes, once.

The one-time step (do this at your domain registrar)

Your registrar is the company you bought the domain from (Rumahweb, Niagahoster, IDwebhost, DomaiNesia, Exabytes, Namecheap, GoDaddy, …). Log in there and:

1. Open the domain's settings.

2. Find "Child nameservers", "Glue records", "Private nameservers" or "Register nameserver" (the name differs per registrar — see the per-registrar guide below) and create two hosts, both pointing at your server's IP:

   Host	IP
   ns1.yourdomain.com	your server IP
   ns2.yourdomain.com	your server IP

   (Yes — the same IP for both is fine. Registrars require two names, not two servers.)

3. Then set the domain's Nameservers to ns1.yourdomain.com and ns2.yourdomain.com, replacing whatever is there.

4. Save. Done — forever. From now on the panel serves every record itself.

Your panel shows you exactly what to type. Open the Dashboard → Server Setup card. It detects how your domain is pointed right now (as seen from the public internet), shows the two ns1/ns2 hosts + IP with Copy buttons, and turns green once the internet sees the change. Press Recheck after you save at the registrar.

Propagation takes minutes to a few hours (nameserver changes are the slowest kind). HTTPS for the panel switches on by itself once panel.yourdomain.com resolves.

Per-registrar guide

The click paths for the popular registrars (Indonesian first) are in Registrar guide: creating ns1/ns2. If yours isn't listed, search its help for "child nameserver" or "glue record" — every registrar has it.

The two alternatives (only if you can't or don't want to use own nameservers)

Alternative A — keep DNS at your registrar. If your registrar has a "DNS management" / "Zone editor", you can leave the nameservers as they are and create the records there by hand instead: panel, ns1, ns2, mail, www, @ → all A records to your server IP. Downside: every new subdomain, email record, add-on domain and reseller customer must be added there manually — the panel can't do it for you.

Alternative B — Cloudflare (free). A reliable DNS host, useful if your registrar's DNS is flaky. Add the same A records there, and set panel, ns1, ns2, mail to DNS only (grey cloud), never proxied (orange) — proxying breaks HTTPS issuance, authoritative DNS and mail. Same downside as A: records are manual.

For a hosting business, the own-nameservers path above is the right one: it's what lets resellers get white-label nameservers (ns1.reseller-brand.com) and what makes new domains work with zero clicks.

The pitfall to know about

"I set the nameservers but nothing resolves." Usually the domain is delegated to a DNS host that isn't actually serving the zone (the registrar points at a nameserver that answers "REFUSED"). The Server Setup card will show this as "no working nameservers". Fix: complete the own-nameserver step above (our server always answers for its zones), or activate DNS at that host.

Verify it worked

• Dashboard → Server Setup → Recheck: green = the public internet sees your records.
• Or open dnschecker.org → type NS → enter yourdomain.com: it should list ns1.yourdomain.com / ns2.yourdomain.com.

Next: Email deliverability & sending — most VPS providers block outbound port 25, so set up a relay so your customers' mail is delivered.