Cname vs alias aws If you're creating an alias record that has the same name as the hosted zone (known as the zone apex), you can't route traffic to a record for which the value of Type is CNAME. Registros de alias. An A-ALIAS resource record is not supported by AWS for RDS. CNAME is the one that acts like an alias pointing to the canonical name, while A has nothing to do with aliases. Los registros de alias le permiten enrutar el tráfico a AWS los recursos seleccionados, incluidas, entre otras, las CloudFront distribuciones y los The difference between a CNAME and an alias is that a CNAME is still a proper, standard, ordinary DNS CNAME, which returns a DNS query response "hi, you need to know that the real ("canonical") name of the server you are looking for is 'x'" and, depending on circumstances, may also include the A record for the target host or may not, requiring Alias record can point to other Route53 or AWS resources but not to external DNS names or IP addresses. CNAME records can be used only for subdomains. It is designed to give developers and businesses an extremely reliable and cost effective way to route end users to Internet applications by translating names like example. The problem with CNAME is that it actually works like an alias, so for that name you no longer can specify other record types like MX,TXT,SRV etc. Here is all you need to know about Route 53 CNAME vs Alias . Both of them are translated internally into A records to There is no "better," there's only one correct answer: the Alias RR type must be the same as the target RR. vmgs mcgzhx omtzn rlo mtuw xsm atvd deej murxafl pnjor mgqe wkzzpkh kwiu wcf ixsxyrk