Hosted zones concept in AWS - Step-by-Step Execution

Process Flow - Hosted zones concept

Create Hosted Zone

↓

Assign Domain Name

↓

Add DNS Records

↓

DNS Queries Received

↓

Route Traffic Based on Records

↓

Respond to DNS Queries

This flow shows how a hosted zone is created, assigned a domain, configured with DNS records, and then used to route traffic when DNS queries arrive.

Execution Sample

AWS

Create hosted zone for example.com
Add A record pointing to 192.0.2.1
DNS query for www.example.com
Resolve to 192.0.2.1

This example shows creating a hosted zone, adding a record, and resolving a DNS query using that record.

Process Table

Step	Action	Input	State Change	Output
1	Create hosted zone	Domain: example.com	Hosted zone 'example.com' created	Hosted zone ready
2	Add DNS record	Type: A, Name: www, Value: 192.0.2.1	Record added to hosted zone	Record stored
3	Receive DNS query	Query: www.example.com	Lookup in hosted zone records	Found A record
4	Route traffic	Use A record value	Prepare response with IP	Respond with 192.0.2.1
5	End	No more queries	No state change	Process complete

💡 No more DNS queries to process, hosted zone serves all configured records

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
HostedZone	None	example.com created	example.com with www A record	example.com with www A record	example.com with www A record	example.com with www A record
DNSRecords	Empty	Empty	A record for www added	A record for www present	A record for www present	A record for www present
DNSQuery	None	None	None	Query for www.example.com	Query resolved	None
Response	None	None	None	None	IP 192.0.2.1 sent	None

Key Moments - 3 Insights

Why do we need to create a hosted zone before adding DNS records?

Because the hosted zone is like a container for all DNS records of a domain. Without it, there is no place to store or manage the records. See execution_table step 1 and 2.

What happens if a DNS query is received for a name not in the hosted zone?

The hosted zone will not find a matching record and cannot resolve the query. This is why only configured records respond. See execution_table step 3.

How does the hosted zone respond to DNS queries?

It looks up the requested name in its records and returns the associated value, like an IP address. See execution_table steps 3 and 4.

Visual Quiz - 3 Questions

Look at the execution_table, what is the state of DNSRecords after step 2?

A A record for www added

B Query for www.example.com received

C Empty

D Hosted zone deleted

💡 Hint

Check the 'State Change' column in row for step 2.

At which step does the hosted zone respond with the IP address?

A Step 3

B Step 4

C Step 1

D Step 5

💡 Hint

Look for 'Respond with 192.0.2.1' in the 'Output' column.

If no DNS records are added, what will happen when a DNS query arrives?

A Hosted zone will respond with IP

B Hosted zone will create a record automatically

C Hosted zone will not find a matching record

D Hosted zone will delete itself

💡 Hint

Refer to key_moments explanation about queries without matching records.

Concept Snapshot

Hosted zones are containers for DNS records of a domain.
Create a hosted zone before adding records.
Add DNS records like A, CNAME inside the hosted zone.
DNS queries are answered by looking up these records.
No records means no resolution for queries.
Hosted zones route traffic by responding with record values.

Full Transcript

A hosted zone is like a folder that holds all the DNS records for a domain name. First, you create the hosted zone for your domain, for example, example.com. Then you add DNS records inside it, such as an A record that points www.example.com to an IP address. When someone asks for www.example.com, the hosted zone looks up the record and replies with the IP address. If no record matches the query, the hosted zone cannot answer. This process helps route internet traffic to the right place.

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