Price comparison of Slovenian (.si) domain names

I compared a number of Slovenian domain registrars for prices for one year for a .si domain, with no hosting.

tld-registrar.com - €30 / year
101domain.com - $119 / year
slovenia-domain.com - €16.80 / year
domene.si - €19.96 / year
domovanje.si - €15.59 / year
domenar.net - €14.90
hitrost.com - €15.54
Gigaspark.com - €18.90

The cheapest of the providers that had an english option was slovenia-domain.com at 16.80 euro. They also had a paypal option, so this is the one I chose.

domenar.net also appeared to have a paypal option, but it didn't work when I tried it.

All the other providers required a bank transfer as a form of payment, and had no english option. their sales support spoke english, and were even happy to zero rate the purchase for VAT, meaning that it would have been possible to order the domain for €12.95 from HitTrost.com
(podpora@hitrost.com)

New Domain Registry System in Malaysia

We are pleased to announce that .my DOMAIN REGISTRY will be launching a new .my DOMAIN REGISTRY System. We would like to thank our valued customers for all comments and opinions as the new system would not be possible without you.

With this new system,

• a Registrant can apply for multiple domain names in one submission and the domain names can be registered up to 5 years
• a Contact Person with the same Contact Code can perform multiple domain name transaction such as modification, deletion and transfer
• a domain name to be transferred to a new Registrant, is required to make payment before it is registered.
  

The effective date of this new system is on Monday 1st February 2010, 9.00 A.M.

In conjunction with the launch, .my DOMAIN REGISTRY website and WHOIS service will not be available during the following planned maintenance works:

Start Date/Time : Saturday, 30th January 2010, 9:00 A.M.
Completion Date/Time : Monday, 1st February 2010, 9:00 A.M.

However, please note that all domain names registered with .my DOMAIN REGISTRY will not be affected by this.

Please do not hesitate to e-mail domreg@domainregistry.my or call us at 03-8991 7272 if you have any query at all.

Changes to the NameCheap DNS API

The changes are primarily to namecheap.domains.create, namecheap.users.create methods and to the error numbers that were returned earlier. Error numbers returned for several API methods are changed and are now documented in the link below.

Changes to the API:
http://developer.namecheap.com/docs/doku.php?id=api-new-release:index

New error code documentation:
http://developer.namecheap.com/docs/doku.php?id=api-new-release:error-codes

Schedule for the update:
Jan 28, 2010 - To API sandbox (api.sandbox.namecheap.com)
Feb 15, 2010 - To production (api.namecheap.com)

NOTE: if you want to start making changes/ test today, new version of code is already available at http://test.api.sandbox.namecheap.com/. This end point will be removed after changes are moved to the proper sandbox URL.

WHMCS Plugin Customers:

Please note that the open source version of the plugin available at http://code.google.com/p/namecheap/ will not be updated anymore as WHMCS is providing their own official plugin for Namecheap. So, please pass this information on to WHMCS so that they can update the plugin.

