Summary

  • IANA’s public .IE delegation record now names IE Domain Registry CLG as manager after a transfer completed on 23 July 2026.
  • This was formal recognition, not a new technical operation: IEDR had performed significant day-to-day duties since July 2000, and IANA recorded no associated operational or technical change.
  • A delegation-state receipt should separate operator, recorded manager, government endorsement, IANA evaluation, Board procedure and root implementation so that “transfer” does not imply ownership or an outage-prone migration.

The change happened in the record, not in the live registry

The public IANA record for .IE now places IE Domain Registry CLG in the manager field. The change became operationally visible on 23 July 2026, three days after the ICANN Board approved Resolutions 2026.07.20.02–03. IANA’s July root-operations audit lists the completed work as changes to the organisation, administrative contact and technical contact.

Read alone, the word “transfer” suggests that one party handed a running system to another. That is not what IANA says happened. Its evaluation states that no operational or technical changes were pursued, that the way .IE is operated was not intended to change, and that the request was limited to formally recognising the organisation already doing significant day-to-day work.

The live function and the formal attribution had been separated for 26 years. University College Dublin was the recognised manager when .IE entered the root in 1988. On 1 July 2000, UCD and the then IE Domain Registry Limited entered a Deed of Assignment, and IEDR assumed day-to-day responsibilities. In 2010, UCD told IANA that the relevant assets, liabilities, staff and undertakings had been reassigned, that it no longer held an operational role and that its continuing status as recognised manager was unsatisfactory.

Yet UCD remained in the manager field. Administrative and technical contacts were moved to IEDR personnel in 2012, creating a public record in which the contacts and the operating institution pointed one way while the formal manager pointed another. The July 2026 action closed that gap.

This is useful institutional housekeeping. It does not create .IE, start IEDR’s service, sell a namespace or transfer Ireland’s sovereignty. A root record coordinates a named function. It should not be inflated into a title deed.

A failed transfer can preserve continuity and still leave debt

The delay was not simply an overlooked form. The IANA report preserves a history of disputed institutional design. In 2001, the Internet Service Providers Association of Ireland raised concerns about industry participation, public financial and management reporting, dispute arbitration and the absence of an agreed public-policy forum. IEDR described changes to its board, advisory structure and appeals while preparing a formal proposal.

Irish legislation changed in 2007 to allow ComReg to regulate the domain. In 2011, an IEDR transfer request did not receive support from ComReg or the responsible government department. IANA identified matters that required fuller treatment, and the request was administratively closed in May. The department nevertheless described the request as essentially administrative: staff, policies, service levels and daily operations would remain largely continuous.

That episode demonstrates why operation and recognition cannot be treated as one switch. The live registry continued while the transfer process stopped. Service continuity did not prove that the formal record was current; an unresolved formal record did not prove that the live registry had failed.

The parties restarted the process in 2023. Ireland opened a public consultation in December 2024 on the management framework and future security and stability. A consultation summary followed in April 2026, together with Terms of Endorsement. According to IANA, those terms are reviewed every five years, may be updated by the Minister and must be revisited when relevant legislation changes. IANA received the formal request on 26 April and issued its assessment on 11 June.

This sequence matters because the 2026 result did not erase the 2011 non-result. It resolved the record through a new chain of domestic endorsement, incumbent consent, local-interest evidence, IANA evaluation and Board procedure. A trustworthy ledger keeps both states: a proposal can fail without the namespace failing, and a later proposal can succeed without pretending the earlier objections never existed.

Six roles sit behind one manager field

The manager field is compact; the authority chain is not. IEDR operates the registry and now occupies the formal field. UCD was the incumbent recorded manager and supplied consent. The Irish Minister supplied government support and a domestic endorsement framework. Listed parties supplied support or non-objection relevant to IANA’s local-interest test. PTI evaluated the request through the IANA functions. The ICANN Board checked whether proper procedure had been followed, after which the root-zone workflow implemented the accepted change.

These roles cannot lawfully or technically substitute for one another. A government can state its position without editing the root. IANA can evaluate a request without operating .IE. The Board can confirm procedure without becoming the namespace owner. A root-zone maintainer can publish the changed record without writing Irish registration policy. IEDR can run the service without speaking for every person in Ireland.

The support evidence has the same boundary. IANA recorded consent from UCD and IEDR, ministerial support, four statements of support or non-objection, and no objection letter. That is relevant evidence under the transfer criteria. It is not a referendum and does not establish a mandate from every registrant, operator or citizen.

The Board’s approved resolutions are similarly narrow. They say that PTI reviewed and evaluated the request and that the documentation demonstrated proper procedure. The Board said it knew of no significant community issue and identified no specific security, stability or resiliency risk. Some materials remain confidential. None of those statements makes the Board the political principal of the Irish namespace.

The missing object is a delegation-state receipt

The current record tells readers the result. It does not present the whole transition as one inspectable object. A delegation-state receipt would join the prior manager and new manager to the exact effective time, while keeping each control role separate.

The receipt should record incumbent consent, proposed-manager acceptance, government position, local-interest evidence and the versioned evaluation. It should identify the Board action and root implementation event. It should compare administrative contact, technical contact, nameserver and DNSSEC fields before and after. Most importantly for this case, it should carry an explicit operational-handover delta: none.

That last field prevents a basic category error. Manager transfer, contact change, nameserver change, DNSSEC change, policy change and operating handover are different transitions. They may occur together, but they did not do so here. A public delta table would let an operator or regulator see immediately that the formal identity changed while service architecture and daily operation remained continuous.

The receipt also needs a correction history and review route. If a manager name is wrong, a contact becomes stale or a support document is later released, the record should append the correction rather than silently rewriting history. Confidential application material can remain protected; the public layer needs hashes, dates, roles, outcome and a reasoned boundary for withheld evidence, not personal correspondence.

This would not manufacture legitimacy. It would make the coordination function honest about what it did. The July change did not grant life to .IE; it removed a stale separation between the organisation in the manager field and the organisation doing the work.

Sources

  1. IANA report on the transfer of .IE
  2. ICANN Board approved resolutions, 20 July 2026
  3. IANA .IE delegation record
  4. IANA root-operations audit, July 2026
  5. IANA guide to ccTLD delegation and transfer
  6. IANA common questions on ccTLD transfers
  7. Irish public consultation on .IE management
  8. Irish Government announcement of Terms of Endorsement
  9. Government of Ireland Internet policy page
  10. IANA Naming Function Contract