Skip to content
Fragmented Development

Transfering a domain from GoDaddy to Hover

I have been slowly moving all of my domains away from GoDaddy to my preferred registrar, Hover (full disclosure; that's a referral link). I have about a dozen domain names, but one of them is much more complex and important than the rest:

So, out of all the transfers, this one went the worst. Of course. I'm going to document my failures, and ways to avoid them, for posterity.

Failure 1: TTL

TTL stands for "time to live". It indicates how long a record is "good" before the browser/computer should check the record again. In most DNS changes, you want to set it low ahead of time; that way, the new values will be picked up shortly, when DNS is usually cached for a week or more. GoDaddy has their TTL set to 1 hour by default, which is very low.

When switching registrars, you want to set your TTL pretty high if you can. One week would be a good start. That way, if you have some downtime, returning visitors will still have your domain in their DNS cache.

Failure 2: Timing

I started my domain transfer at 7:00 PM. The work did not take very long, but the waiting killed me. There are several steps in the domain transfer process that take time, and it did not finish before I went to sleep.

The process stalled at a very inconvenient point. The domain had been transferred to Hover, but Hover was still pointing at GoDaddy's nameservers. I had completely set up the zone at Hover, but GoDaddy had removed it as soon as the transfer was complete. This is mostly what caused the lapse in DNS coverage.

While this was still a failure on my part, I feel I can comfortably put partial blame on Hover. The nameserver configuration was not available until the domain was completely transferred, even though I could edit the rest of the zone file. This seems bizarre, and caused the majority of the issues.

Failure 3: Lots of eggs, one basket

FragDev is the parent domain to all of my services: RSS reader, webmail, GNUsocial, you name it. Almost all of the services that I run that impact multiple users are a subdomain of It also hosts my primary website, and is the domain I use for email. It has over a dozen subdomains, a TXT record, MX records, and just about everything else you can do via DNS.

Before the transfer, I realized that if anything went wrong, I would blink off the face of the Internet. This is probably not the safest way to do things.

Domains remain at the whim of your registrar. A clerical error or service outage could completely take me (and all of the services that I run) out of commission. While I don't like this, I'm not entirely sure how to combat it just yet.

For now, I'm making sure my domain is registered with a reputable registrar, backed by a large company. In the future, I may spread things out over several domains to minimize the importance of one.

I'm also going to stay away from any domain transfers for a while!

Tags: networking dns

Add Your Comment