nerdexam
Microsoft

AZ-104 · Question #183

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might…

The correct answer is B. No. Option B (No) is correct because a PTR record is used for reverse DNS lookup - mapping an IP address back to a hostname - and does nothing to fix forward name resolution (hostname → IP). The actual problem is almost certainly that the domain registrar for contoso.com has not…

Submitted by tyler.j· Mar 4, 2026Implement and manage virtual networking

Question

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it As a result these questions will not appear in the review screen. Your company registers a domain name of contoso.com. You create an Azure DNS zone named contoso.com, and then you add an A record to the zone for a host named www that has an IP address of 131.107.1.10. You discover that Internet hosts You need to resolve the name resolution issue. Solution: You create a PTR record for www in the contoso.com zone. Does this meet the goal?

Options

  • AYes
  • BNo

How the community answered

(31 responses)
  • A
    23% (7)
  • B
    77% (24)

Explanation

Option B (No) is correct because a PTR record is used for reverse DNS lookup - mapping an IP address back to a hostname - and does nothing to fix forward name resolution (hostname → IP). The actual problem is almost certainly that the domain registrar for contoso.com has not been updated to delegate to Azure DNS name servers; internet hosts query the registrar's listed name servers, which don't know about the Azure zone or its A record.

Why "Yes" (A) is wrong: Adding a PTR record to the contoso.com zone is irrelevant to the forward resolution failure. Even if the PTR record were correct, it would only allow someone to reverse-look up 131.107.1.10 - it would not help any host resolve www.contoso.com to that IP.

Memory tip: Think of PTR as "Pointer back" - it points an IP back to a name. If forward resolution is broken, check NS delegation at the registrar, not PTR records. The fix for this scenario is updating the registrar to use Azure's assigned name servers for the zone.

Topics

#Azure DNS#DNS Records#A Record#PTR Record

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full AZ-104 Practice