|44067 .is||| Login | Lost password ||
Frequently Asked Questions
If you have your own nameservers, you must have configured the domain and the nameservers must be registered with ISNIC. If you do not have any nameservers yet, you can park your domain with ISNIC. See "Domain->Requirements" and "Nameserver->Requirements" . You must also have available the NIC-handles of the domain's contacts, and you yourself must be logged in via "Contacts->Login" . If contact handles are unavailable, you must first register the contacts (and/or yourself) via "Contacts->Register" on the left.
All .is domain's are registered in the ISNIC domain registry and their registration information is available via the ISNIC web. However, the registration WHOIS lookup is rate-limited and does not include pending domains. Use a suitable whois client on port 4343 to determine if a particular domain is available for registration. (Or use http://whois.isnic.is:4343/domain.is). These lookups are not rate-limited.
Usually, a domain's adminstrative contact is simply the registrant. If the registrant wants someone else to have full change-control over the domain, a third party can be appointed administrative contact.
Domains can have up to four different contacts (NIC-Handles). Each contact serves a different role and holds different change-authority over the domain. The contacts use their NIC-Handles to log into the ISNIC web to modify their own, and their domain's registration.
The annual renewal fee is EUR 39. The first year fee (the registration fee) must be prepaid before registration can proceed. For list of other fees see ISNIC's tariff.
The last step of the registration process allows the registrant to select to pay the fees using a creditcard. The registrant can also register the card details with ISNIC and register his/her domains for automatic renewal. In this case the renewal fee will be debeted to the card 60 days prior to its expiry date, automatically.
If a domain remains unpaid on it's expiration date, ISNIC informs the domain's billing contact (and the domain's administrative contact) that the domain is about to be deactivated (put on hold).
Modifications are web-based. You must begin by logging in to the ISNIC web using your NIC-handle and password and select "My page". You will then get a list of domains and nameservers for which you are registered and over which you have change-control. Select the domain/nameserver you wish to modify and follow the instructions.
The domains zone contact is the first (master) nameserver's technical contact. It is automatically modified, when the domain is redelegated to a new set of nameservers. The zone contact can thus only be changed by changing the technical contact of the domains current nameserver as registered with ISNIC, or by redelegating the domain to a different set of nameservers.
Glue record modifications are web-based. Log on to the ISNIC web using your NIC-handle (you must use either the NIC-handle of the administrative contact or of the technical contact). On "My page", select the domain you wish to move (change nameservers for), click "Redelegate" on the menu, and follow the instructions.
It is important that nameservers are registered with ISNIC by the nameserver operator/owner or their technical representative. The nameserver's technical contact becomes the zone contact for all .is domains delegated to the nameserver and therefore must be whoever administers the nameserver. ISNIC contacts the domain's zone contact in case of technical difficulties with the nameservers and this contact must have systemic access to the nameserver and be able to fix DNS-technical problems.
The only way to test a particular UDP service is to query the service that listening on the particular port. Thus the only way to test if a DNS server is running on UDP port 53 is to make a DNS query. As there is no way of knowing wich zones are served by that host, so a query for the root zone NS records is made. A secondary query is also made, in case the root zone fails.
It is important to realize that TTL is not an attribute of a domain (zone). TTL is an attribute of each record in the zone. ISNIC only requires a minimum TTL on the nameserver records within the domain (NS resource records). The value of the TTL field in the NS records affects the query-rate on the .IS nameservers, therefore there is a certain minimum enforced. Please note that this minimum TTL requirement only applies to the NS records. It is possible to debate as to what precisely the minimum value should be, but experience in recent years suggests that these values should only be lowered from rather high defaults if some changes are planned. According to RFC1912:"Popular documentation like [RFC 1033] recommended a day for the minimum TTL, which is now considered too low except for zones with data that vary regularly. Once a DNS stabilizes, values on the order of 3 or more days are recommended. It is also recommended that you individually override the TTL on certain RRs which are often referenced and don't often change to have very large values (1-2 weeks). Good examples of this are the MX, A, and PTR records of your mail host(s), the NS records of your zone, and the A records of your nameservers."and according to RFC1030:"Most host information does not change much over long time periods. A good way to set up your TTLs would be to set them at a high value, and then lower the value if you know a change will be coming soon. You might set most TTLs to anywhere between a day (86400) and a week (604800). Then, if you know some data will be changing in the near future, set the TTL for that RR down to a lower value (an hour to a day) until the change takes place, and then put it back up to its previous value."A recent study on DNS performance concludes that"It is not a good idea to make the TTL values low on NS records, or for A records for name servers. Doing so would increase the load on the root and [g]TLD servers by about factor of five and significantly harm DNS scalability."from DNS Performance and the Effectiveness of Caching by Naeyeon Jung, Emil Sit, Hari Balakrishnana and Robert Morris ACM Transactions on Networking, Vol. 10, NO. 5 October 2002.
According to RFC5966:" ....any DNS server needing to send a UDP response that would exceed the 512-byte limit is for the server to truncate the response so that it fits within that limit and then set the TC flag in the response header. When the client receives such a response, it takes the TC flag as an indication that it should retry over TCP instead."And in section 4 of RFC5966 states:" All general-purpose DNS implementations MUST support both UDP and TCP transport. o Authoritative server implementations MUST support TCP so that they do not limit the size of responses to what fits in a single UDP packet."Accordingly, ISNIC requires nameservers hosting .is domains to support queries over TCP.
All .is domains are checked for compliance with the ISNIC technical requrements once a month. Those that fail this compliance test (which you can execute at Domains->Check Setup any time) are then tested weekly and their technical- and zone contacts informed via email about the nature of the problem. If the technical/zone contact fails to remedy the situation and the domain fails these tests for eight consecutive weeks, the domain is deactivated (removed from the .is zone, put on hold).
When a contact object (admin, technical or billing contact) is registered with ISNIC an email is sent to the registered email address requesting that the person (or role) confirm their willingness to register, and the validity of the email address. This email contains an URL that must be followed to activate the NIC-handle.
The domain is transferred from one registrant to another via the ISNIC web interface. One of the domains contacts logs on using his/her NIC-handle and password, selects the domain to transfer, and selects "Transfer". The contact will be prompted for the details on the new registrant. The domains current administrative contact will then be asked to confirm the transfer request, and once that is received, the request is queued for processing.
The corresponding non-IDN domain is constructed from the IDN domain according to the following table:þ -> th á -> a í -> i æ -> ae é -> e ó -> o ö -> o ý -> y ð -> d ú -> u
ISNIC does not have any official registrars. The registrants have direct access to the .IS registry and deal directly with the registry. Anyone can host .IS domains as long as their nameservers meet ISNICs technical requirements, and the domains zone as set up on those nameservers meets ISNICs delegation requirements.
An agent is a person or company that has applied for and been granted an agent status with ISNIC. Usually the agent simply manages the domain's registration with ISNIC on behalf of the registrant. Please see the application forms for the terms and conditions of agent registration.
A ISNIC service provider is a hosting provider that has registered with ISNIC as such and is willing and able to host .is domains according to ISNIC's technical delegation requirements. The ISP is listed with ISNIC, and has access to the ISP portal on the ISNIC web. Please see the application forms for the terms and conditions of such registration.
Domains can be parked, i.e. temporarily delegated to a special set of parking nameservers. A registrant may park a domain if e.g. the zone is not ready at the time of registration or the production nameservers have gone offline for a long period of time and the domain is in danger of being deleted. While a domain is parked it will not receive any email and no websites will be active. If you choose to park a domain you select the option "Parking" from the ISP's dropdown list. The registrant can park or unpark a domain at any time (via the ISNIC web -- see "How do I change my domains delegation records in the IS zone?" ). Domain parking is a free service.
Web Forwarding is a service provided by ISNIC to direct your domain to a IP address or a pre-defined web URL. If you choose to use an IP address, the webserver should be configured to display your website - you should contact your webserver administrator to make sure this is possible.
ISNIC - Internet a Islandi hf.· Katrinartuni 2, 18th floor · 105 Reykjavik · ICELAND
tel +354 578-2030 · fax +354 578-2031 / +354 561-0999 · e-mail: firstname.lastname@example.org
ISNIC Opening hours: 9-12, 13-16 GMT
Copyright ©2002 Internet a Islandi hf · About ISNIC