Hosted zones concept in AWS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a hosted zone in AWS Route 53?

A hosted zone is a container that holds information about how to route traffic for a specific domain or subdomain. It stores DNS records for that domain.

beginner

What are the two types of hosted zones in AWS Route 53?

Public hosted zones route traffic on the internet, while private hosted zones route traffic within an Amazon VPC (Virtual Private Cloud).

intermediate

How does a public hosted zone differ from a private hosted zone?

A public hosted zone is visible on the internet and routes domain traffic globally. A private hosted zone is only visible inside one or more VPCs and routes traffic privately within AWS.

beginner

What is the purpose of DNS records inside a hosted zone?

DNS records define how domain names map to IP addresses or other resources, directing where traffic should go for services like websites or email.

intermediate

Can you have multiple hosted zones for the same domain in AWS Route 53?

No, you can only have one public hosted zone per domain name in Route 53. Having multiple public hosted zones for the same domain can cause conflicts in DNS resolution. However, you can have multiple private hosted zones for the same domain associated with different VPCs.

What does a hosted zone in AWS Route 53 contain?

A Virtual machines for hosting websites

B DNS records for a domain or subdomain

C Security certificates for HTTPS

D User access policies

A hosted zone contains DNS records that tell the internet how to route traffic for a domain.

Which type of hosted zone is used to route traffic within an Amazon VPC?

A Private hosted zone

B Public hosted zone

C Global hosted zone

D Regional hosted zone

Private hosted zones route DNS traffic only within specified VPCs.

Can you create multiple hosted zones for the same domain in AWS Route 53?

A No, only one public hosted zone per domain is allowed

B Yes, to manage different subdomains

C Yes, but only for private hosted zones

D No, unless you use different AWS accounts

Route 53 allows only one public hosted zone per domain to avoid DNS conflicts.

What is the main use of DNS records inside a hosted zone?

A To store website content

B To monitor network traffic

C To manage user permissions

D To map domain names to IP addresses or resources

DNS records tell where to send traffic for a domain by mapping names to IPs or other targets.

Which hosted zone type is visible to the public internet?

A Private hosted zone

B Internal hosted zone

C Public hosted zone

D Restricted hosted zone

Public hosted zones are visible on the internet and route traffic globally.

Explain what a hosted zone is and the difference between public and private hosted zones in AWS Route 53.

Think about where the DNS information is used and who can see it.

Describe the role of DNS records inside a hosted zone and why you cannot have multiple hosted zones for the same domain.

Consider how DNS resolution works and the importance of unique routing information.

Practice

1. What is the main purpose of a hosted zone in AWS Route 53?

easy

A. To manage DNS records for a specific domain

B. To store website files

C. To host virtual machines

D. To monitor network traffic

Solution

1. Step 1: Understand the role of hosted zones

   Hosted zones are containers for DNS records that belong to a domain.

2. Step 2: Identify what hosted zones manage

   They manage DNS records, which connect domain names to IP addresses or other resources.

3. Final Answer:

   To manage DNS records for a specific domain -> Option A

4. Quick Check:

   Hosted zone = DNS management [OK]

Hint: Hosted zones manage DNS records, not files or servers [OK]

Common Mistakes:

• Confusing hosted zones with web hosting
• Thinking hosted zones store website content
• Assuming hosted zones monitor traffic

2. Which of the following is the correct way to create a public hosted zone in AWS CLI?

easy

A. aws route53 create-hosted-zone --name example.com --caller-reference 12345 --hosted-zone-config PrivateZone=true

B. aws route53 create-hosted-zone --name example.com --caller-reference 12345 --hosted-zone-config PrivateZone=false,VPCId=vpc-12345678,Region=us-east-1

C. aws route53 create-hosted-zone --name example.com --caller-reference 12345

D. aws route53 create-hosted-zone --domain example.com --private false

Solution

