If you create a private hosted zone for example.internal associated with VPC vpc-abc123, what happens when a DNS query for example.internal is made from a different VPC not associated with the hosted zone?

medium📝 Predict Output Q5 of 15

AWS - Route 53

AThe query returns the hosted zone records

BThe query returns NXDOMAIN (not found)

CThe query is forwarded to the public hosted zone

DThe query returns the default AWS DNS response

Step-by-Step Solution

Solution:

Step 1: Understand private hosted zone scope
Private hosted zones are visible only to associated VPCs.
Step 2: Query from unassociated VPC
DNS queries from VPCs not associated with the private hosted zone get NXDOMAIN.
Final Answer:
The query returns NXDOMAIN (not found) -> Option B
Quick Check:
Private hosted zone visible only in associated VPCs [OK]

Quick Trick: Private hosted zone DNS only works in associated VPCs [OK]

Common Mistakes:

Expecting records from unassociated VPC
Assuming forwarding to public zone
Thinking AWS returns default DNS answer

Master "Route 53" in AWS

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More AWS Quizzes

If you create a private hosted zone for example.internal associated with VPC vpc-abc123, what happens when a DNS query for example.internal is made from a different VPC not associated with the hosted zone?

Step 1: Understand private hosted zone scope

Step 2: Query from unassociated VPC

Final Answer:

Quick Check:

Want More Practice?