I had to write a post about this. \u00a0We do our best to protect our clients and make sure their sites remain online at all times. \u00a0As web designers we work with many different domain registrars. \u00a0These are the companies you use to register a domain name. \u00a0Most also provide web hosting services but it’s by no means required to use them (in many cases we don’t suggest it). \u00a0GoDaddy has become the largest and most recognizable name in this industry. \u00a0We personally like to use Namecheap internally, but there are many other decent providers.<\/p>\n
Some are good, some are bad, and some just get the job done. \u00a0Then there is 1and1. \u00a0We cringe when we hear that a client uses 1and1’s registrar because we know it’s going to be an uphill battle to push servers live, do migrations, set up a CDN, or change even simple DNS A records. We pushed the change on 1and1 and waited. \u00a0Generally registrars put up warnings letting users know that locations may cache the old records up to a day. \u00a0It’s normal and fine in this case; this minority of users just wouldn’t pass through the CDN network. \u00a0We waited an hour or so for the status to change, then the client contacted us. \u00a0Site reported down. \u00a0Users reporting it down. \u00a0Not good. \u00a0We checked again, pending update.<\/p>\n This is where things went from bad to worse. \u00a0We queried the DNS, it didn’t report back an ip. \u00a0No error, just blank. \u00a0So we then queried 1and1’s DNS servers directly since they held the records prior. \u00a0Blank. \u00a0We surmise that while the updates were “pending”, 1and1 wiped the records on their own servers and left us high and dry with the site offline. \u00a0So we called in to support. \u00a0After a 20 minute hold, we finally spoke to a CSR that told us this was normal and could take up to 48 hours. \u00a0We responded that it is not normal at all, normal registrars do not wipe their nameservers even after delegating to an external provider… \u00a0then the call was disconnected.<\/p>\n We then started to coordinate with Stephen at Armed Gamer to get the domain off of 1and1 as soon as possible as they were unwilling to provide support other than “just wait, it’s normal” (as he’s losing revenue and followers from an offlined site we have no way to fix). \u00a0Both Armed Gamer and Uber Motif have reached out to 1and1’s support via phone and Twitter without results.<\/p>\n Most registrars take a few hours to transfer out of, 1and1 holds a domain hostage for 5 days because that’s the max allowed under ICANN regulation. \u00a0We don’t support holding clients hostage, especially when they are currently incurring damages as a result of incompetence.<\/p>\n 1.<\/b> Simple nameserver delegation change that takes 10 minutes at most on the majority of registrars is claimed to take up to 2 days on 1and1.<\/p>\n 2.<\/b> Above simple change does not wipe records on normal registrars, no downtime occurs. \u00a0Not on 1and1.<\/p>\n 3.<\/b> Transferring a domain out of 1and1 takes 5 days. \u00a0Most registrars complete the request same day.<\/p>\n 4.<\/b> Support has long hold times, does not acknowledge the above behavior as damaging to our client and atypical for a registrar to engage in.<\/p>\n It’s been over 17 hours downtime as of the writing of this post with no end in sight. \u00a0We would have been furious over a few hours of downtime, We’ll update this post below as things progress (times in EDT):<\/p>\n 18:29, Stephen reports that a support tech at 1&1 just took notice of this blog post (sort of obvious since we linked it on twitter) and claims this has been forwarded along to DNS administrators for investigation. Let’s see if anything happens. <\/p>\n 20:15, Just got off the phone with Aaron at 1&1. They are working to provide a solution and insist they can complete it by 4AM. I requested that our transfer ticket go through to move this out to Namecheap before that. Armed Gamer is at near 21 hours down and will be near 30 hours by that time. This is really the only thing they can do at this point to mitigate further damage. <\/p>\n ~3:00, Domain transfer processed.<\/p>\n 7:16, Aaron notifies us of the processed transfer.<\/p>\n 8:38, Updating nameserver delegation at Namecheap.<\/p>\n 8:39, Update fully propagated.<\/p>\n It’s possible this may have been an issue at 1&1 in their system because they provide a free CloudFlare-supported CDN service and we are using the CloudFlare’s standalone paid service. But it doesn’t excuse it from working and our client shouldn’t have had to suffer through their troubleshooting.<\/p>\n I’d like to thank Aaron at 1and1 for reaching out to us to gain a resolution in this matter. If it were not for him, we’d likely still be waiting. <\/p>\n Update 12\/2<\/strong>: 1&1 actually reached out to us again last month to provide us with more specialized contact information for anyone stuck with a DNS issue. While we’re fairly sure the underlying technical issues have not been resolved yet, this is at least a positive step from them, information is as follows:<\/p>\n Please write back into our comments or send us an email to let us know if this helped you out!<\/p>\n Update 12\/9<\/strong>: Nameserver is not responding on a client using 1and1’s nameservers. We tried the above contact info, the number was busy and we have not received an email in over an hour. Fun.<\/p>\n Update 1\/17\/2016<\/strong>: We still continue to receive reports that 1and1 hasn’t changed its sleazy business practices. I decided to research a bit, and it appears 1and1 is under the 2013 Registrar Accreditation Agreement from ICANN. This means they need to provide a clear description of their customer support procedures. I would argue providing us with false information like the above constitutes a violation of this agreement, but alas I am not a lawyer. Here’s a link to information and a complaint form should you want to file a complaint with ICANN: https:\/\/www.icann.org\/resources\/pages\/customer-service-2013-05-03-en<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" I had to write a post about this. \u00a0We do our best…<\/p>\n","protected":false},"author":2,"featured_media":6987,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13],"tags":[],"jetpack_featured_media_url":"https:\/\/xwaretech.com\/wp-content\/uploads\/2014\/09\/11-nightmare-featured.jpg","_links":{"self":[{"href":"https:\/\/xwaretech.com\/wp-json\/wp\/v2\/posts\/6983"}],"collection":[{"href":"https:\/\/xwaretech.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/xwaretech.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/xwaretech.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/xwaretech.com\/wp-json\/wp\/v2\/comments?post=6983"}],"version-history":[{"count":0,"href":"https:\/\/xwaretech.com\/wp-json\/wp\/v2\/posts\/6983\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/xwaretech.com\/wp-json\/wp\/v2\/media\/6987"}],"wp:attachment":[{"href":"https:\/\/xwaretech.com\/wp-json\/wp\/v2\/media?parent=6983"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/xwaretech.com\/wp-json\/wp\/v2\/categories?post=6983"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/xwaretech.com\/wp-json\/wp\/v2\/tags?post=6983"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n
\nFor 1and1, it’s best to explain the travesty we’re going through. \u00a0One of our clients, Armed Gamer (http:\/\/armedgamer.com<\/a>, offline at this time), experiences large spikes in traffic throughout the day when he makes or promotes new posts. \u00a0A way to help mitigate slowdowns and lower the server load is to CDN the site, we chose CloudFlare in this case. \u00a0For this to work, the nameservers for the domain need to be changed from 1and1 to Cloudflare. \u00a0It’s normally a trivial task and it takes maybe up to 10 minutes on slower registrars. \u00a0 But not on 1and1.<\/p>\nTo sum up:<\/h3>\n
we’re now at war until this gets resolved<\/strike>. \u00a0If you or your company has experienced a nightmare like this at the hands of 1and1, please share this along and comment below. \u00a0If you’re looking to move your domains off of their system, we will provide assistance free of charge.<\/p>\n1&1 Internet, Inc.
\nThe Solutions Team
\n877-501-2631
\nsolutions@1and1.com
\ncares@1and1.com<\/del> (they likely got rid of this team, if they ever really had it, so they could invest more advertising money into deceiving people) <\/p>\n