Skip to main content

domain name system - DNS: CNAME as www record

itemprop="text">

I'm considering changing the DNS www
records of a domain name from an A record to a CNAME. Various questions and answers on
serverfault are not as clear cut as I'd hoped. Also, many DNS checking tools like DNSsy
or intoDNS have as a check the fact that the www record is not a CNAME, is an A record,
pointing to a public IP address.



In my case, I
want to point my domain's www record to an Amazon Web Services load balancer which I can
only do with a CNAME. What would be the best way to achieve that?



Answer




If you are concerned about this issue, you can use Route 53 and ELB together to
get what you want. Create the www record as an A record, then
select the "Alias" option and the interface will allow you to select an AWS-specific
target to point the record to. So the ELB has to exist first, then you can create the
Alias to it.



So you start to create a new A
record in Route 53 as usual, but you click on the "Alias" option right under the host
name. The freeform text block will disappear and you will be given the ability to select
your ELB under "Alias Target". Select your ELB and save the change. You will then have
an A record that points to www, which will be your
ELB.




(The above info about
the Route 53 UI has been corrected from the original
error.)



This is a special Route 53
feature most often used to handle serving from the domain apex, where A records are
required. But it can also be used for subdomains such as www.
Basically, it's an A record that acts like a CNAME within the confines of AWS. Using
this feature, DNS tools will find an A record.



Comments

Popular posts from this blog

iLO 3 Firmware Update (HP Proliant DL380 G7)

The iLO web interface allows me to upload a .bin file ( Obtain the firmware image (.bin) file from the Online ROM Flash Component for HP Integrated Lights-Out. ) The iLO web interface redirects me to a page in the HP support website ( http://www.hp.com/go/iLO ) where I am supposed to find this .bin firmware, but no luck for me. The support website is a mess and very slow, badly categorized and generally unusable. Where can I find this .bin file? The only related link I am able to find asks me about my server operating system (what does this have to do with the iLO?!) and lets me download an .iso with no .bin file And also a related question: what is the latest iLO 3 version? (for Proliant DL380 G7, not sure if the iLO is tied to the server model)

linux - Awstats - outputting stats for merged Access_logs only producing stats for one server's log

I've been attempting this for two weeks and I've accessed countless number of sites on this issue and it seems there is something I'm not getting here and I'm at a lost. I manged to figure out how to merge logs from two servers together. (Taking care to only merge the matching domains together) The logs from the first server span from 15 Dec 2012 to 8 April 2014 The logs from the second server span from 2 Mar 2014 to 9 April 2014 I was able to successfully merge them using the logresolvemerge.pl script simply enermerating each log and > out_putting_it_to_file Looking at the two logs from each server the format seems exactly the same. The problem I'm having is producing the stats page for the logs. The command I've boiled it down to is /usr/share/awstats/tools/awstats_buildstaticpages.pl -configdir=/home/User/Documents/conf/ -config=example.com awstatsprog=/usr/share/awstats/wwwroot/cgi-bin/awstats.pl dir=/home/User/Documents/parced -month=all -year=all...

linux - How can I get my mediawiki to stop thinking I have cookies disabled?

I've searched half a day for how to resolve this issue, and can't figure it out. Shortly after I made my wiki a simple private wiki according to the instructions at Mediawiki's website, it started giving me this weird login error message: Wiki uses cookies to log in users. You have cookies disabled. Please enable them and try again. If I remove those private wiki settings, the error disappears, even if I try logging in. But I need it to be a private wiki for only my team. So what do I do? Here's what I've done so far. Just to be safe, after ever change, I try rebooting Apache using: sudo /etc/init.d/apache2 restart In my php.ini file, I have the following set: session.save_path = "/var/lib/php5" session.cookie_secure = secure session.cookie_path = /tmp session.cookie_domain = my server's internal URL (should I even set this? this field was blank before, but not commented out) session.referer_check = Off I ran the following to ensure that the fold...