<P> One of the key features of Route 53 is programmatic access to the service that allows customers to modify DNS records via web service calls . Combined with other features in AWS, this allows a developer to programmatically bring up a machine and point to components that have been created via other service calls such as those to create new S3 buckets or EC2 instances . </P> <P> Black hat hackers did a BGP attack to route everything that was going to Route 53 to go to a fake DNS server in Russia . When someone was looking up MyEtherWallet it sent them to a fake server in Russia . The crackers took over the DNS for MyEtherWallet by taking over the whole Route 53 DNS server . </P> <Ul> <Li> </Li> <Li> AAAA </Li> <Li> CAA </Li> <Li> CNAME </Li> <Li> MX </Li> <Li> NAPTR </Li> <Li> NS </Li> <Li> PTR </Li> <Li> SOA </Li> <Li> SPF </Li> <Li> SRV </Li> <Li> TXT </Li> </Ul> <P> Additionally, there is a Route 53 - specific virtual record type called "Alias". Alias records act similarly to CNAME records but are resolved on the server side and appear to clients as an A record . They can be used to create transparent references to other AWS resources that only provide DNS names and not IP addresses, such as an Elastic Load Balancer or a CloudFront distribution . Because alias records are resolved on the server - side and return A records to clients they can be used in domain apex records in a similar way to a CNAME record, where CNAME records are disallowed for this use by RFC 2181 </P>

Aws a highly available and scalable domain name system web service