1. BWEZE Domains
  2. Blog
  3. Engineering

Engineering · 3 min read

How BWEZE will register .rw domains: EPP, straight to the registry

Most platforms resell domains through another registrar's API. For .rw, BWEZE speaks EPP to RICTA itself. What that means, and where accreditation stands.

When you buy a domain from a hosting platform, the platform usually is not the registrar. It passes your order to a registrar’s HTTP API, and the registrar talks to the registry. For most suffixes BWEZE works that way too, through a provider. For .rw, Rwanda’s own suffix, we are building the shorter path: BWEZE as the registrar, talking to the registry directly.

What EPP is

Registries and registrars speak the Extensible Provisioning Protocol, EPP. A registrar opens a TLS connection to the registry, logs in with its credentials, and sends XML commands against the registry’s objects: domains, contacts and nameserver hosts. The commands are few: check, info, create, update, renew, transfer and delete. Every reply carries a result code, and anything from 2000 up is an error.

EPP is defined in RFC 5730, with mappings for domains (RFC 5731), hosts (RFC 5732) and contacts (RFC 5733), carried over TCP with TLS (RFC 5734). BWEZE has its own EPP client, so nothing sits between the control plane and the registry.

What happens when you buy a .rw name

You never write EPP. You call the same domains API as for any other suffix, and once the direct path is switched on, BWEZE translates:

  1. Check. A search maps to EPP domain:check against the registry.
  2. Contacts. BWEZE makes sure the contacts exist at the registry: you as the registrant and admin contact, and BWEZE as the technical contact, because it runs the nameservers.
  3. Create. The domain is created in your name and delegated to ns1.bweze.com and ns2.bweze.com.
  4. Connect. Because BWEZE runs that DNS, the domain is attached to your project and routed without a manual DNS step.

Renewals and transfers map to domain:renew and domain:transfer the same way. The registrant on record is you, not BWEZE: the domain is yours.

What accreditation involves

RICTA, the not-for-profit that runs .rw, sells names only through accredited registrars, and publishes the list of them: a few dozen in Africa and abroad. Becoming one is open to companies anywhere; RICTA does not require a local presence. An applicant fills in a form, RICTA says it decides within two working days, and an approved registrar pays an advance into a prepaid account at the registry and signs the registry-registrar agreement. For a registrar in Africa the application fee is RWF 100,000 and the yearly membership is RWF 78,625.

The .rw zone itself is signed with DNSSEC at the root, and RICTA runs RDAP and WHOIS services for lookups.

Where it stands

BWEZE is not yet an accredited .rw registrar. The EPP path is built and switched off until three things are done:

  • Accreditation by RICTA, the .rw registry, which issues production credentials.
  • Testing in RICTA’s test environment before any production command is sent.
  • Public nameservers for ns1.bweze.com and ns2.bweze.com on stable addresses.

Until then, availability is checked over RDAP, and a .rw purchase is recorded as requested and completed by hand. The API is the same either way, so code written today keeps working when the direct path is switched on. You pay when you buy, and if the registry refuses the name or we cannot complete it, the full price goes back to your wallet.

Prices for every suffix are on the pricing page, from the same public price list as the rest of BWEZE. For the steps to buy a name or connect one you own, see the domains docs.

Sources

Build the next thing, from Rwanda.

Get started