|Why register .si?|
|Slovenia, is located in Central Europe at the crossroads of main European cultural and trade routes. It boarders with Italy to the west, Austria to the north, Hungary to the northeast, Croatia to the southeast, and the Adriatic Sea to the southwest.
If you conduct business from within Slovenia, it is time to register a .SI domain extension. Registering a dot 'SI' country code extension (top level domain name) will increase credibility for your business across the globe. Why? Country-code domains are meant specifically for businesses that do business within a particular country--in this case, Slovenia. The .com domain (and other generic TLDs) are not targeted and that online space is saturated--and you likely already have the .com for your business. Extend your brand presence with a more relevant, shorter domain--a ccTLD that differentiates you from competitors.
Identify yourself as an official Slovenia business owner and give your clients and constituents more confidence as they interact with you online. Country code domains also help you rank higher in local search results.
1. Domains according to the "first come, first served" principle
The new rules will until further notice keep the same spectrum of entities eligible to register a .si domain; the domains can be
registered by Slovene entities only and other international organisations as it is currently done. However there are no more domain
name restrictions, domains only have to comply with the syntax rules which have stayed the same. After 4th April 2005 all eligible
entities are able to register any domain (that is not yet taken) according to the "first come first served" principle, the only
limitation being the maximum number of 20 domain holdings. Arnes doesn't check the legitimacy of domain applicants to specific
domains. That responsibility is entirely up to the rightful claimant.
2. The registrar system
The second significant change is that with 4th April 2005 Slovenia, by following the examples of other national registers, also
starts a registrar system. Before 4th April 2005 the applicants/domain holders registered their domains directly with Arnes. With
the new system, Arnes only kept its basic function as a register, all the rest have been taken over by the registrars.
ARNES operates the primary server for the .si domain, which must contain appropriate records for all domains that holders wish to be visible on the Internet. After registering a domain name under the .si, the new domain name must also be entered into the primary DNS server.
ARNES operates the primary servers for both .si and .edus.si.
The domain name holder must report appropriate data for entry into the top-level DNS server on the "Authorisation to operate domain names under the .SI top-level domain" form. This form is in the pdf. format, for which you will need version 6 of Acrobat Reader. If you have an older version of this program, use this version. Please consult your ISP about this form, since they will be able to send you partly completed form with data on the authorised person and the DNS servers. If the domain name holder operates the primary DNS server for his own domain name, he or she should report the appropriate data using the same form.
The authorisation form must be signed by the administrative contact person stated during domain registration. To insert the domain name in the primary DNS for .si, the IP address of the primary and secondary DNS servers for the registered domain name has to be sent to the following address:
ARNES, p.p. 7
or by fax on +386 1 479 88 99.
The correctness of settings and the operation of DNS servers is checked every day between 12:00 and 15:00. After each check, an email is sent to the address given on the authorisation form. In the event of an error in the DNS server settings for the domain name, you should contact your authorised person. ARNES offers advice and technical help for DNS server settings only to organisations connected to the ARNES network.
A domain name will be excluded from this automatic checking procedure if it fails within two months of ARNES receiving an insertion request that does not meet technical criteria. If this happens a new request for entry into the DNS will have to be made.
Users of the ARNES network can contact email@example.com for help.
The primary DNS server and at least one secondary DNS server must exist for the domain. It is recommended that at least one secondary server should be in a different physical location from the primary server.
Domain data must contain a SOA (Start of Authority) record in standard format. Data on the domain server in the SOA record must be the name of the primary server, and the email address given in the SOA record. Their information must be valid and active. The serial number and time-intervals must meet the recommended values (see example below).
Under Internet standards, the address firstname.lastname@example.org must be operational, and the relevant MX record must exist.
NS records must refer to operating DNS servers. Records on all listed servers must match.
Recommended values in SOA record
Refresh 8 hours (28800 seconds)
Retry 2 hours (7200 seconds)
Expire 7 days(604800 seconds)
Time To Live 1 day (86400 seconds)
Example SOA record for domain name domain.si:
domain.si. IN SOA primary.domain.si. hostmaster.domain.si.
1 ; serial
28800 ; refresh
7200 ; retry
604800 ; expire
86400 ; TTL
Example NS records for domain name domain.si:
domain.si. IN NS primary.domain.si.
domain.si. IN NS secondary-1.domain.si.
domain.si. IN NS secondary-2.domain.si.
A record for localhost must be defined within the domain:
localhost.domain.si. IN A 127.0.0.1
We can customise a solution to fit your business needs.