31–40 of 308 posts
Does anybody have a guide on how to migrate away from GoDaddy without downtime? And what would you recommend instead? We currently host a bunch of domains and use their DNS servers.
I use namecheap[1] for everything domain related and never had a problem. There's a no downtime migration guide here [3]. [1] (Affiliate) http://www.namecheap.com?aff=37912 [2] (Non-Affiliate) http://www.namecheap.com [3] http://www.namecheap.com/support/knowledgebase/article.aspx/...
Does anybody have a guide on how to migrate away from GoDaddy without downtime? And what would you recommend instead? We currently host a bunch of domains and use their DNS servers.
Does anybody have a guide on how to migrate away from GoDaddy without downtime? And what would you recommend instead? We currently host a bunch of domains and use their DNS servers.
I use namecheap[1] for everything domain related and never had a problem. There's a no downtime migration guide here [3]. [1] (Affiliate) http://www.namecheap.com?aff=37912 [2] (Non-Affiliate) http://www.namecheap.com [3] http://www.namecheap.com/support/knowledgebase/article.aspx/...
Status Alert: Hey, all. We're aware of the trouble people are having with our site. We're working on it.
That understates things by several orders of magnitude. It's not just their site that is down, it's their domain name servers, so most websites that bought their domain from GoDaddy are unreachable (unless you are working off of cached domain data).
Does anybody have a guide on how to migrate away from GoDaddy without downtime? And what would you recommend instead? We currently host a bunch of domains and use their DNS servers.
Aside from that, focus on two concepts: TTL and overlap.
1) On your old host, lower the TTL of all your records to something quite low, like 30 seconds. This will increase the burden on your nameservers, since records will only be cached that long, but it will make you more nimble as you make substantial changes.
2) Migrate your records over to the new provider. This can be a bit tedious for more complex zones, but rather straight-forward for many. Change your nameserver on your local machine to point to your new DNS host, just to test in a "real-world" scenario.
Then go to your registrar and flip the switch.
Switching DNS providers is much less prone to downtime than changing web hosts, since the records themselves aren't changing much -- just where to find them.
If you're switching registrars, the principal is similar, setting the TTL quite low during the transition to help you make changes more quickly should something go wrong.
Does anybody have a guide on how to migrate away from GoDaddy without downtime? And what would you recommend instead? We currently host a bunch of domains and use their DNS servers.
DNS services cost money, either in staffing or recurring charges, so it really depends on your budget. Neustar is a nice DNS provider ($50+/mo). Generally you'll want to set up your new DNS, turn down the refresh on your existing DNS domains, wait $old_refresh or so, then change your primary/secondaries listed at your registrar to point at your new DNS.
Does anybody have a guide on how to migrate away from GoDaddy without downtime? And what would you recommend instead? We currently host a bunch of domains and use their DNS servers.
If you are using GoDaddy for anything, you deserve what you get. If you are using GoDaddy for not just registration but also for DNS, I would just fix it as soon as possible and not tell anyone. Also, do backups, use good password practices, and everything else that everyone knows and the lazy will still fail to do. Oh, 20 seconds in and a downvote. I can take them, I didn't ignore the last 8 problems GoDaddy has bee…
Does anybody have a guide on how to migrate away from GoDaddy without downtime? And what would you recommend instead? We currently host a bunch of domains and use their DNS servers.
Example:
1) setup amixdomain.com at, say, zoneedit.com (not recommending them just using as an example).
2) Wait a bit, say several hours then use a dns utility like the one at kloth.net to query the two zoneedit.com dns servers directly. If both of them answer for your domain you are in good shape. I don't know what the lag is until zoneedit reloads their dns. It could be in a minute or it could take longer (which is why you can just wait).
Or you can use the OSX (or equivalent on other platforms) dig tool from the command line as follows, using ycombinator.com as an example:
Edit: What I meant to say was "if you have a mac open a terminal session and use dig" sorry for seeming to implying that dig is an OSX tool.
dig @NS1.EASYDNS.COM ycombinator.com 'A'
yc's servers are, so I picked one. You want to query all the dns servers:
Name Server: NS1.EASYDNS.COM
Name Server: NS2.EASYDNS.COM
Name Server: NS3.EASYDNS.ORG
Name Server: NS6.EASYDNS.NET
Name Server: REMOTE1.EASYDNS.COM
Name Server: REMOTE2.EASYDNS.COM