amazon-route53domain-name-systemnameserver
I bought a domain from GoDaddy, say abc.com.
I was able to forward profile.abc.com to http://www.linkedin.com/in/myname.
Not I've changed my domain nameserver to Amazon Route 53, I want to do the same thing but wasn't able to do so, here's what I've tried:
Create a new record set, name is profile.abc.com, type is CNAME, value is http://www.linkedin.com/in/myname.
But this doesn't work.
I have another CNAME, hg.abc.com, which points to my BitBucket (value = www.bitbucket.com), that one works.
Regardless of how godaddy or other registrars use it in their web interfaces, "@" has a specific meaning in zone configuration files used with BIND.
When an @ is encountered in a zone file, it's replaced by the current value of $ORIGIN. $ORIGIN is usually defined as the root domain - the same as you're familiar with at godaddy - but it doesn't have to be. $ORIGIN can be defined as any domain to simplify a zone file or it can be left undefined, in which case it'll be taken to be the zone name specified in named.conf.
But the behaviour you're asking about is not really to do with the underlying DNS software, it's how the web interface you've been given parses the information you specify and generates a zone file. Apparently Amazon doesn't let you throw an @ around as much as godaddy, so you're stuck having to use the zone name.
(It's worth noting that a CNAME record technically shouldn't point to a domain name, it should point to a Canonical host NAME - but in your example, your domain name is also a host name.)
To make things nice and clear, as some of the GoDaddy help articles are dead wrong:
You just need to paste the two records from the server settings into your Route 53 control panel as a new record.
The possible deception here is the the GD email panel will tell you you're wrong, but not what is right so you can make it right. Further, their help article tells you do look for the proper MX record settings under the Domains manager, where you'll not find them.
Finally, AWS is a tad confusing since they'll only let you enter a single apex domain MX entry. You can't have two as GD wants and some other zone managers allow, hence the need to double them up.
Hope this helps others! :)
Best Answer
The contents of the CNAME record cannot be a URL. It must point to another name in the DNS, just like
hg.abc.comdoes.It sounds like what you want to do is host a web site at
profile.abc.comwhich redirects all incoming requests tohttp://www.linkedin.com/in/myname. If so, that's exactly what you should do:Redirectdirective)profile.abc.comthat points to the canonical name of the server that hosts the web site, ORprofile.abc.comthat give the IP addresses of the server that hosts the web site.