.IS

TLD metadata
Add Properties
Register
Transfer in
Trade
Troubleshooting
Transfer out


Add Properties

To add additional properties for .IS domains to a contact, follow the procedure below.

Take note: additional properties for .IS only have to added if the registrant, company or individual, is located in Iceland.

  • Lookup the contact you wish to add the properties to and open it. Next, you're going to add additional properties to the contact. In this case, you will choose the IS(RegistryIS) option. Once you've selected the .IS properties, you'll be directed to the page where you can submit the requested information.

  • Fill out the data as requested by the form and click save properties when you're done.
  1. Icelandic ID number (Kennitala): Submit the Icelandic ID number.

Register

To create a .IS domain, follow the procedure below:

Take note: Role contacts are not allowed for .IS domains. There has to be a valid natural person/organisation mentioned in the registrant contact. In case you do not wish to specify the name of a natural person in a registrant contact belonging to an organisation, you can use the organisation name in both the name and organisation fields of the registrant contact. Do keep in mind that there are other registries that do not allow the use of an organisation name in the name field. Strictly use a registrant contact formatted as described above only for .IS domains and you should have no issues.

  • Create a contact handle, or search for a contact handle already created with valid data to use for the create. For a detailed description of how to create a contact handle, check the contacts knowledgebase article.
  • If necessary, add additional properties for .IS (RegistryIS) to the registrant contact.
  • Use the availability checker to determine if the domain is available. If the domain is available, select it to register using the green 'Select to register button'.
  • Submit the details you wish to use for registration. For in-depth support on the registration process, check the register domain(s) knowledgebase article.
Troubleshooting

Registered a .IS domain and your freshly registered domain does not resolve? Refer to the troubleshooting section of this article to update your IS get your domain resolving.


Transfer in

To transfer in a .IS domain, follow the procedure below:

Take note: Role contacts are not allowed for .IS domains. There has to be a valid natural person/organisation mentioned in the registrant contact. In case you do not wish to specify the name of a natural person in a registrant contact belonging to an organisation, you can use the organisation name in both the name and organisation fields of the registrant contact. Do keep in mind that there are other registries that do not allow the use of an organisation name in the name field. Strictly use a registrant contact formatted as described above only for .IS domains and you should have no issues.

  • Create a contact handle, or search for a contact handle already created with valid data to use for the transfer. For a detailed description of how to create a contact handle, check the contacts knowledgebase article.
  • If necessary, add additional properties for .IS (RegistryIS) to the registrant contact.
  • Request the transfer through the Domain Manager. For instruction on how to request a transfer through the Domain Manager, check the initiate transfer knowledgebase article.
  • Once requested, contact support to receive a transfer TAG
  • Once received, provide the TAG to the current registrar and request a push transfer.
  • Once the push transfer is initiated by the current registrar, the transfer will complete.
Troubleshooting

Transferred in a .IS domain and your domain does not resolve? Refer to the troubleshooting section of this article to update your IS get your domain resolving.


Trade

To successfully change the registrant for a .IS domain, follow the procedure below.

Take note: Role contacts are not allowed for .IS domains. There has to be a valid natural person/organisation mentioned in the registrant contact. In case you do not wish to specify the name of a natural person in a registrant contact belonging to an organisation, you can use the organisation name in both the name and organisation fields of the registrant contact. Do keep in mind that there are other registries that do not allow the use of an organisation name in the name field. Strictly use a registrant contact formatted as described above only for .IS domains and you should have no issues.

  • Create a contact handle, or search for a contact handle already created with valid data to use for the Registrant change. For a detailed description of how to create a contact handle, check the contacts knowledgebase article.
  • If necessary, add additional properties for .IS (RegistryIS) to the registrant contact.
  • Update the domain to the new registrant contact. For a detailed description of how to update domains through the Domain Manager, check the domain update knowledgebase article.
  • Once the trade is requested, either the Admin contact or the Registrant contact has to approve the registrant change through email. Once the trade has been accepted through, the trade will complete real-time.

Troubleshooting

New registered domain not resolving

.The .IS registry (ISNIC) has additional requirements for nameservers in order for domains to resolve. If nameservers are not up to par according to what ISNIC demands regarding the nameserver requirements, domains will be placed in a so called parking mode and will not resolve until the nameservers are up to par.

  1. Nameservers must be correctly registered in DNS (with A and/or AAAA resource records).
  2. Nameserver names may only contain ascii letters, digits, hyphen and periods.
  3. Nameservers must allow connection to UDP port 53, and to TCP port 53 as well.
  4. For nameservers within the ".is" zone, the following also applies:
    1. The hostname part of the nameserver's name may not be numeric only: i.e. 123.example.com is invalid.
    2. The name of the nameserver must not be be a bare domain name, it must have a hostname part (e.g. hostname.example.net)
  5. Nameservers must be correctly registered with ISNIC.
  6. TTL for NS records can not be lower than 86400 seconds (24 hours).

A nameserver check to test the configuration for your nameservers can be found at: https://www.isnic.is/en/host/test.

Transferred domain stopped resolving

If a transferred .IS domain changes nameservers during a transfer and the new nameservers are not configured according to the above requirements, they will be parked on ISNIC's nameservers until the issues are resolved. The process that precedes the parking of domains on ISNIC nameservers starts with warning emails. Check the full process below:

  1. Warning e-mails are sent weekly to the domain's contacts. First only the zone contact but eventually zone, tech and admin contacts and finally the registrant is added.
  2. If the problem persists for 8 consecutive weeks, the domain is suspended: it is marked inactive in the registry and its DNS records are removed from the ".is" zone file
  3. After the domain has been put on-hold it will be tested daily and activated if found to comply with the requirements.
  4. After another 30 days the domain is moved to the ISNIC parking servers (the DNS server settings for the domain are changed).

If the domain setup is brought into compliance (issues are resolved) before the domain is transferred to the ISNIC parking servers, the domain will be re-listed in the ".is" zone automatically and no further action need be taken.

If the domain setup is brought into compliance (issues are resolved) after the zone has been moved to ISNIC's parking servers, then one of the domain's contacts will need to use this website to redelegate the domain to the correct name servers.


Transfer out

To transfer out a .IS domain you're not going to need an authcode. Similar to .IS domains, outgoing transfers are pushed to the new registrar.

  • Have the registrant contact the new registrar and request the transfer.
  • Have the registrant provide the TAG of the gaining registrar once the transfer has been requested.
  • Provide the new registrar's tag to support by sending an email to support@realtimeregister.com. Support will than arrange the domain to be pushed to the new registrar.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.