Summary

  • Sri Lanka’s Sinhala .ලංකා and Tamil .இலங்கை domains reached the DNS root only after a national task force, registry operator, public authorities and a global stability review aligned.
  • Gihan Dias matters less as a lone inventor than as a figure who crossed the layers: early email, academic networking, .LK stewardship, script technology and the institutional work of delegation.

Two quiet records

The two IANA pages are almost aggressively plain. One is headed “Delegation Record for .ලංකා”; the other substitutes .இலங்கை. Both designate a country-code top-level domain for Sri Lanka. Both name the LK Domain Registry as manager and Gihan Dias as administrative contact. Beneath those human-readable labels sit the ASCII forms that DNS software can carry: xn--fzc2c9e2c and xn--xkc2al3hye2a.

That symmetry is the point. Sinhala and Tamil do not appear as decorative translations on a government portal. They are separate strings in the global naming system, each with name servers, an operator and a chain of responsibility. The records make a modest proposition with considerable institutional weight: a country may have more than one legitimate way to name itself at the Internet’s root.

The proposition did not follow automatically from connectivity. Dias’s career makes the distance visible. The Internet Hall of Fame credits him with helping establish Sri Lanka’s academic Internet, beginning with its first email system in 1990, and with leading LEARN from 1993 to 2003. In his recollection, the early service was built for scarcity. Mail could be composed offline, exchanged during a short dial-up session and read after disconnecting. Some users arrived carrying diskettes. Every design choice accounted for expensive calls and intermittent links.

This was access as reachability. A message had to get through.

Dias also helped secure and operate .lk, according to his Internet Hall of Fame profile. That work introduced a different question: who is entitled to name things, under what rules, and with whose trust? A country-code registry is not merely a server. It is a local institution attached to a globally unique namespace. Its credibility depends on technical continuity, but also on whether the community it represents accepts its stewardship.

By the time Sri Lanka pursued country names in Sinhala and Tamil, the problem had changed again. Packets could cross the island; an academic network existed; commercial access had arrived. Yet Dias argued that an Internet people could not understand, or on which they could not make themselves understood, remained of limited use. Script was no longer a presentation detail. It was part of the access stack.

How a name reaches the root

The 2010 IANA delegation report reads like a compressed constitution for this kind of change. It first fixes the strings precisely. ලංකා consists of specified Sinhala Unicode code points and means “Lanka”; இலங்கை consists of specified Tamil code points and means “Sri Lanka”. Their Punycode encodings are not alternative public names but the ASCII-compatible forms used underneath.

Then the report turns from characters to institutions. Sri Lanka’s Information and Communication Technology Agency had convened an internationalised-domain-name task force in 2007. Work began in May 2008. Invitations went out through newspapers as well as directly to interested parties. The participants named in the record crossed sectors: government agencies, the University of Colombo School of Computing, a newspaper organisation and two Internet providers.

The group had to settle two questions. Which strings properly represented the country? And which institution could operate them? It reportedly reached unanimity on the names and on using the existing .LK registry rather than creating another body. The latter decision was practical—another institution was judged financially infeasible—but it also carried a theory of legitimacy. The operator already had technical history, a national base and experience with the corresponding ASCII domain.

The request still needed more than a local vote. Support came from the ICT agency, the telecommunications regulator and the Department of Official Languages. A DNS Stability Panel considered confusion and security. IANA examined local backing, legal standing, fair operation, in-country presence and technical competence. ICANN’s Board approved the two delegations on 5 August 2010; the IANA records give 19 August as their registration date.

This sequence complicates the heroic version of Internet history. Dias was an important connective figure: early network builder, registry executive, national-language researcher and the named administrative contact. But the root did not accept his personal preference. It accepted a request that had been converted into evidence of community agreement, operational capacity and compatibility with a shared technical system.

The danger hidden in a digit

Internationalisation is sometimes described as if Unicode merely opened a larger character cupboard. An IETF review record shows why that is too easy. In an exchange labelled “Gihan Dias: Tamil digits”, the Sri Lanka IDN Task Force objected to treating the Tamil digits U+0BE6 through U+0BEF as generally valid for IDNs because of confusion risk. The ensuing discussion asks whether such problems belong in the protocol’s universal rules or in the policies applied by individual registries.

That boundary remains fundamental. A protocol that excludes too much can deny a script legitimate expression. A protocol that admits everything can move difficult security and usability judgments downstream to registries that vary widely in expertise. Dias’s concern, as preserved in the record, was institutional as much as typographic: if a standards group could not reach a workable consensus, registrars might face an “anything goes” environment.

The lesson is not that one proposed treatment prevailed. The source does not establish that. It is that multilingual naming requires native-script knowledge inside technical governance. Visual similarity, customary use, input behaviour and reader expectations cannot be derived from a code-point number alone. The people who know a script’s lived grammar have to meet the people responsible for global interoperability.

A delegation is a beginning

Two top-level strings do not make a multilingual Internet. They do not translate a ministry’s forms, put Sinhala or Tamil keys on a handset, make every email address interoperable, persuade certificate authorities or applications to accept an IDN, or tell a citizen which site to trust. They create an authoritative possibility. Whether that possibility becomes ordinary depends on registration policy, software support, content, security practice and sustained use.

The institutional tail is long. In May 2025, the ccNSO Council approved the membership of Sri Lanka’s Sinhala IDN ccTLD manager and welcomed LK Domain Registry. The minutes note that the same manager oversees the ASCII and IDN domains. Fifteen years after delegation, the namespace was still acquiring another formal connection to the community of country-code operators.

That detail rescues the story from ceremonial history. Root entry was not the finish line; it was the beginning of stewardship. An operator must keep names resolving, publish defensible rules, respond to abuse, maintain community confidence and ensure that one language community is not treated as the optional annex of another.

Dias’s most useful legacy here is a change in the definition of “connected”. The early network taught Sri Lanka how to move messages through constrained links. The registry taught it how to hold responsibility for a national namespace. The IDN process forced a further recognition: people do not inhabit a network only through routes and addresses. They inhabit it through names they can read, type and regard as their own.

Sources