About a year ago, I bought a short url so I didn’t have to use tinyurl.com or bit.ly on Twitter. It’s a .me address, and at the time the best/cheapest .me registrar was GoDaddy.
I don’t host sites there, but I registered the domain there anyway. Then I immediately pointed the domain at my old shared hosting account over on 1and1.
Things worked perfectly!
After a few weeks, I decided to add an email at this short url. But I didn’t want to use 1and1′s email system, so I set up Google Apps for the domain and pointed my MX records at Google.
Again, things worked perfectly!
Then … two weeks ago I started getting inundated with spam. Lots of spam. I got about a hundred or so “Out of office” emails an hour from a mailing list in Russia.
All in response to an email that seemingly originated from my address.
Turns out, some spammer was using my email address in the “from” field of their messages. As a result, I got all of the “unsubscribe” and “out of office” responses.
One system even blacklisted my email address as a known spammer. I didn’t find out until several angry client phone calls – why haven’t you sent us the code we paid for?!
Simple Solution
Google recommends setting up authentication for your email to prevent this. It’s actually pretty easy. Just add a TXT record to your DNS with some encrypted strings that Google knows. Then email recipients can verify that messages appearing to be from you are actually from you.
Well, simple if you don’t use 1and1.
You see, shared hosting accounts with 1and1 use a very basic DNS system. You can use their name servers, or remote name servers. You can use their MX records or set your own MX records.
But you can’t add a TXT record.
Migrating
I was one of the many who jumped ship when GoDaddy announced their (shortlived) support of SOPA. I quickly moved my email domain (and several other domains) over to Namecheap.
But to keep things simple, I had left the DNS in place – still pointing at 1and1.
To add a TXT record, I moved my DNS registration to Namecheap for my .me domain as well. I figured it would be easy enough:
- Keep the domain registered with Namecheap
- Register the DNS with Namecheap
- Set the TXT record I needed for authenticated email
- Set an A record to point back at my 1and1 hosting account
And sure enough it worked! The spammy emails stopped. My sites still worked. Everything was happy.
Until I got the email …
The Problem
We at 1&1 Internet have noticed that you have changed the name server of your eam.me domain. Your new settings are:
DNS1: dns3.registrar-servers.com
DNS2: dns2.registrar-servers.com
DNS3: dns5.registrar-servers.com
DNS4: dns4.registrar-servers.comBecause of these new settings, your website hosted with 1&1 Internet can no longer be reached via the eam.me domain. The e-mail addresses included in your Developer Package, if any, have also been disabled.
If you still intend to keep using our services, you can enter the following name servers with your registrar by February 23, 2012 at 11:46:00 PM and continue using our services as usual.
DNS1: ns51.1and1.com
DNS2: ns52.1and1.comIf by February 23, 2012 at 11:46:00 PM you have not registered with our name servers, we will remove the eam.me domain from our systems. If you want to use your domain with your 1&1 Package after February 23, 2012 at 11:46:00 PM, you can specify this configuration on the Control Panel once more and enter the name servers specified there with your registrar.
Yeah … this doesn’t work for me. The applications (namely YOURLS) are still running on my shared hosting system over at 1and1. But I need the DNS running through Namecheap so I can keep the TXT entry available for email authentication.
I tried one workaround – setting a CNAME record for the domain to point to my 1and1 account – but this ate my MX and TXT records as well.
At the moment (assuming no one offers a better alternative) it looks like I’ll just need to move my applications to a different system entirely. That is not an optimal solution … and this entire c****** f*** has me wanting to dump 1and1 altogether.
Update
I emailed 1and1 a potential workaround that I found in their own knowledge base. Essentially, it recommends setting the external domain, pointing it at an external DNS system, then pointing the external DNS system back at 1and1.
My email was along the lines of “I found a solution posted on your site, had you directed me here in the first place, it would have saved us all a lot of time.”
They responded … by directing me to the exact same link:
Dear Eric Mann, (Customer ID: XXXXXXXX)
Thank you for contacting us.
We advise you to use the method on the link below.
How do I use my own name server for a 1&1 domain?
http://faq.1and1.com/domains/domain_admin/dns_settings/18.html
The technical subdomain for your account is sxxxxxxxxx.onlinehome.us
If you have any further questions please do not hesitate to contact us.
> For the record, I have found a way to make this work. According to your
> own knowledge base, it *is* possible to host a site with your system while
> the domain and DNS is registered elsewhere:
>
> http://faq.1and1.com/domains/domain_admin/dns_settings/18.html
I’m not sure why … but this irritates me even more than the original fiasco.


