Skip to main content

Domain name registration through Google - when things go wrong.

Not too many people know, that you can register new domains through Google. This can be done when you're registering for Google Apps Standard Edition which is free and somewhat stripped version of their Google Apps Premium Edition. Latter one is tailored more to suit business needs.

With $10/year prize tag it's not cheapest option, but you'll get "private domain registration to protect against spam at no extra cost, full DNS control and domain management, automatically configured to work with Google services, email, calendar, instant messaging, web pages and more also at no extra charge".

As a comparsion GoDaddy offers .org domains at $14.99/year so it's actually not that bad offer. Google actually is just collecting the data and sending it to their partners (godaddy, enome) which does the registration. I decided to give it a try at January 11th. To my big surprise things didn't went that smoothly. It's been now one week since my order - the domain I registered is actually not registered at all - it's up for grabs for anyone out there. All I got was account to Google Apps Standard Edition. After one days waiting I figured out there's something wrong with my order as my domain was freely available and in my Google Apps Dashboard my status was "Not active, pending payment", so I asked Google a status request about my order. I got automated reply stating that my orders payement was pending and I should wait them to process it. I waited one more day and since things didn't get better I sent another mail stating that my order was invalid. Once again I got automated reply without any useful info (except the fact that by replying to that mail Googles personnel should contact me). I replied to the mail stating that there really is something wrong as my payement hasn't gone through. I waited few days for reply which I never got.

At this point all I wanted was to delete my google apps account so I can retry, so I browsed through google help center and forums for information. What I found was that you actually CAN'T delete your account if you're ordered your domain through Google ( Wait what? So.. now I have Google apps standard edition account for my nonexisting domain which I can't delete so that I could try registering again. Also, I can't get any contact to Googles "customer service" to get someone to solve this.

I did a quick search from Google Help forums with words "Not active, pending payment" and got quite a lot of results. It seems that Google staff reads those forums and can "flag" some posts which some support personnel can then pick and solve so I left their forum message describing my case and asking for any help. I haven't got any replies yet.

As a summary about everything above: I'm a victim of extremely automated process which had some hickups when it was processing my order and I'm not too happy about that. I know Googles strength isn't in customer service but in their extremely scalable systems. What pisses me most is that their system didn't work for me.

Based on my experience I really can't recommend anyone registering their domain names through Google.

End of rant.

Popular posts from this blog

Plone 4, ZEO and supervisor

This post belongs also to the "lessons learned" category.

With Plone 3, ZEO and supervisor combination you've probably configured your supervisor to start plone instances by running $BUILDOUT/parts/client1/bin/runzope.

Problem is that with Plone 4 your $BUILDOUT/parts/client folder doesn't contain anything else than etc folder. You know starting instances by targeting supervisor to use $BUILDOUT/bin/client1 fg doesn't work like you'd expect (supervisor would control the client1 script - not the actual plone process).

My colleague Jussi Talaskivi figured that using 'console' argument instead of 'fg' for bin/client1 script should do the trick. With 'console' argument stopping, starting and restarting Plone 4 instances with supervisor works like a charm.

Below is full example of working supervisor configuration.

[buildout] parts = supervisor [supervisor] recipe = collective.recipe.supervisor port = 8200 user = xxxx password = xxxx pr…

Plone RPM deployment

It's been ages since I wrote my last post. I guess now it's time to make that up with post about Plone deployment. In a last few months I've had chance to invest part of my time at work to develop our Plone deployment model and since there hasn't been that many posts about the subject I thought I'd share my experiences for the community.

Before I get to the details here's some background information about the environment I've been dealing with. I'm working at the University of Jyväskylä, Finland. Our university is a heavy weight Plone adopter here in Finland. Plone is in use by every faculty and department. We have about 500 - 700 content managers and about 50 - 60 separate Plone instances. Our front page gets about 2 - 3 million hits page views / month. The important information in previous data is the amount of instances. 50 - 60 is just my estimation about our current status and that amount is increasing every year. I'm sure you got the idea so I&…

Speed comparsions between Plone and Wordpress

Jon Stahl wrote recently a blogpost about Plone being three times faster than Dropal, Joomla and Wordpress. We had a small discussion about this in my workplace and as my colleague pointed out this wasn't a really that comprehensive test that you could state Plone being 3 times faster than it's competitors. This seemed a bit unfair test considering how fast this has been spread in tweet/blogosphere, so I decided to repeat the test with a bit more critical viewpoint.

What's wrong in the original test? No one would consider opinion poll with 10 answers nowhere near trustworthy - it's all the same with requests. I didn't want to put up all the cms so I just set up second best (Wordpress 2.9.1) and compared that to my Plone development site (4.0a3). As a comparsion I did the first test with same ab command Jon used and my iMac gave following results:

Wordpress: 7.13 requests / second
Plone: 17.10 requests / second

So far we have clear winner and Jons data holds up... almos…