▸itoka
How it worksAPISign in
DNS hosting for Nigerian developers

Point your domain.
It's live in seconds.

Itoka hosts DNS for .ng and .com.ng domains on our own nameservers. Record changes reach both servers in seconds, mistakes are caught before they're saved, and there's no panel to fight with.

Sign inSee how it works

Sign-up isn't open yet: we're running our own domains on Itoka first. Pricing will be in Naira, with no upsells.

How it works

Two steps, then Itoka takes over

  1. 1

    Add your domain

    Itoka creates the zone with NS records for both nameservers and copies it to the second server right away. You can add records before anything changes at your registrar.

  2. 2

    Point your nameservers here

    At your registrar, replace every existing nameserver with these two:

    Primaryns1.itoka.ng
    Secondaryns2.itoka.ng

    Set both. With only one, about half of all lookups fail once the change propagates.

  3. See it go live

    Itoka checks the registry and the .ng zone itself, separately, and shows each one's nameservers. When delegation goes live you'll see it on the zone, no refreshing needed.

What you get

The DNS editor we wanted for our own domains

▸ Live in seconds

Every save is pushed to both nameservers straight away, and Itoka waits until ns2 is serving it before saying so. The confirmation shows the real time it took.

▸ Errors that explain themselves

A CNAME at the apex, an MX pointing at an IP, a TXT value too long for one string: Itoka says what's wrong, why, and how to fix it, while you type.

▸ One-click presets

Google Workspace, Zoho Mail, Vercel, Coolify and SendByte. Anything that clashes with records already in the zone is flagged first, and SPF records are merged instead of overwritten.

▸ Delegation you can watch

After you change nameservers at your registrar, Itoka checks the registry and the .ng zone separately and tells you the moment delegation goes live, or what to fix if only one nameserver made it.

▸ Scoped API keys

Keys limited to the zones and permissions they need, including keys that can only write _acme-challenge records for certificate renewals. Each key is shown once and stored as a hash.

▸ An audit log for every change

Who changed what and when, with the record before and after, whether it came from a person, an API key, a preset or Itoka itself.

API

Everything in the dashboard is an API call

Create zones, edit records and apply presets from your deploy scripts. Changes made with a key are attributed to it in the audit log.

curl https://api.itoka.ng/api/v1/zones/ojaara.ng/records \
  -H "Authorization: Bearer itk_live_…" \
  -H "Content-Type: application/json" \
  -d '{"record": {"type": "A", "name": "www", "value": "159.195.40.229"}}'
▸

Itoka is Yoruba for pointer. DNS records are pointers.

Sign in