Skip to content

Clarify Private DNS support in Azure Firewall docs #127450

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

cpressland
Copy link

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.

@cpressland
Copy link
Author

@microsoft-github-policy-service agree

Copy link
Contributor

@cpressland : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. @duau

Copy link
Contributor

Learn Build status updates of commit f4a060e:

✅ Validation status: passed

File Status Preview URL Details
articles/firewall/dns-settings.md ✅Succeeded

For more details, please refer to the build report.

@ttorble
Copy link
Contributor

ttorble commented Jul 31, 2025

@duongau

Can you review the proposed changes? Note that the author metadata should reflect your GitHub alias to facilitate automation. Can you create a PR in the private repo to update this? Thanks.

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Jul 31, 2025
@v-dirichards
Copy link
Contributor

@duongau Could you review this proposed update to your article and enter #sign-off in a comment if it's ready to merge?

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants