Amazon S3 domain hosting: CNAME too long [closed]

Question

Closed. This question is off-topic. It is not currently accepting answers. Learn more.

---

Want to improve this question? Update the question so it's on-topic for Stack Overflow.

Closed 7 years ago.

So I have a bucket set up on Amazon S3, which is configured as a site, and is accessible via the endpoint address.

When I go to paste this endpoint address into 1and1's control panel, it tells me it's too long (past the ridiculous 30 character limit).

What are my options instead, here? 1and1 allows me to change the DNS, or add an IP address as the A record. If either is applicable here, what value would it be set to, bearing in mind my bucket is in the Ireland datacenter.

Thanks all.

Answer 1

Here was my solution after 1&1 were ridiculously unhelpful. It involves an external DNS provider, but oh well, it works just fine.

I signed up for Namecheap's FreeDNS service with the naked domain (i.e. don't include the 'www'). Point your DNS records with 1&1 to use Namecheap's servers.

The records are then set up as:

@  http://www.yourdomain.com  URL redirect (301)  3600
www  your.long.cname.aws.amazon.com.  CNAME (Alias)  3600

The top line sorts out the naked domain issue (and I seem to recall trying it set to the CNAME also and it didn't work), and the TTLs can be changed for whatever you feel is appropriate.

Answer 2

I rang the 1and1 technical helpline with the same problem. The answer: if the cname alias is more than 32 characters, then ring your host and ask them for a shorter cname alias. Yes, 1and1 genuinely think that you should ring Amazon Web Services and ask them to reconfigure their load-balancing software for you!

I immediately cancelled my domain name registration with 1and1. That or a domain name transfer to another provider are the only options if you want to go with Amazon S3.

Answer 3

Unless you're somehow getting a static IP assigned to your S3 bucket, I'm afraid there's not much you can do.

You could always try using using 1&1's HTTP redirection service, but I'm not sure what the downsides will be for your domain (in terms of what URL shows up in Google searches, etc).