Welcome
What Is Route 53 and How Does it Work?
- Hosted Zones
- DNS Domain Name Format
- Supported DNS Resource Record Types
- NS and SOA Records that Route 53 Creates for a Hosted Zone
- Limits on Route 53 API Requests and Entity Counts
- DNS Constraints and Behaviors
- Route 53 Pricing
- AWS Identity and Access Management
Getting Started with Route 53
- Getting Started: Creating a Domain that Uses Route 53
- How to Use the Route 53 Console, API, AWS SDKs, and Command-Line Tool
Creating a Domain that Uses Route 53 as the DNS Service
Migrating an Existing Domain to Route 53
Creating a Subdomain that Uses Route 53 without Migrating the Parent Domain
Migrating a Subdomain to Route 53 without Migrating the Parent Domain
Working with Hosted Zones
- Creating a Hosted Zone
- Getting the Name Servers for a Hosted Zone
- Listing the Hosted Zones for an AWS Account
- Deleting a Hosted Zone
Working with Resource Record Sets
- Creating, Changing, and Deleting Resource Record Sets
- Listing Resource Record Sets
Creating Weighted Resource Record Sets
- Using Weighted Resource Record Sets with the 2010-10-01 Route 53 API
Creating Alias Resource Record Sets
- How to Create Alias Resource Record Sets
- How to Create Weighted Alias Resource Record Sets
- Using Aliases with the 2010-10-01 Route 53 API
Creating Latency Resource Record Sets
- How to Create Latency Resource Record Sets
- Using Latency Resource Record Sets with Route 53 API Versions Earlier than 2012-02-29
Managing Resource Availability
- How Health Checks Work in Simple Route 53 Configurations
- How Health Checks Work in More Complex Route 53 Configurations
- Configuring Route 53 to Check the Health of Your Resources
- Configuring Router and Firewall Rules for Route 53 Health Checks
- Configuring Route 53 Active-Active and Active-Passive Failover
- Creating and Deleting Health Checks
- Adding Health Checks to Resource Record Sets
- Creating Failover Resource Record Sets
- Determining the Status of a Health Check
- How Route 53 Determines Whether an Endpoint Is Healthy
- How Route 53 Averts Failover Problems
- Using API Versions Before 2012-12-12
Routing Queries to a Website That Is Hosted in an Amazon S3 Bucket
Using IAM to Control Access to Route 53 Resources
Making API Requests
- Endpoints
- REST Requests
- REST Responses
  - Request ID
- Authenticating REST Requests
Route 53 Tutorials
Example: Using dnscurl.pl
Additional Route 53 Resources
Third-Party Tools and Libraries
Document History

AWS Documentation » Amazon Route 53 » Developer Guide » What Is Route 53 and How Does it Work?	« Previous Next »
	Did this page help you? Yes \| No \| Tell us about it...

What Is Route 53 and How Does it Work?

Route 53 is a scalable Domain Name System (DNS) web service. It provides secure and reliable routing to your infrastructure that uses Amazon Web Services (AWS) products, such as Amazon Elastic Compute Cloud (Amazon EC2), Elastic Load Balancing, or Amazon Simple Storage Service (Amazon S3). You can also use Route 53 to route users to your infrastructure outside of AWS.

Route 53 is an authoritative DNS service, meaning it translates friendly domains names like www.example.com into IP addresses like 192.0.2.1. Route 53 responds to DNS queries using a global network of authoritative DNS servers, which reduces latency. For a list of the locations of Route 53 DNS servers, see The Amazon Route 53 Global Network on the Amazon Route 53 detail page.

You can manage your DNS records through the Route 53 console or the Route 53 API, or set account-level user and access management through the AWS Identity and Access Management (IAM) API.

See the following topics for more information about how Route 53 works.

Topics

Document Conventions	« Previous Next »
Terms of Use	Did this page help you? Yes \| No \| Tell us about it...

Warning

Javascript is disabled or is unavailable in your browser.
To use the AWS Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions.