Skip to main content

Attention Adobe Connect Users: Service Change (Action Required)

Adobe Connect, ICANN's remote participation tool, is moving over to an ICANN-hosted server. The transition will occur on a rolling basis between 26 September and 14 October 2016. After 14 October, all Adobe Connect meetings will use the new server.

ICANN made this change to address the performance and reliability problems you have been experiencing. Having the server under ICANN's management means that Adobe Connect will be more stable than in the past. You should experience increased call quality and better customer service. In addition, we will be able to create custom pods – for example, multilingual chat, multilingual scribe streams and timers.

What Exactly Is the Change?

Old server:
New server:

What Do I Have to Do?

Important! Because the change is happening in phases, not all meetings will move over to the new server at the same time. During the transition period, check your meeting invitation for the correct URL. If you have any questions, contact the meeting organizer.

  • If you are a meeting attendee, you don't have to do anything. Your meeting organizer should be updating the meeting request with the new URL.
  • If you are a meeting organizer, update the meeting notice. Change the portion of the URL that specifies the server to the new ICANN server.

What if I Have Questions?

Update: We've received questions about new security features. We have moved to a Single Sign-On (SSO) security feature, only available to ICANN organizational staff, that is also behind a VPN tunnel. This security feature significantly increases our back-end security with Adobe. With this change, community members who had a custom login on the old server will no longer be able to use it on the new server. However, community members can simply log in as a Guest and have the same experience as they did before with their custom logins. Meeting hosts can promote Guests to Presenter or Host status, as needed, to give additional meeting room control and access.

Email your questions to

More Announcements
Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as"""" is not an IDN."