We sincerely apologize for the inconvenience caused. Please post any question you may have in the new "Developer/ API Discussions" section of Namecheap Community Forums (http://community.namecheap.com/forums/viewforum.php?f=17)

Free DNS monitoring service

http://websitemonitor.sms.eu.sk/en/signup.php

Got a problem with a DNS lookup that cuts out every so often, and you need to get SMS notification whenever the lookup fails.?

Try the link above, which will monitor your domain every 15 minutes, and email or text you whenever there's a problem.

Sunrise for Russian Federation top level domain .RF (.РФ )

Today, November 25, 2009 starting 12.00 MSK trademark holders may
enjoy .РФ Domains Sunrise Registration.

The .РФ Top level domain stands for "R.F." or Russian Federation.

Before March 25, 2010 RU-CENTER clients - Russian-named trademark
holders may register .РФ domains at 1200 rub.

Before submitting an application for .РФ domain registration we recommend
that you study "Sunrise Registration Schedule in РФ TLD".

Further details about .РФ domains sunrise registration are given at nic.ru

To learn more about РФ TLD please refer to za-rf.ru

IP address change of main Nameservers

IMPORTANT

IP Addresses of the nameservers on freenameservers.co.uk are changing from:

ns3.openmerchantaccount.com, from 78.110.167.104 to 85.234.144.8
ns4.openmerchantaccount.com, from 78.110.165.153 to 92.48.88.241

This change will be finalized on the 18th of December 2009, when the old IP address will
fail to work.

Into DNS, a free DNS checking service

Category	Status	Test name	Information
Parent		Domain NS records	Nameserver records returned by the parent servers are: ns3.openmerchantaccount.com. ['78.110.167.104'] (NO GLUE) [TTL=14400] ns4.openmerchantaccount.com. ['78.110.165.153'] (NO GLUE) [TTL=14400] udns2.ausregistry.net.au was kind enough to give us that information.
		TLD Parent Check	Good. udns2.ausregistry.net.au, the parent server I interogated, has information for your TLD. This is a good thing as there are some other domain extensions like "co.us" for example that are missing a direct check.
		Your nameservers are listed	Good. The parent server udns2.ausregistry.net.au has your nameservers listed. This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers.
		DNS Parent sent Glue	The parent nameserver udns2.ausregistry.net.au is not sending out GLUE for every nameservers listed, meaning he is sending out your nameservers host names without sending the A records of those nameservers. It's ok but you have to know that this will require an extra A lookup that can delay a little the connections to your site. This happends a lot if you have nameservers on different TLD (domain.com for example with nameserver ns.domain.org.)
		Nameservers A records	Good. Every nameserver listed has A records. This is a must if you want to be found.
NS		NS records from your nameservers	NS records got from your nameservers listed at the parent NS are: ns4.openmerchantaccount.com ['212.227.102.68'] [TTL=7200] ns3.openmerchantaccount.com ['78.110.167.104'] [TTL=7200]
		Recursive Queries	I could use the nameservers listed below to performe recursive queries. It may be that I am wrong but the chances of that are low. You should not have nameservers that allow recursive queries as this will allow almost anyone to use your nameservers and can cause problems. Problem record(s) are: 78.110.167.104 78.110.165.153
		Same Glue	Looks like the A records (the GLUE) got from the parent zone check are different than the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do.I detected some problems as follows: For ns4.openmerchantaccount.com the parent reported: ['78.110.165.153'] and your nameservers reported: ['212.227.102.68'] For ns3.openmerchantaccount.com the parent reported: ['78.110.165.153'] and your nameservers reported: ['78.110.167.104']
		Glue for NS records	OK. When I asked your nameservers for your NS records they also returned the A records for the NS records. This is a good thing as it will spare an extra A lookup needed to find those A records.
		Mismatched NS records	OK. The NS records at all your nameservers are identical.
		DNS servers responded	Good. All nameservers listed at the parent server responded.
		Name of nameservers are valid	OK. All of the NS records that your nameservers report seem valid.
		Multiple Nameservers	Good. You have multiple nameservers. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me.
		Nameservers are lame	OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
		Missing nameservers reported by parent	OK. All NS records are the same at the parent and at your nameservers.
		Missing nameservers reported by your nameservers	OK. All nameservers returned by the parent server udns2.ausregistry.net.au are the same as the ones reported by your nameservers.
		Domain CNAMEs	OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
		NSs CNAME check	OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
		Different subnets	OK. Looks like you have nameservers on different subnets!
		IPs of nameservers are public	Ok. Looks like the IP addresses of your nameservers are public. This is a good thing because it will prevent DNS delays and other problems like
		DNS servers allow TCP connection	OK. Seems all your DNS servers allow TCP connections. This is a good thing and usefull even if UDP connections are used by default.
		Different autonomous systems	OK. It seems you are safe from a single point of failure. You must be carefull about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down.
		Stealth NS records sent	Ok. No stealth ns records are sent
SOA		SOA record	The SOA record is: Primary nameserver: ns3.openmerchantaccount.com Hostmaster E-mail address: ns3.openmerchantaccount.com Serial #: 1256841781 Refresh: 28800 Retry: 7200 Expire: 2419200 4 weeks Default TTL: 7200
		NSs have same SOA serial	OK. All your nameservers agree that your SOA serial number is 1256841781.
		SOA MNAME entry	OK. ns3.openmerchantaccount.com That server is listed at the parent servers.
		SOA Serial	Your SOA serial number is: 1256841781. This can be ok if you know what you are doing.
		SOA REFRESH	OK. Your SOA REFRESH interval is: 28800. That is OK
		SOA RETRY	Your SOA RETRY value is: 7200. Looks ok
		SOA EXPIRE	Your SOA EXPIRE number is: 2419200.Looks ok
		SOA MINIMUM TTL	Your SOA MINIMUM TTL is: 7200. This value was used to serve as a default TTL for records without a given TTL value and now is used for negative caching (indicates how long a resolver may cache the negative answer). RFC2308 recommands a value of 1-3 hours. Your value of 7200 is OK.
MX		MX Records	Your MX records that were reported by your nameservers are: 10 mail.freebiesms.com.au 212.227.102.68 [These are all the MX records that I found. If there are some non common MX records at your nameservers you should see them below. ]
		Different MX records at nameservers	Good. Looks like all your nameservers have the same set of MX records. This tests to see if there are any MX records not reported by all your nameservers and also MX records that have the same hostname but different IPs
		MX name validity	Good. I did not detect any invalid hostnames for your MX records.
		MX IPs are public	OK. All of your MX records appear to use public IPs.
		MX CNAME Check	OK. No problems here.
		MX A request returns CNAME	OK. No CNAMEs returned for A records lookups.
		MX is not IP	OK. All of your MX records are host names.
		Number of MX records	OK. Looks like you only have one MX record at your nameservers. You should be carefull about what you are doing since you have a single point of failure that can lead to mail being lost if the server is down for a long time.
		Mismatched MX A	OK. I did not detect differing IPs for your MX records.
		Duplicate MX A records	OK. I have not found duplicate IP(s) for your MX records. This is a good thing.
		Reverse MX A records (PTR)	Your reverse (PTR) record: 68.102.227.212.in-addr.arpa -> s15243155.onlinehome-server.info You have reverse (PTR) records for all your IPs, that is a good thing.
WWW		WWW A Record	Your www.freebiesms.com.au A record is: www.freebiesms.com.au [212.227.102.68]
		IPs are public	OK. All of your WWW IPs appear to be public IPs.
		WWW CNAME	OK. No CNAME

Processed in 0.214 seconds.

This is a sample domain set up on FreeNameServers.co.uk, and the report is from IntoDNS