Docs / Registrar guide — creating ns1/ns2 (the one-time step)

Registrar guide — creating ns1/ns2 (the one-time step)

This is the click path for the one thing you must do at your domain registrar (see Point your domain): register two hosts ns1.yourdomain and ns2.yourdomain pointing at your server IP, then set the domain's nameservers to them.

Your panel shows the exact values to type: Dashboard → Server SetupDomain nameserversShow the registrar steps (with Copy buttons). The IP there is the one to use everywhere below.

Order matters, everywhere: (1) register ns1/ns2 + IP first → (2) wait a few minutes → (3) then switch the domain's nameservers to ns1/ns2. Doing (3) before (1) breaks resolution.

Same IP for both? Yes — you need two names, not two servers. Hostinger states this explicitly; Rumahweb and Exabytes show it in their own examples; Namecheap allows it for common TLDs (.com/.net/.id …) but a few TLDs require distinct IPs (.ca, .blog, .nl, .cn, .eco, .kiwi). If a form rejects a duplicate IP, ask the registrar's support — it's a TLD rule, not a Nimbopanel limit.

Menu names below are quoted from each registrar's own help articles (linked). Registrars redesign their panels; if a label differs, search their help for "child nameserver" / "private nameserver" / "glue record".

Rumahweb (Clientzone, Bahasa Indonesia)

  1. Buat nameserver: Clientzone → DomainManage pada domain → Private NameserverAdd NewNameserver: ns1 (awalan saja), IP Address: IP server → Save Changes. Ulangi untuk ns2.
  2. Ganti nameserver domain: DomainsManageSettingNameserver Setting → isi ns1.domainanda & ns2.domainandaChanges Nameserver.
  3. Rumahweb's own walkthrough registers ns1/ns2 on one IP — fine. Propagation 1–2 h (nameserver anak), 1–24 h (ganti nameserver). Rumahweb has a newer "new.clientzone" UI; wording may differ slightly.

Niagahoster → Hostinger Indonesia (hPanel, Bahasa Indonesia tersedia)

Niagahoster is now Hostinger; use hPanel.

  1. Buat child nameserver: hPanel → Domain → pilih domain → DNS / Nameserver → bagian Child nameserversNama: ns1, IP: IP server → Simpan. Ulangi ns2.
  2. Ganti nameserver: Domain → domain → DNS / Nameserver → pilih Ganti nameserver (bukan "Gunakan nameserver Hostinger") → isi ns1.domainanda, ns2.domainandaSimpan.
  3. Hostinger: "You can use the same IP for several child nameservers." Max 4 child NS; some TLDs don't support child NS. Propagation up to 24 h.

IDwebhost (Member Area my.idwebhost.com)

  1. Buat nameserver: Member Area → Domain → klik domain → Private Nameservers → isi nama nameserver + IP VPS. Lakukan dua kali (ns1, ns2).
  2. Ganti nameserver: Domain → domain → Name Server → isi NS baru → Ubah Nameserver.
  3. Propagation "maksimal 1×24 jam". IDwebhost's articles don't state whether ns1/ns2 may share an IP (usually accepted — ask support if the form refuses).

DomaiNesia (MyDomaiNesia, label bahasa Inggris)

  1. Buat nameserver: MyDomaiNesia → Domains → klik domain → Private NameserversRegister a Nameserver: nama + IP → Save Changes. Ulangi ns2.
  2. Ganti nameserver: Domains → domain → tab NameserverUse Custom Nameservers → isi → Change Nameservers.
  3. Propagation 12–48 h. Their guides are older (2016); confirm labels in the panel.

Exabytes Indonesia (Customer Area; help tersedia dalam Bahasa Indonesia)

  1. Buat nameserver: Customer Area → My DomainsManage Domain → panel kiri Private NameserversRegister a NameServer Name: ns1 + IP → Save Changes. Ulangi ns2.
  2. Ganti nameserver: DomainsMy Domains → domain → ikon obeng → ManageName Servers → isi → simpan.
  3. Exabytes' own example uses one IP for two NS — fine. Glue takes effect in 6–48 h; NS change 2–4 h. If registration errors, open a ticket to the Domain department with the NS + IP.

Namecheap

  1. Create: Domain ListManageAdvanced DNSPersonal DNS ServerAdd NameserverNameserver: ns1, IP address: server IP. Repeat ns2.
  2. Switch: Domain ListManageNameservers dropdown → Custom DNS → enter ns1.yourdomain, ns2.yourdomain → click the green ✓.
  3. Registering personal nameservers does not point the domain at them — do step 2 separately. Same IP OK for common TLDs; a few (.ca, .blog, .kiwi, .eco, .cn, .nl) require distinct IPs.

GoDaddy

  1. Create: Domain Portfolio → domain → DNSHostnamesAdd HostnameHostname: ns1, IPv4: server IP → Save. Repeat ns2. Ready within ~90 min (GoDaddy emails you).
  2. Switch: DNSNameserversChange NameserversI'll use my own nameservers → enter → SaveContinue.

Cloudflare Registrar — this approach does NOT apply

Domains registered at Cloudflare are locked to Cloudflare's nameservers; there is no child-NS / glue screen and you cannot point the domain at your own server's nameservers. For such a domain, keep DNS at Cloudflare and simply add A records (@, www, panel, mail, ns1, ns2 → your server IP, all DNS only / grey cloud) — see Alternative B in Point your domain. Resellers' white-label nameservers won't be possible on a Cloudflare-registered domain; transfer it to a registrar that allows custom nameservers if you need that.

After you've saved

Go back to the panel → Dashboard → Server SetupRecheck. It checks from the public internet and turns green when the world sees ns1/ns2. Panel HTTPS then switches on by itself.