1. Step 1: Review AWS CLI syntax for creating hosted zones

   The basic command requires --name and --caller-reference; --hosted-zone-config is optional.

2. Step 2: Identify correct public hosted zone creation

   Omitting --hosted-zone-config creates a public hosted zone by default.

3. Final Answer:

   aws route53 create-hosted-zone --name example.com --caller-reference 12345 -> Option C

4. Quick Check:

   Default is public hosted zone [OK]

Hint: No PrivateZone flag means public hosted zone by default [OK]

Common Mistakes:

• Setting PrivateZone=true creates private zone, not public
• Using incorrect parameter names like --domain
• Omitting required --caller-reference

3. Given the following Route 53 hosted zone configuration, what will happen if you create an A record pointing to an IP address?

Hosted Zone: example.com
Record Name: www.example.com
Record Type: A
Value: 192.0.2.44

medium

A. The record will redirect to example.com automatically

B. www.example.com will resolve to the IP 192.0.2.44

C. The record will cause a DNS error

D. www.example.com will resolve to the hosted zone ID

Solution

1. Step 1: Understand A record function

   An A record maps a domain name to an IPv4 address.

2. Step 2: Apply to given record

   The record www.example.com with type A and value 192.0.2.44 means it resolves to that IP.

3. Final Answer:

   www.example.com will resolve to the IP 192.0.2.44 -> Option B

4. Quick Check:

   A record maps domain to IP [OK]

Hint: A record points domain to IPv4 address directly [OK]

Common Mistakes:

• Confusing A record with hosted zone ID
• Expecting automatic redirects from DNS
• Assuming DNS error without syntax issues

4. You created a private hosted zone but your EC2 instances cannot resolve the domain names inside it. What is the most likely cause?

medium

A. The private hosted zone is not associated with the VPC

B. The hosted zone is public instead of private

C. The domain name is misspelled in the record

D. The EC2 instances do not have internet access

Solution

1. Step 1: Understand private hosted zone requirements

   Private hosted zones must be linked to one or more VPCs to work.

2. Step 2: Identify why EC2 can't resolve names

   If the private hosted zone is not associated with the VPC where EC2 runs, DNS queries fail.

3. Final Answer:

   The private hosted zone is not associated with the VPC -> Option A

4. Quick Check:

   Private hosted zone needs VPC association [OK]

Hint: Private hosted zones must link to VPCs to resolve names [OK]

Common Mistakes:

• Assuming public/private mix-up causes resolution failure
• Ignoring VPC association requirement
• Thinking internet access affects private DNS resolution

5. You want to host a website on AWS and use a custom domain. Which steps correctly describe how to use a hosted zone to make your website accessible via your domain?

hard

A. Create a private hosted zone, add DNS records, and update your domain registrar to use Route 53 name servers

B. Create a hosted zone, configure EC2 security groups, and update your domain registrar

C. Create a public hosted zone, upload website files to Route 53, and update your domain registrar

D. Create a public hosted zone for your domain, add DNS records pointing to your website's IP or load balancer, then update your domain registrar to use Route 53 name servers

Solution

1. Step 1: Choose hosted zone type for public website

   A public hosted zone is needed to make the domain accessible on the internet.

2. Step 2: Add DNS records pointing to website

   Add A or CNAME records pointing to your website's IP or load balancer.

3. Step 3: Update domain registrar with Route 53 name servers

   Set your domain's name servers to those provided by Route 53 to route traffic correctly.

4. Final Answer:

   Create a public hosted zone for your domain, add DNS records pointing to your website's IP or load balancer, then update your domain registrar to use Route 53 name servers -> Option D

5. Quick Check:

   Public hosted zone + DNS records + registrar update = website access [OK]

Hint: Public hosted zone + DNS records + registrar update = website online [OK]

Common Mistakes:

• Using private hosted zone for public website
• Thinking Route 53 hosts website files
• Skipping domain registrar name server update