How difficult can it be to transfer a .name domain?

How difficult can it be to transfer a .name domain?

I was reading an article where it was noted that .name names can now be used for OpenID registrations.

With a little more research I found that the sites only supported new registrations, unfortunately they did not support transfers.

Several years ago when the .name domains were new and the in thing to do, I registered my domain and with

Over the years the support for .name domains has declined, to the point where the domain control panel no longer exposed any controls for my domain.

Any changes, e.g. domain or email forwarding required a tech support contact.

I started looking for a new .name registrar, and to my surprise found very few, and even fewer that were accepting transfers.

I already have several domains registered with eNom, and fortunately eNom did offer .name transfers, and did actively support .name domains, or at least this is what they advertised.

I initiated an electronic domain transfer with eNom, but the transfer is denied with a message stating that the authorization code does not match.

I call support, and am told that .name transfers do not require an authorization code.

I call eNom support, and am told to just enter 00000.

I submit the order again using 00000 as the authorization code, and the same problem as before.

I call eNom support, explain the story, are transferred, and this time I am told that I really do require an authorization code.

I call support, explain the story, are transferred, and after authenticating myself I receive an email with the authorization code.

I submit the order again, this time using the authorization code.

I receive the email, using the whois information from my current registrar, asking for transfer permission, I approve.

Several days go by and the order status remains in a processing state.

I call eNum support, and are told to wait a few more days.

After a few more days I call eNom support, and I am told to open a trouble ticket using their online support system.

I open the ticket, and a few days later I get a reply email stating that the issue needs to be escalated to the developers.

Every few days I ask for a status update, and am told they are working on the problem.

After about two weeks the transfer completes.

For some reason eNom uses the whois email address I registered with them to contact me for support status updates.

It was by chance that I opened my hotmail account and noticed the support emails.

All previous eNom communications were done using my primary email address I registered with eNom.

Since eNom was not in my good books, I decided to open a support case with eNom complaining that they use the wrong email address for support emails.

After several exchanges, including them not believing me, and me having to show them screenshots of my hotmail account, and screenshots of Outlook with regular eNom email communications, they offer an excuse that the system uses whois emails because everybody must fill out a whois email address.

When reality is that the eNom account system uses your primary email address and the whois email address is inconsequential when using eNom identity protection plans.

I just gave up and closed the case.

I configure the domain forwarding of to, and it seems to work fine.

Now I want to configure email forwarding, but unlike where email forwarding was part of the .name package, eNom wants an additional $21.95 per year for email forwarding.

I don’t use that email address, but I order the email forwarding anyway.

A few minutes later I get a confirmation email, but the order was cancelled, with a message stating that I must cancel my existing email forwarding.

I open a support ticket with eNom, and are told that the domain transfer is independent of the email forwarding, and that I must cancel the email forwarding with

I login to my account, and I still see my listed as an active domain.

I start a support chat conversation, and I am told that they will open a support case and get back to me.

A day later I receive an email from, and they confirm that they have deleted my domain from the fronted and backed systems, I confirm that the domain is no longer listed on my account.

I order email forwarding with eNom again, and the same problem.

I call support, are transferred, and after some time while the agent conversed with technical support, am told that my new registrar, eNom, must contact the .name ICANN authority, and arrange for the transfer.

I am also told by the agent that .name registrations are problematic in that very few individuals or registrars really understand how it works.

On a whim I decide to see if email forwarding still works, and sure it does.

So given that neither nor eNom is capable of taking care of the problem, and that eNom wants to charge me $21.95 per year for forwarding, and that email forwarding is working, I decided to just do nothing.

I really cannot offer any advice for anybody with an existing .name domain, but what I would say is that if you decide to register a .name domain, make sure your registrar is really committed to supporting .name.

Asus P5E-VM HDMI motherboard

In the ongoing saga to get a motherboard that works well with Vista SP1 going to sleep, I have yet again switched motherboards.

As previously posted I’ve tried an Intel DG33TL board, and an Intel DQ35JO, and I am now using an Asus P5E-VM HDMI board.

I was happy with the Intel DQ35JO, but this did not last very long. A few days after posting I found my machine with garbage characters on the screen, requiring a cold boot. Intel support was of little help, but a few days later I updated the firmware on my ThinkPad T61, and I read that one of the fixes in the firmware was to fix garbage characters on the screen when sleeping on resuming from sleep caused by the AMT feature. The DQ35JO board also has AMT, so maybe that was the same problem.

Not wanting to have more trouble I returned the Intel DQ35JO board to Fry’s, and I ordered an Asus P5E-VM HDMI board from Amazon. There are three variants of the P5E-VM board; the SE, DO, and HDMI, but only the HDMI variant was immediately available on Amazon. I would not be using the HDMI output since I was going to use the ATI HD 2600 XT card, but it does not hurt to have onboard HDMI available.

Installing the board was simple, the RAID still worked, and Vista Ultimate x64 booted without issues. The only missing driver was for the Realtek audio. I tried the driver from the Asus site but that failed to install, rather disappointing. Asus support told me to use the driver from the Realtek site, and that worked fine.

I again noticed that the power LED was intermittently not working, this being the third board with this problem, I was now convinced it was a problem with the actual LED. I contact Antec support, and a few days later I received a new power LED free of charge. I installed it, and problem solved.

Asus provides several utilities to monitor and adjust the performance of their boards, i.e. AI Suite and PC Probe II. I’ll spare you the details but these utilities are of very poor quality, failing to install, failing to uninstall, crashing on start, crashing on sleep, crashing on resume from sleep, and worse when uninstalled they still leave crap behind. I had to delete two tasks from the task scheduler, delete several files and folders, and manually delete several COM objects from the registry. Avoid these tools.

One feature I really like about the Asus board is the BIOS upgrade feature. Just copy the firmware to a USB key, plug the USB key in, boot, enter the BIOS, select the upgrade option, pick the file, and upgrade, so simple.

This time round I waited a few weeks before posting, and I am very happy with the Asus P5E-VM board.