We switched over to Google as the registrar for a number of our domains yesterday (we used to use a mix of GoDaddy and Register.com previously), and in the process our DNS got screwed up.

We didn’t realize this right away because it affected one of our subdomains (which meant the website itself was up and running, but one of the ways in which you can sign into Kerika was messed up.)

The basic problem was with Google’s way of handling incoming transfers of domains that have already been set up: even if you use the setting for keeping your current domains, Google doesn’t keep your current DNS settings for all the subdomains as well.

Our apologies for everyone affected by this!

Update on 10:15AM PST Oct 6:

We are still waiting for Google’s bazillion DNS servers to all get the new DNS entries.  It’s a bit hit-or-miss for individual users, depending upon which Google server they get routed to when they try to login.

Here in the Seattle area, for example, we can login consistently, but we know some of our users can’t. In India it is literally a 50:50 chance that your Kerika session will connect to an updated DNS server or not.  In the UK the problem seems mostly fixed now.