Summary

  • A September 1998 RINAF report says .ng was registered in March 1995, that yaba.edu.ng was its only registered domain “by that time,” and that CNUCE in Pisa managed the TLD. The report’s phrasing does not give a precise cutoff for that one-name snapshot.
  • The same account describes transfer procedures to Nigeria Internet Group (NIG) as having started and says NIG secretary-general Lanre Ajayi visited CNUCE to learn the work. IANA’s later record says a 1998 NIG and NITEL redelegation request was not pursued; the formal root-zone changes documented here came in 2004, to NITDA, and 2009, to NiRA.

One name is a small beginning, not a small responsibility. The RINAF evaluation published in September 1998 says that Nigeria’s .NG had been registered at InterNIC in March 1995 and that yaba.edu.ng was the only registered domain “by that time.” It says the CNUCE Institute in Pisa managed the top-level domain, had defined its domain structure and rules, and installed a WHOIS database to help with registrations and provide information about registered domains. The document does not specify exactly when its “by that time” snapshot was taken, so it should not be silently rewritten as an exact March 1995 count or as proof that the namespace remained at one name through September 1998. (RINAF technical-support evaluation, September 1998, pp. 5–7.)

The small register sat inside a larger technical and institutional arrangement. RINAF had begun operating in Nigeria in 1992, first at NACETEM at Obafemi Awolowo University. After problems with power and telephone service, the project moved its main node to Yaba College of Technology in 1993. The 1998 paper says CNUCE made regular dial-up connections for email for three more years. It also says the Nigerian Internet Group emerged after a Yaba College workshop on promoting RINAF. Those details help explain why a local registry was not simply a local machine: the people, connectivity, records and technical assistance occupied different sites.

They do not establish that email relay, Internet access and DNS management were one service.

The handover passage is unusually concrete—and carefully incomplete. The RINAF authors write that procedures had started to transfer TLD management to NIG after a request from the Nigerian government through the NCC. They add that NIG secretary-general Lanre Ajayi spent a week at CNUCE learning the procedures and technical aspects of management. That is evidence of an intended transfer and knowledge exchange. It is not a completion notice. The report gives no effective date, signed acceptance, root-zone change, or account of which duties had already moved.

Because the paper was written by RINAF’s technical-support unit, it is also an institutional account from one participant in the arrangement, not a complete transaction file.

A contemporary email notice reinforces the need to keep systems separate. In July 1995, a public announcement preserved by the Network Startup Resource Center said RINAF’s email link to Lagos had been restored; messages addressed to Yaba accounts had to be collected at the college. That notice speaks to email delivery at that moment. It neither dates .ng’s root-zone delegation nor establishes who held the registry database. (NSRC archive, “E-Mail Sites and Services in Nigeria,” 24 July 1995.)

IANA’s 2004 report supplies a different kind of ledger. It says Jon Postel established .ng on 15 March 1995, with Iyabo Odusote of Yaba College of Technology as administrative contact and Abraham Gebrehewit of IAT in Pisa as technical contact. In March 1998, IANA received expressions of interest in redelegation from both NITEL and NIG. The requests were not pursued, and ICANN took no action; the older records were no longer available to its staff. The evidence therefore does not let us treat the training visit reported by RINAF as a completed IANA transfer to NIG. Nor does it tell us why the 1998 expressions of interest stopped. (IANA, “Report on Redelegation of the .ng Top-Level Domain,” 10 June 2004.)

The later root-zone sequence is clearer. In 2003 the Nigerian government endorsed NITDA as the appropriate delegee; after agreements were reached, IANA concluded in June 2004 that .ng should be redelegated to NITDA. In 2009, a new request proposed Nigeria Internet Registration Association (NiRA) as sponsoring organization. IANA’s report says the initial technical operations had been performed by IAT in Italy and later by Randy Bush, while summarizing the 2004 NITDA transfer and evaluating NiRA’s capacity. NiRA’s own history says the association was founded in March 2005 and that NITDA coordinated the transfer on the federal government’s behalf. These are two later institutional changes, not proof that NIG never handled any operational task. (IANA 2004 report; IANA 2009 report; NiRA history.)

The distinctions matter because “the registry” can refer to several things: the database that accepts names, the DNS servers that publish a zone, the contact in the root-zone record, or the organization accountable for the country-code domain. RFC 1591 described the designated country-code manager as performing a public service and as a trustee for the Internet community, not an owner. That framework helps frame the succession question but does not resolve Nigeria’s particular division of labor. (RFC 1591, March 1994.)

Heng Lu’s Note 70 offers a present-day lens: the naming function can outlast a particular gatekeeper, but continuity is not automatic merely because a new institution is named. The Nigerian evidence makes that distinction tangible. A 1998 report records a transfer being prepared through procedures and training; the 2004 and 2009 IANA reports record later root-zone redelegations. A registry’s continuity depends on carrying forward the records, rules, technical knowledge and authority that let names remain usable. The sources establish the sequence, but they do not show every operational step between the visits and the later formal changes.

Sources and limits

The 1998 RINAF paper’s one-domain phrase has an imprecise time reference and reflects the perspective of the Pisa technical-support unit. IANA’s 2004 report says the 1998 requests were not pursued and that earlier files were unavailable; neither it nor the RINAF paper explains why. This article distinguishes root-zone delegation, registry management, DNS operation, WHOIS, email relay and general connectivity, and makes no claim of a .ng outage or of a completed NIG handover in 1995–98.