Clarify Private DNS support in Azure Firewall docs #127450
Conversation
|
@microsoft-github-policy-service agree |
|
@cpressland : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. @duau |
|
Learn Build status updates of commit f4a060e: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? Note that the IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
|
@duongau Could you review this proposed update to your article and enter Thanks! |
|
Can you review this old PR and determine whether it needs to be closed or merged? @MicrosoftDocs/public-repo-pr-review-team |
|
#sign-off |
|
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @duau |
|
@duongau I'll merge this, thanks! GitHub didn't recognize you as the author because your Microsoft alias of |
This PR updates the Azure Firewall DNS Settings documentation to clarify that while Azure Firewall can resolve Azure Private DNS zones for its own operations, the DNS Proxy feature does not return these records to downstream clients unless the configured upstream DNS server can also resolve them. This helps prevent confusion for users expecting Private DNS zones to be accessible via the DNS Proxy without additional configuration.