Scenario

Your team is launching a new application and needs DNS configured in Route 53 for the domain example.com.

Task

1. Create a hosted zone for example.com
2. Create an A record for app.example.com pointing to 10.20.30.40 with a setting so that DNS responses are cached by resolvers for 1 minute before making new lookup.

Note: You can use either the AWS Management Console or AWS CLI to complete this task.

Step 1: Create the hosted zone

aws route53 create-hosted-zone --name example.com --caller-reference "exercise-$(date +%s)"

Creates a public hosted zone for example.com. The --caller-reference must be a unique string for each request.

Step 2: Get the hosted zone ID

ZONE_ID=$(aws route53 list-hosted-zones --query "HostedZones[?Name=='example.com.'].Id" --output text | sed 's|/hostedzone/||')
echo $ZONE_ID

Note: Route 53 stores domain names with a trailing dot (example.com.).

Step 3: Create the A record

aws route53 change-resource-record-sets --hosted-zone-id "$ZONE_ID" --change-batch '{
  "Changes": [
    {
      "Action": "CREATE",
      "ResourceRecordSet": {
        "Name": "app.example.com",
        "Type": "A",
        "TTL": 60,
        "ResourceRecords": [
          {
            "Value": "10.20.30.40"
          }
        ]
      }
    }
  ]
}'

Creates an A record that maps app.example.com to 10.20.30.40 with a 1-minute TTL.

Step 4: Verify the record

aws route53 list-resource-record-sets --hosted-zone-id "$ZONE_ID" --query "ResourceRecordSets[?Name=='app.example.com.']"

Shows the newly created record with its type, TTL, and IP value.