Bird
0
0

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

medium📝 Debug Q14 of 15
AWS - Route 53
You created a private hosted zone but your EC2 instances cannot resolve the domain names inside it. What is the most likely cause?
AThe private hosted zone is not associated with the VPC
BThe hosted zone is public instead of private
CThe domain name is misspelled in the record
DThe EC2 instances do not have internet access
Step-by-Step Solution
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]
Quick Trick: 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

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes