Bird
0
0

You created a private hosted zone for internal.example.com and associated it with your VPC, but DNS queries from EC2 instances fail to resolve names in this zone. What is the most probable cause?

medium📝 Debug Q7 of 15
AWS - Route 53
You created a private hosted zone for internal.example.com and associated it with your VPC, but DNS queries from EC2 instances fail to resolve names in this zone. What is the most probable cause?
AThe domain name is not registered in Route 53
BThe hosted zone is public instead of private
CThe EC2 instances lack internet access
DThe VPC is not associated with the private hosted zone
Step-by-Step Solution
Solution:
  1. Step 1: Check VPC association

    Private hosted zones must be explicitly associated with VPCs to resolve DNS queries within them.
  2. Step 2: Analyze failure reason

    If DNS queries fail, the most common cause is missing VPC association.
  3. Final Answer:

    The VPC is not associated with the private hosted zone -> Option D
  4. Quick Check:

    Private hosted zones require VPC association [OK]
Quick Trick: Private zones must be linked to VPCs to resolve DNS [OK]
Common Mistakes:
  • Assuming public/private zone type causes resolution failure
  • Thinking internet access is required for private DNS
  • Confusing domain registration with hosted zone setup

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes