Amazon Route 53

{{Short description|Cloud-based Domain Name System service}}

{{Infobox software

| title = Route 53

| logo =

| logo caption =

| logo alt =

| logo size =

| collapsible =

| screenshot =

| screenshot size =

| screenshot alt =

| caption =

| other_names =

| author =

| developer = Amazon.com, Inc.

| released = {{start date and age|2010|12|5|paren=y|df=y}}

| ver layout =

| discontinued =

| latest release version =

| latest release date =

| latest preview version =

| latest preview date =

| repo =

| qid =

| programming language =

| middleware =

| engine =

| operating system =

| platform =

| included with =

| replaces =

| replaced_by =

| service_name =

| size =

| standard =

| language =

| language count =

| language footnote =

| genre =

| license =

| website =

| AsOf =

}}

Amazon Route 53 is a Domain Name System (DNS) service by Amazon Web Services (AWS) since 2010. The name is a possible reference to U.S. Routes,{{cite web|first=Neeru |last=Jain |date=2020-01-08 |title=Introduction to Amazon Route 53 |url=https://www.whizlabs.com/blog/amazon-route-53/ |access-date=2020-07-12 |quote=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.}} and "53" is a reference to the TCP/UDP port 53, where DNS server requests are addressed.{{cite web

|url=https://aws.amazon.com/route53/faqs/

|archive-url=https://web.archive.org/web/20130307215723/https://aws.amazon.com/route53/faqs/

|url-status=dead

|archive-date=2013-03-07

|access-date=2013-03-07

|title=What is Amazon Route 53?

}} Route 53 allows users to reach AWS services and 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.{{Cite web | url=https://aws.amazon.com/about-aws/whats-new/2016/10/amazon-route-53-now-supports-dns-queries-over-ipv6-networks/ | title=Amazon Route 53 Now Supports DNS Queries over IPv6 Networks}}

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.{{cite web

|url=https://aws.amazon.com/blogs/aws/route-53-domain-reg-geo-route-price-drop/

|access-date=2014-07-31

|title=Route 53 Update - Domain Name Registration, Geo Routing, and a Price Reduction

|date=2014-07-31

|first=Jeff |last=Barr

|work=AWS News Blog

}} Amazon provides an SLA of the service always being available at all times (100% available).{{cite web

|url=https://aws.amazon.com/route53/sla/

|access-date=2011-11-08

|title=Amazon Route 53 SLA

}}

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.{{fact|date=May 2024}}

Alias resource record type

Route 53 has a proprietary 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.{{cite web

|url=https://aws.amazon.com/route53/faqs/#Supported_DNS_record_types

|title=Amazon Route 53 FAQs

|access-date=2011-11-08

}} 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.

{{cite IETF

| title = Clarifications to the DNS Specification

| rfc = 2181

| sectionname = CNAME resource records

| page = 11

| last1 = Elz

| first1 = R.

| last2 = Bush

| first2 = R.

| date=July 1997

| publisher = IETF

| access-date = 2018-04-30

}}

See also

References

{{Reflist|1}}