Amazon Route 53

Amazon Route 53 (Route 53) is a scalable and highly available Domain Name System (DNS) service. Released on December 5, 2010, [1] it is part of Amazon.com's cloud computing platform, Amazon Web Services (AWS). The name is a reference to TCP or UDP port 53, where DNS server requests are addressed,[2] and a reference to U.S. Route 66.[3] In addition to being able to route users to various AWS services, including EC2 instances, Route 53 also enables AWS customers to route users to non-AWS infrastructure and to monitor the health of their application and its endpoints. Route 53's servers are distributed throughout the world. Amazon Route 53 supports full, end-to-end DNS resolution over IPv6. Recursive DNS resolvers on IPv6 networks can use either IPv4 or IPv6 transport to send DNS queries to Amazon Route 53.[4]

Customers create "hosted zones" that act as a container for four name servers. The name servers are spread across four different TLDs. Customers are able to add, delete, and change any DNS records in their hosted zones. Amazon also offers domain registration services to AWS customers through Route 53.[5] Amazon provides an SLA of the service always being available at all times (100% available).[6]

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.

Supported DNS record types
Further information: List of DNS record types

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.[7] 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[8]

gollark: Ah.
gollark: Where?
gollark: Audit log? Do you have perms?
gollark: The thing is that you seem to alternate between "you are EVIL and we do not want you anyway" and "please join now", which is also... very dodecahedral.
gollark: They are actually better as foods, but I prefer melons.

See also

References
  1. "Amazon Route 53 – The AWS Domain Name Service". 2010-12-06. Retrieved April 30, 2018.
  2. "What is Amazon Route 53?". Archived from the original on March 7, 2013. Retrieved Mar 7, 2013.
  3. Neeru Jain (January 8, 2020). "Introduction to Amazon Route 53". Retrieved July 12, 2020. Many people wonder why is it called route 53! The basic explanation for such doubts is the reference to TCP or UDP port 53. The ‘route’ element in the name route 53 is an inspiration from the iconic ‘Route 66” in the USA.
  4. "Amazon Route 53 Now Supports DNS Queries over IPv6 Networks".
  5. "Route 53 Update - Domain Name Registration, Geo Routing, and a Price Reduction". 2014-07-31. Retrieved July 31, 2014.
  6. "Amazon Route 53 SLA". Retrieved November 8, 2011.
  7. "Amazon Route 53 FAQs". Retrieved November 8, 2011.
  8. Elz, R.; Bush, R. (July 1997). "CNAME resource records". Clarifications to the DNS Specification. IETF. p. 11. doi:10.17487/RFC2181. RFC 2181. Retrieved April 30, 2018.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.