Route 53 Zones Flashcards
What is a Route 53 Hosted Zone?
A Route 53 hosted zone is a container that holds information about how you want to route traffic for a domain (and its subdomains) on the internet. It contains records that define where the traffic should be directed.
What are the types of Route 53 Hosted Zones?
There are two types of Route 53 hosted zones: Public Hosted Zones, for routing internet traffic, and Private Hosted Zones, for routing traffic within one or more Amazon VPCs.
How do you create a Route 53 Hosted Zone?
To create a hosted zone, you use the Route 53 console, API, or AWS CLI to create a new hosted zone for your domain. Once created, Route 53 automatically assigns four name servers to the hosted zone.
What is the purpose of NS Records in a Hosted Zone?
NS (Name Server) records identify the DNS servers responsible for your domain. When you register a domain, these records are updated in the registrar to point to Route 53 name servers.
What are SOA Records in Route 53?
An SOA (Start of Authority) record provides information about the domain and the hosted zone, including the primary DNS server, email of the domain administrator, domain serial number, and other key details.
What are A Records in Route 53?
A (Address) records map a domain, such as example.com, to an IP address, allowing users’ browsers to reach the domain. This record type is fundamental for DNS routing.
How does CNAME Record differ from an A Record?
A CNAME (Canonical Name) record redirects DNS queries from one domain name (alias) to another (the canonical domain). Unlike A records, they cannot be used for root domain names.
What is a Route 53 Alias Record?
Alias records are Route 53-specific and allow you to map one DNS name to another ‘target’ DNS name, like mapping a root domain to an AWS resource, such as an S3 bucket or CloudFront distribution. They work similarly to CNAME records but can be used for root domains.
How can you manage traffic flow with Route 53?
Route 53 provides traffic policies that allow you to route traffic based on health checks, geographic location, latency, and other parameters, offering sophisticated traffic management capabilities beyond traditional DNS.
What steps are necessary to migrate DNS service for an existing domain to Route 53?
To migrate to Route 53, you must create a new hosted zone, recreate the existing DNS records in Route 53, update the domain’s NS records at your current registrar to use Route 53 name servers, and ensure all records are replicated before fully switching over.
