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.