Hosted zones concept in AWS - Mini Project: Build & Apply

Create a Private Hosted Zone in AWS Route 53

📖 Scenario: You are setting up a private network for your company's internal services. To manage domain names inside this private network, you will create a private hosted zone in AWS Route 53.

🎯 Goal: Build a private hosted zone in AWS Route 53 with a specific domain name and associate it with a VPC.

📋 What You'll Learn

Create a private hosted zone with the domain name internal.example.com

Associate the hosted zone with the VPC ID vpc-0abc123def456ghij

Set the hosted zone type to Private

Use AWS CLI commands or AWS SDK code snippets

💡 Why This Matters

🌍 Real World

Private hosted zones are used to manage DNS names inside a private network, such as a company's internal cloud environment, ensuring internal services are reachable only within the VPC.

💼 Career

Understanding hosted zones and VPC associations is essential for cloud engineers and network administrators managing AWS infrastructure and internal DNS.

1

Create the hosted zone data structure

Create a JSON object called hosted_zone_config with the key Name set to "internal.example.com" and the key CallerReference set to "unique-string-001".

AWS

# Create the hosted_zone_config JSON object
# Your code here

Hint

The Name is the domain name for the hosted zone. The CallerReference is a unique string to identify the request.

2

Add the VPC association configuration

Add a key VPC to the hosted_zone_config dictionary. Set it to a dictionary with keys VPCRegion set to "us-east-1" and VPCId set to "vpc-0abc123def456ghij".

AWS

hosted_zone_config = {
    "Name": "internal.example.com",
    "CallerReference": "unique-string-001"
}
# Add the VPC association configuration below
# Your code here

Hint

The VPC key links the hosted zone to the specific VPC by region and ID.

3

Add the hosted zone type configuration

Add a key HostedZoneConfig to hosted_zone_config. Set it to a dictionary with the key PrivateZone set to true.

AWS

hosted_zone_config = {
    "Name": "internal.example.com",
    "CallerReference": "unique-string-001",
    "VPC": {
        "VPCRegion": "us-east-1",
        "VPCId": "vpc-0abc123def456ghij"
    }
}
# Add HostedZoneConfig with PrivateZone true below
# Your code here

Hint

Setting PrivateZone to true makes the hosted zone private to the VPC.

4

Complete the AWS CLI command to create the hosted zone

Write the AWS CLI command string create_command that uses aws route53 create-hosted-zone with the --name internal.example.com, --vpc VPCRegion=us-east-1,VPCId=vpc-0abc123def456ghij, and --hosted-zone-config PrivateZone=true options.

AWS

hosted_zone_config = {
    "Name": "internal.example.com",
    "CallerReference": "unique-string-001",
    "VPC": {
        "VPCRegion": "us-east-1",
        "VPCId": "vpc-0abc123def456ghij"
    },
    "HostedZoneConfig": {
        "PrivateZone": true
    }
}
# Write the AWS CLI command string create_command below
# Your code here

Hint

This command creates the private hosted zone with the specified name, VPC association, and private zone setting.

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