For anyone wishing to own their own Internet domain name, owning and managing a co.za domain could not be harder if the co.za registrar, Uniforum SA, tried.
There are several major problems all caused by the lack of a modern system to register and manage and pay for co.za domains.
To register a Top Level Domain (TLD) such as a dot com or dot net or dot org, the procedure is straight forward. You can choose between a large number of competing online registrars who regularly offer promotions and discounts which allows you to get the best possible deal. I use godaddy myself, so I’ll use them as my example.
To register a new TLD domain, you open godaddy’s web site and register an account with them. Then you search for the domain name you want. If it’s available you add it to your cart and proceed to checkout. You pay for your domain with a credit card or with your PayPal account. As soon as you have paid for the domain, it is registered and you can then proceed to activate hosting for it. That is accomplished by entering the nameserver information. You can even create custom nameservers for your new domain simply by adding them and assigning to them the IP addresses that your web hoster supplied to you.
For most TLD domains, your domain will come online either immediately or within a few hours. No checks are enforced on your domain. If you enter the wrong information, it obviously won’t work, but it won’t require you to have any pre-existing DNS records on a pre-existing web hosting account.
If you want to switch your domain to a new server, you simply login to your online control panel, that your registrar provides, and edit the nameserver fields. Updates either reflect immediately or within a few hours. Again no checks are made for pre-existing DNS records on your new server (or web hosting account) - whatever you type in is simply accepted.
The system is easy and quick. Getting your domain set up on a new server takes a few minutes and the changeover happens either immediately or within a few hours.
This is, however, not the case with a co.za Second Level Domain (SLD). Frankly it is a nightmare. Registering a co.za domain is a technical challenge. For starters, unlike with a dot com, you cannot register a co.za domain without first setting up an existing DNS SOA (Start of Authority) record for it on TWO nameservers. This means that before you can register a co.za you have to host it, which is an additional expense, especially for someone who simply wants to own a co.za domain but does not necessarily wish to use it right away.
To register a co.za one must fill out a text form and then email it to a special email address which automatically processes domain registrations, updates and deletes. For a new domain, registration is usually accomplished within minutes IF the name servers specified on the registration form contain correctly formatted SOA entries for the domain name being registered. If Uniforum SA’s script finds an error in them, it rejects the application. The same applies to updates, but not to deletes.
Updating a co.za domain involves a frustrating delay of 24 hours in which voting tickets are sent out to the email address specified in your current registration. If the email addresses are no longer valid, you have to fill in a form, take a copy of your ID, get them certified and then fax them to Uniforum SA. The only online method of updating involves responding to emailed out tickets. If after 24 hours, the votes all accepted the update, then Uniforum SA updates the domain registration and a further delay is involved while you wait for the DNS to propagate. This can take 8 hours.
All this pales in comparison to the technical challenge involved in setting up custom name servers for your co.za domain. It is used to be popular for many co.za domains to have name servers at the same domain, like this:
ns1.domain.co.za
ns2.domain.co.za
However, this all changed in May 2005 when Uniforum SA adopted a very strict regime for registering custom name servers for a co.za domain. Unlike with a dot com, you cannot simply add them yourself and be merrily on your way.
To register custom name servers for a co.za now requires you to have two static IP addresses assigned solely to your domain. They cannot also be used as custom name servers for any other co.za domain, which used to be the case.
The reason is because each IP must now reverse resolve to its respective name server name. Uniforum SA’s domain update script checks that each IP address has correctly formatted SOA records, that it contains no “bad” data, is not missing any data and that each IP reverse resolves. None of these things are essential for your custom name servers to work. All that is required is that your domain registrar add A and NS records to its DNS database for your domain name - no checking of external DNS entries is needed.
So why does Uniforum SA check for all these things? Because some guy (Matt Tagg) discovered a theoretical exploit for adding A records to third party domains during the domain update process. An exploit that had never actually ever been used. An exploit that potentially only exists because of the way that Uniforum SA updates domains - via unauthenticated emails instead of through an authenticated online control panel that only allows you to make changes to your own domains.
So the bottom line for any owner of a co.za domain is that you have no choice as to what you will pay for one, since there is only one registrar for them and they decide the price as they see fit. co.za domains now cost R50 to register, but due to all the technical challenges involved, most people prefer to pay their ISP or a web hoster (like myself) to do it for them at around R250 per annum.
They also have the added expense of having to pay for a web hosting account since without one, it is not possible to register a co.za domain. And when it comes to switching web hosts, it takes over 24 hours instead of a few hours. And if they want custom name servers, it costs extra to have two dedicated static IPs assigned to your account, and then there is the additional technical hurdle of making sure that all the required DNS records are all sailing in a row.
Did I mention that if something goes wrong and your update is rejected that you have to wait at least another 24 hours to try again? If the domain update has a few errors, it may not reject it outright but instead will sleep for 8 hours at a time, without any ability to tell it to recheck again now.
I have yet to register or update a co.za domain with custom name servers that did not fail at least once. Reason for that? Uniforum SA provides no online tool for you to use to verify that everything is good to go. Nope. Nothing useful like that. You submit your update application and take your chances. And fail and fail and fail, each time waiting either 24 hours to try again or, if you’re lucky, only 8 hours between tries.
Great system.
Score: 0 out of 10.